So we're using artifactSubscriptions as defined in the bamboo spec docs.
The problem we're having is that whenever we publish that plan to bamboo it adds that artifactSubscriptions a new artifact dependency every time even if there's been no changes to that artifact dependency.
This leads to duplicate entries in our artifact dependencies and can have an effect on runtimes.
I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...
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