Build configuration parameter change causes all branches to build
Answered
Since updating to 10.0.4 I have a problem where if I change a parameter (that is used in a branch name) it triggers all branches to build (100+ builds) for that configuration.
In the Build Queue all builds say there were triggered by "VCS Trigger".
So I have a System Property "system.
+:feature-*
+:fix-*
+:hotfix-*
+:dev
+:release-%system.MajorMinorVersion.Release%
+:master
Each time I change this parameter for a release everything builds and I have to manually cancel them in the build queue.
Any help would be appreciated :)
Please sign in to leave a comment.
Hi Josh,
I have also checked in 10.0.4 and could reproduce your issue. Could you confirm whether this wasn't happening in previous releases (and on which one)?
When the VCS trigger conditions themselves are changed, TeamCity stores the current state of changes as a baseline to wait for new changes to be built, but because you aren't changing the VCS Trigger but only a parameter, this baseline isn't saved and thus you get the behaviour you are experiencing.
The workaround for it would be to use the value instead of the property, and changing it in the trigger instead of/additionally to changing the parameter.
Could you please report this as an issue in our tracker here? https://youtrack.jetbrains.com/issues/TW
Thank you
Hi Denis,
No, this wasn't happening before, we've been using this method for about 2 years. I believe it was working correctly on 10.0.2.
Hard coding the value in the filter won't be ideal as we are using it in multiple places. Should be ok for the short term though.
No problem: https://youtrack.jetbrains.com/issue/TW-48319
Thank you for your help :)