I have a plan using our svn trunk and another branch of that plan in which I ,manually override the repository with a svn branch.
The problem is that branch builds are being triggered whenever any change is commited to the trunk as well as to the branch. How do I make the branch plan trigger only when a change has been commited to the trunk?
This should not happen. Either you have your branch misconfigured (for example it still references trunk because you have multiple repositories defined) or you found a bug.
Are you sure you don't have duplicate repository definition on your 'trunk' plan? Please verify and if you are still convinced that you got your plan right perhaps you should contact Atlassian Support. Bug reports posted there are handled much faster ;-)
Yep, currently you can only override 1 repository (default) So if you have change detection on master plan configured to check more than 1 repo, branch will check them too.
However, in Bamboo 4.2 you have an option to override Build Strategy in Branches. Would that help?
I upgraded to 4.2, but it' still not clear how to do this. When I override the Build Strategy, it allows me to pick which repositories to poll, but includes the same repositories (sub-folders) off the trunk. Is there a way to automatically use the same folders, but have the branch as the root of these folders?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs