I'm running Bamboo 7.0.4. I have defined my build plan as YAML specs.
The build plan is connected to multiple linked repositories hosted on Bitbucket Server. One of them is the main repository which should trigger the build. The others are checked-out to fetch some configuration files. I'm using the repository-checkout task for this.
After setting up this configuration, a commit to any linked repository will trigger a build.
Is there a way to ignore triggers of linked repositories in the YAML specs?
The YAML specs manual states (section triggers):
If your plan repository is Bitbucket Server, the Bitbucket Server trigger will be used instead.
The YAML specs manual states (section repository triggers build on commit)
On the Bamboo side, use the
triggers(new RemoteTrigger())on plan definition. By default the remote trigger will react on all triggering repositories defined in a plan. You can limit it by selecting a subset of repositories.
And on the right hand side, the YAML doesn't match this comment:
A plan listening for events from a
The manual is quite misleading. Is it currently possible to ignore triggers of linked repositories (ideally by name) in YAML specs?
G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events