We have two repositories where one is the main project and the other is a shared library. We want to trigger a build on a commit in branch X of both repositories but we DO NOT want teamcity to fallback to the default branch if the same branch does not exist in the other repository.
Example from documentation:
Multiple VCS roots
If your build configuration uses more than one VCS root and in both VCS roots you have specified branches to monitor, the way how builds are triggered is more complicated.
VCS Trigger groups branches from several VCS roots by the part matched by star. When some root doesn't have branch from the other root, its default branch is used. For example you have 2 VCS roots, both have default branchrefs/heads/master, first root has branch specification refs/heads/7.1/* and changes in branches refs/heads/7.1/feature1 and refs/heads/7.1/feature2, second root has specification refs/heads/devel/* and changes in branch refs/heads/devel/feature1. In this case VCS trigger runs 3 builds with revisions from following branches combinations:
We don't want the third case to happen, instead the build should not run at all.
Is this possible?