Unable to render embedded object: File (TeamCity48.png) not found.

TeamCity 9.x Documentation

Documentation for Previous Versions

Icon

You are viewing the documentation of TeamCity 9.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

 
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

TeamCity provides several ways to create a new build configuration for a project. You can:

Creating New Build Configuration

  1. On the Administration > Projects page, select the desired project in the list. (Alternatively, select the project from the Projects popup, and click the Edit Project Settings link on the right). On the project settings page, click Create build configuration.
  2. Specify general settings for the build configuration, click Create.
  3. Proceed with creating other settings:

Creating New Build Configuration from URL

Since TeamCity 9.1, you can create a build configuration using a VCS URL:

  1. On the project settings page, click Create build configuration from URL.
  2. Specify settings for the build configuration, click Create.

Creating Build Configuration Template

Creating a build configuration template is similar to creating a new configuration. On the Project settings page, click the Create template button and proceed with configuring general settings, VCS settings and build steps.

Alternatively, you can create a build configuration template from an existing build configuration using the Extract Template option from the Actions menu at the top right corner of the screen.


Creating Build Configuration From Template

To create a build configuration based on a template:

  1. On the Project settings page locate the desired template and click its name or use Edit.
  2. Click the Create Build Configuration button available from the Actions button at top right corner of the screen.
  3. Specify a name for the new configuration.
  4. The settings set up in the template cannot be edited in a configuration created from this template. However, some of the can be redefined in a build configuration. Note that modifying the settings of the template itself will affect all configurations based on this template.

Alternatively, you can create a build configuration based on a template by clicking Create build configuration and selecting a template from the Based on template drop-down on the configuration settings page.


Creating Maven Build Configuration (Depricated)

Icon

Deprecated. Since Teamcity 8.1, use the create project from url option.

To create a new build configuration automatically from the POM.xml file, on the Project settings page click Create Maven build configuration.
Specify the following options:

Option

Description

POM file

Specify the POM file to load configuration data from. You can either provide an URL to the pom.xml file in a repository or upload pom.xml file from your local working PC. The URL to the POM file should be specified in the #Maven SCM URL format.

Username

Username to access the VCS repository.

Password

Password to access the VCS repository.

Goals

Provide goals for the Maven build runner to be executed with the new configuration.

Triggering

Select the check box to set automatic build triggering on snapshot dependency.

Icon

TeamCity reads the name and the VCS root URL parameters for the new build configuration from the provided POM file. For non-Maven projects, if there's no VCS root URL provided in the pom.xml, then the process will be aborted with an error.

When a new Maven configuration is created, any further configuring is similar to editing an ordinary build configuration.

Refer to Maven documentation on the SCM Implementation for the following supported version control systems:

Maven SCM URL Format

The general format for a SCM Url is

As a delimiter, use either a colon ':' or, if you use a colon for one of the variables (for example, a windows path), you can use a pipe '|'.

For more information, refer to the official Maven SCM documentation page.

In TeamCity you can use simplified SCM URL format:

  • If the protocol defined in the provider-specific part unambiguously identifies the SCM-provider, then the scm:<scm_provider>: prefix of the URL can be omitted. For instance, the "scm:starteam:starteam://host.com/trunk/pom.xml" URL will be valid in the "starteam://host.com/trunk/pom.xml" format. In any other case, for example if HTTP protocol is used for SVN repository, then the SCM-provider must be specified explicitly:
    svn:http://svn.host.com/trunk/project/pom.xml
    
  • The scm prefix can be omitted, or can be replaced with vcs prefix.

Examples of the SCM URL for Supported SCM Providers

The following URLs will be considered equal:

  • Subversion:

    Note

    Icon
  • StarTeam:
  • Perforce:

Ordering Build Configurations

You can view all build configurations of a project on the Project Overview page listed in alphabetical order by default. Starting from TeamCity 9.1, administrators can customize the default order.

Configuring Settings


Configuring settings of a build configuration is described on the following pages:



See also:

  • No labels