Create Maven Build Configuration
Last modified: 20 April 2023Administration > <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.
Option | Description |
|---|---|
POM file | Specify the POM file to load configuration data from. You can either provide an URL to the |
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. |
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:
Subversion: http://maven.apache.org/scm/subversion.html
Maven SCM URL Format
The general format for a SCM Url is
scm:<scm_provider><delimiter><provider_specific_part>
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://host.com/trunk/pom.xml" URL will 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.xmlThe
scmprefix can be omitted, or can be replaced withvcsprefix.
Examples of the SCM URL for Supported SCM Providers
The following URLs will be considered as equal:
Subversion:
scm:svn:svn://svn.company.com/project/trunk/pom.xml or vcs:svn:svn://svn.company.com/project/trunk/pom.xml or svn:svn://svn.company.com/project/trunk/pom.xml or svn://svn.company.com/project/trunk/pom.xmlnote
Please note that "
svn:http://svn.company.com/project/trunk/pom.xml" URL does not equal to the "http://svn.company.com/project/trunk/pom.xml".StarTeam:
scm:starteam:starteam://host.com/project/view/pom.xml or starteam:starteam://host.com/project/view/pom.xml or starteam://host.com/project/view/pom.xmlPerforce:
scm:perforce:user@//main/myproject/pom.xml or perforce:user@//main/myproject/pom.xml
Thanks for your feedback!