Identifier

Using External IDs

External IDs are used:

• in URLs of the web interface (including RSS feeds, NuGet feed), for example, https://teamcity.jetbrains.com/project.html?projectId=TeamCityPluginsByJetBrains;

• in the dep. and vcsRoot. parameter references;

• in REST API and build scripts used to automate actions with TeamCity (for example, download artifacts via direct URLs or Ivy);

• in the configuration files storing settings of projects and build configurations under < TeamCity Data Directory >/config;

• in file and directory names under < TeamCity Data Directory >/system (for example, build artifacts storage).

Assigning External IDs

By default, TeamCity automatically suggests an ID for an object by converting its name to match the ID requirements and prefixing that with the ID of the parent project. The ID can be modified manually.

It is recommended to leave the automatically generated IDs as is unless there are special considerations to modify them.

If you consider moving projects between several TeamCity server installations, it is a good practice to make sure that all the IDs are globally unique.

To reset the IDs to match the default scheme for all projects, VCS roots, build configurations, and templates, use the Bulk Edit IDs action on the Administration page of the parent project. To use the automatically generated ID after it has been modified or after you change an existing object name, you can regenerate ID using the Regenerate ID action.

When you copy a project, TeamCity automatically assigns new IDs to all the child elements. The IDs can be previewed and changed in the Copy dialog. When you move an object, its ID is preserved and you might want to use Regenerate ID action to make the ID reflect the new placement.