Parameter inheritance
Answered
We've defined multiple parameters in the Root project. Furthermore we've defined a build configuration template within one of our projects. In this template, we've overridden some of the parameters from the Root project. When using the config template as base for an actual configuration, however, the parameters are inherited from Root project rather than from the template. Is this by design?
I would have expected that overriding parameters would be using a "closest parent" logic, i.e. first check if the parameter was overridden in the template and if not, fallback to the value defined in the Root project.
Please sign in to leave a comment.
Hello Magnus,
Our documentation covers this scenario (see case 2 in this article: https://www.jetbrains.com/help/teamcity/project-and-agent-level-build-parameters.html#Project+Level+Build+Parameters). However, I do agree that inheriting the parameter value from the template would be more intuitive in this case.
We have a usability issue registered as https://youtrack.jetbrains.com/issue/TW-63091 on our tracker - would you mind to vote/comment on the issue? I have also left an internal reference on the tracker to this request, so that the developers are aware of your case.