Skip to end of metadata
Go to start of metadata
You are viewing documentation of TeamCity 5.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.

Table of Contents

Administration > <project> > Create Maven build configuration

Create Maven build configuration dialog allows creating new build configuration automatically from the specified POM.xml file.

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



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 specified in the #Maven SCM URL format.


Username to access the VCS repository.


Password to access the VCS repository.


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


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

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

View 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 delimiter you can use either 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, please 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://" URL will valid in the "starteam://" format. In any other case, for example if HTTP protocol is used for SVN repository, then the SCM-provider must be specified explicitly:
  • 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 as equal:

  • Subversion:


  • StarTeam:
  • Perforce:

See Also: