Menu
When I create a new branch B from branch A and do a single commit, TeamCity triggers multiple builds on B, although I would expect just a single build.
I set "Trigger a build on each check-in" to true, but nevertheless there should only be a single build because there is only one new commit.
It seems that TeamCity triggers a build for each commit within the current month.
All builds of branch A finished and the same build configuration is used to build branch A and B.
Can I configure TeamCity to create builds just for the commits that haven't been built (no matter on which branch)?
735
To run a custom build with specific changes, open the build results page, go to the Changes tab, expand the required change, click the Run build with this change, and proceed with the options in the Run Custom Build dialog. Use HTTP request or REST API request to TeamCity to trigger a build.
VCS triggers automatically start a new build each time TeamCity detects new changes in the configured VCS roots and displays the change in the pending changes. Multiple VCS triggers can be added to a build configuration.
A VCS root in TeamCity defines a connection to a version control system. It represents a set of parameters (paths to sources, username, password, and other settings) that determine how TeamCity communicates with a VCS to monitor changes and get sources for a build.
It looks like you faced with this issue. As current workaround please try to set
teamcity.vcsTrigger.runBuildOnSameRevisionInEveryBranch=false
You can set it either as a parameter in build configuration - to affect a particular build configuration, or in internal.properties file to affect all build configurations.
184
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
