Template's VCS Root Being Applied Everywhere?
I currently have a project with three jobs. Two of them inherit from a template and one of them does not. Strangely, the one that is not based on the template nonetheless inherits a VCS root configuration from it despite not being attached and their being no option to detach it.
The UI for the non-templated job looks like this:
Every new job that I create also inherits a VCS root from the template.
How can I fix this without deleting the template?
Please sign in to leave a comment.
Success!
It turns out that if you have a template set as a default for a project it is applied to all jobs – I assumed that the default was simply automatically attached to all newly created jobs. Removing it as the default fixed the project.
My love for TeamCity is only be matched by my hatred of its UX.
Hi Myles,
As you experienced, default templates are thought to be applied to all configurations on that project. In fact, when you select a default template, it even specifies that below the selector: "The template will be attached to all build configurations in this project and its subprojects unless redefined in a subproject."
There is another option, if you still want to share template configuration for all builds via default-template but not use the VCS Root in all. Simply remove the VCS Root from the template but keep it at the project, then add it to every build configuration that needs it, or to a non-default template that the other builds can be attached to.