Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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

Tags:

teamcity

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.

like image 583
polyglot Avatar asked Jun 28 '10 21:06

polyglot


People also ask

Is TeamCity a version control?

TeamCity allows synchronizing project settings with the version control repository (VCS). Supported VCSs are Git, Mercurial, Perforce, Subversion, and Azure DevOps Server (formerly TFS).

How do I find TeamCity build configuration?

Go to Administration | Projects and open the required project. Alternatively, open the project using the Projects pop-up menu and click Edit Project Settings. The Project Settings page will open. On the Project Settings page, click Create build configuration under the Build Configurations section.

How do I disable TeamCity build configuration?

Pausing Build Configuration To remove the builds of the paused build configuration from the build queue, check the Cancel already queued builds box. Click Pause to confirm. To activate a paused build configuration, select Activate in the Actions menu.

What is build configuration ID in TeamCity?

An ID is an identifier given to TeamCity entities (projects, build configurations, templates, VCS roots, and so on). Each entity has two identifiers: external ID. Universally Unique ID, or UUID.


2 Answers

This has been introduced in TeamCity 9. Also answered in another post:

Version control (e.g. in TFS) build configuration for TeamCity - is it possible?

like image 121
Japster24 Avatar answered Nov 04 '22 07:11

Japster24


I try to keep what ever CI I am using as light as possible and put as much of the running of the build into an msbuild or nant script including running tests, code coverage, etc.

The benefit of this is:

  1. The build file is version controlled.
  2. You can run the script in any environment.
  3. Easier to move between CI environments.
  4. Everyone becomes responsible for the build.
like image 44
Bronumski Avatar answered Nov 04 '22 05:11

Bronumski