- if you keep TeamCity configuration files in the same VCS root as your project source code, you can now start remote run/pre-tested commit with changes made in the
.teamcitydirectory, and these changes will affect the build behavior
- if you are using TeamCity feature branches, you can define a branch specification in the VCS root used for versioned settings, and TeamCity will run a build in a branch using settings from this branch
- if you're starting a history build, TeamCity will try to use the settings corresponding to the moment of the selected change.
Note: Before starting a build, TeamCity stores configuration for this build in build internal artifacts under
.teamcity/settings directory. These configuration files can be examined later to understand what settings were actually used by the build.
Currently there are some limitations, which we hope to overcome in the future: