# eggPlant Performance workspaces and source control

**URL:** <https://forums.eggplantsoftware.com/t/eggplant-performance-workspaces-and-source-control/3464>\
**Category:** Eggplant Performance\
**Created:** [March 27, 2014, 6:10am UTC](https://forums.eggplantsoftware.com/t/eggplant-performance-workspaces-and-source-control/3464 "2014-03-27T06:10:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![radders](https://forums.eggplantsoftware.com/letter_avatar_proxy/v4/letter/r/53a042/32.png) [@radders](https://forums.eggplantsoftware.com/u/radders)\
**Post date:** [March 27, 2014, 6:10am UTC](https://forums.eggplantsoftware.com/t/eggplant-performance-workspaces-and-source-control/3464/1 "2014-03-27T06:10:00Z")

</div>

Hello,

as our eggPlant Performance workspaces are shared between a number of testers we’d like to add them to some sort of source control system (probably Subversion with TortoiseSVN).

Are there any files or folders contained in a workspace that should be excluded from source control? (e.g. files generated at runtime etc.)

Thanks,

Jon

---

<div class="post-metadata">

**Author:** ![Ian1](https://forums.eggplantsoftware.com/letter_avatar_proxy/v4/letter/i/ebca7d/32.png) [@Ian1](https://forums.eggplantsoftware.com/u/Ian1)\
**Post date:** [April 1, 2014, 5:46am UTC](https://forums.eggplantsoftware.com/t/eggplant-performance-workspaces-and-source-control/3464/2 "2014-04-01T05:46:16Z")

</div>

Hi Jon,

The following lists what you can exclude from SCC  
[list]

- The runs folder of a project, e.g. MyWorkspace\projects\MyProject\runs.  
These are where all the files generated at runtime are located

- The repository folders under both the workspace and projects as these contain the IDE and compilation files that will be regenerated when building.

- .bak files and the WSLock file.

- Optionally the Analysis folder under a project as which contains the Analyzer database that can be rebuilt from the results under the runs folder.  
[/list:u]  
Note that if you want to reliably save and recover complete snapshots, we recommend that you use the Export and Import Workspace/Projects feature under the File menu of eggplant Performance Studio. There are many inter-dependencies of the numerous configuration, data and source files and using this feature ensures you capture a complete and portable snapshot that can also be imported into later versions of the product. This would not be always the case with a file archive.

Let us know if you have any further questions.

---

<div class="post-metadata">

**Author:** ![radders](https://forums.eggplantsoftware.com/letter_avatar_proxy/v4/letter/r/53a042/32.png) [@radders](https://forums.eggplantsoftware.com/u/radders)\
**Post date:** [April 2, 2014, 5:13am UTC](https://forums.eggplantsoftware.com/t/eggplant-performance-workspaces-and-source-control/3464/3 "2014-04-02T05:13:03Z")

</div>

Thanks, I think we’ll probably have to use a combination of source control and make regular backups using the export feature 🙂