Maven

Maven Settings

Choose the Maven version you want to use.

User Settings

Specify what kind of user settings to use here. This is equivalent to the Maven command-line option -s or --settings. The available options are:

Java Parameters

Local Artifact Repository Settings

Select one of the following options:

Incremental Building

Select the Build only modules affected by changes checkbox to enable incremental building of Maven modules.
The general idea of incremental building is to process only changed modules without spending time on reprocessing unchanged modules they are connected with. TeamCity utilizes this method to run tests only for changed Maven modules thus saving time when rerunning a build or a build chain.

Since Maven itself has very limited support for incremental builds, TeamCity uses its own change impact analysis algorithm for determining the set of affected modules and uses a special preliminary phase for making dependencies of the affected modules.

First TeamCity performs own change impact analysis taking into account parent relationship and different dependency scopes and determines affected modules. Then the build is split into two sequential Maven executions.

The first Maven execution called preparation phase is intended for building the dependencies of the affected modules. The preparation phase is to assure there will be no compiler or other errors during the second execution caused by the absence or inconsistency of dependency classes.

The second Maven execution called main phase executes the main goal (for example, test), thus performing only those tests affected by the change.

Also, check the related blog post on the topic.

Docker Settings

In this section, you can specify a Docker image which will be used to run the build step.

Code Coverage

The Maven build runner supports code coverage based on the IDEA coverage engine. To learn about configuring code coverage options, refer to the Configuring Java Code Coverage page.

If you have several build agents installed on the same machine, by default they use the same local repository. However, there are two ways to allocate a custom local repository to each build agent:

• Specify the following property in teamcity-agent/conf/buildAgent.properties:

  system.maven.repo.local=%system.agent.work.dir%/<subdirectory_name>

  For instance, %system.agent.work.dir%/m2-repository.

• Run each build agent under different user account.

Using Maven Release with Perforce

The Maven Release plugin needs a ticket to authenticate in Perforce.

In the Perforce VCS root settings of your build configuration in TeamCity:

1. Enable the checkout on agent.

2. Enable Use ticket-based authentication in Perforce VCS root settings.

3. Make sure your build agent environment doesn't have any occasional P4 variables which can interfere with the execution of Maven Release Plugin.

4. Specify release:prepare in the Goals field of the Maven build step and run the build.

Using Maven Release with Git VCS

To use this plugin with Git, set a Git SSH URL as SCM URL in your pom.xml.

On the TeamCity agent:

1. Make sure the agent has Git installed and added to the agent's $PATH on Unix-like OS's and to the %PATH% environment variable on Windows.

2. On the agent, set your account's identity by executing

   git config --system user.email "buildserver@example.com" git config --system user.name "TeamCity Server"

3. Make sure your Git VCS is added to the known hosts database on the agent.

On the TeamCity server:

1. Upload a Git SSH key to your TeamCity server.

2. On the Build Configuration Settings | Version Control Settings page, enable the checkout on the agent.

3. In your Git VCS root, enable Private Key authentication.

4. Add the SSH Agent build feature to your configuration.

5. Specify release:prepare in the Goals field of the Maven build step and run the build.