How does one version control the configuration of a TeamCity project?

Question

In my CruiseControl instances, I have version controlled the ccnet.config file.

When I want to update CruiseControl, I run an "update config" job which fetches the config from version control.

In this manner, the very build process of a release is configuration managed.

I am wondering how to achieve these goals effectively under TeamCity.

Answer 1

You might try looking at the folders that are backed up prior to upgrade (or when restoring team city) as those represent the configurations and changes you've made since initial installation.

http://confluence.jetbrains.net/display/TCD4/TeamCity+Data+Backup

Some of the relevant data is actually a database, (and in fact the documentation advises you to point team city to a real database like mysql instead of the default embedded database it uses)

You could try checking those into SVN, but you'll want to stop team city for any check-in actions.