Patterns for Developing build configurations

During normal development of any coded or configured project usually involves merging changes of some sort.  Currently I'm failing to see a good way to do this in TeamCity.  So far I've found a couple of primary ways to move a developed build configuration to a production usage.

These assume you already have a build configuration in use for production... i.e. it's not being actively modified or configured.
1.  Make a copy of the build configuration A.  We'll call the copy build configuration B.
2.  Make your changes to configuration B and test them.

Now, there are two ways to get this back to the production build.
A.  Delete build configuration A and move configuration B in.
- doing this would remove any history of configuration A.


B.  Manually, by hand, make the changed needed to configuration A.
- This seems very error prone and lends itself to a great deal of human error.

If there is a better way to do this, or anybody has any thoughts, please let me know.

1 comment
Comment actions Permalink

Hi Andy,

Unfortunately there is no good way to perform it now. At the moment the easiest way is to make changes in A build configuration manually. You can copy build step between build configurations.

Since TeamCity 9.0 the project setting can be stored in VCS. In the future this feature should help to solve this problem. Please create a new feature request in our tracker.


Please sign in to leave a comment.