Feature Request - Isolate Project Build Settings to a Single Branch for Testing
Answered
I have been testing out some configuration changes to our project build, and unfortunately this results in some switching back and forth between settings. Since the project settings affect each branch build within the project, my changes are impacting others on my team.
It would be awesome to be able to designate a code branch as a test branch and save the edited project configuration in test mode so they were only run against my test branch. Switching to live mode would then apply the changes to all branches within my project.
Please sign in to leave a comment.
Hi,
I'm not entirely sure that I understand your scenario, but it seems like it would be covered by having the settings stored in version control and using different settings in different branches? This already exists, even though it presents some limitations: https://blog.jetbrains.com/teamcity/2018/01/branch-specific-settings-in-teamcity/
We are working on improving this functionality further mainly by working over the limitations and being able to just have that in the scope of this issue: https://youtrack.jetbrains.com/issue/TW-45912
The other typical workaround would be to simply create a copy of the project and use it in some sort of sandbox for yourself.
If that doesn't cover what you are looking for, I'd like to ask whether you can explain your scenario a bit further, or maybe add an example, as I'm not exactly sure I understand it entirely. Also, we handle feature request in our issue tracker (linked above) rather than the forums. If you consider that this feature would not be covered enough with the suggestions above, feel free to open the request there.