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 6 Next »

You are viewing documentation of TeamCity 6.x, which is not the most recent released version of TeamCity. Please refer to the listing to choose another version.

Table of Contents

This page is being developed and subject to change.

When reading POM data and and resolving artifact in an artifact trigger, TeamCity uses both global and user-level Maven settings.

  The license could not be verified: License Certificate has expired!

TeamCity looks for the global settings in the following location:

${env.M2_HOME}/conf/settings.xml (or ${system.maven.home}/conf/settings.xml)

For user-level settings TeamCity searches the following locations (listed in order of priority):

1. ~/.BuildServer/system/pluginData/maven/settings.xml
2. ~/.m2/settings.xml

where ~ denotes the user home directory.

To resolve artifacts, Maven artifact trigger should know repositories to look at.
If Maven artifact trigger is configured for a non-Maven build configuration, then it reads repository from locally stored settings obtained the way described earlier for POM reading.
Otherwise, the trigger takes repository list from the corresponding POM.

See also: