![]() ![]() On changing the ID of a project or build configuration, all the related URLs (including the web UI, artifact download links, and REST API) will change. 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. It is recommended to leave the automatically generated IDs as is unless there are special considerations to modify them. In file and directory names under /system (for example, build artifacts storage).īy 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. In the configuration files storing settings of projects and build configurations under /config In REST API and build scripts used to automate actions with TeamCity (for example, download artifacts via direct URLs or Ivy) In URLs of the web interface (including the NuGet feed), for example, IDs can contain only alphanumeric characters and underscores ( _) - maximum 80 characters - and should start with a Latin letter. Build configurations and templates share the same ID space. The so-called external identifiers are configured in the TeamCity web UI (for example, Project ID) and must be unique within all the objects of the same type on the entire server. An ID is an identifier given to TeamCity entities ( projects, build configurations, templates, VCS roots, and so on).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |