Maven Server-Side Settings
The TeamCity server invokes Maven on the server side for functionality like Maven dependency triggers and the Maven model display on the Maven build configuration tab.
You can upload Maven settings using the Maven Settings tab of project settings, and then select one of the uploaded settings on the Maven step settings.
During the process, TeamCity uses the usual Maven logic for finding the settings.xml files with several differences (see below).
Maven global-level settings are used from the .xml file in the default Maven location for the TeamCity server process: ${env.M2_HOME}/conf/settings.xml or ${system.maven.home}/conf/settings.xml.
The global values of M2_HOME environment variable and maven.home JVM option are used set for the TeamCity server process.
Maven user-level settings are defined in the User settings selection section of the Maven build step of the build configuration (if there are several Maven steps, settings from the first one are used).
The following options are available:
Value | Description |
|---|---|
<Default> | TeamCity searches the following locations for the
|
<Custom> | The path to the file is provided by user. The file should be available both on the server and all the agents where the build will be run. |
Uploaded settings name | TeamCity automatically uses the specified file content both on the server and agents. Maven settings are defined on the project level: the Project Settings | Maven Settings tab. The settings are stored in the
|
For the logic of Maven settings, refer to the related Maven documentation.
User-level settings can be configured in the Maven Artifact Dependency Trigger.