You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
So we're using artifactSubscriptions as defined in the bamboo spec docs.
Job.artifactSubscriptions(
new ArtifactSubscription()
.artifact(artifactName)
.destination(destination)
)
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.
Thanks!
Turns out we were behind on versions, be a while before we get an update in but thanks for the answer!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had a similar problem in later version of Bamboo - see https://community.atlassian.com/t5/Bamboo-questions/Bamboo-Duplicate-entries-for-produced-artifacts/qaq-p/1567472 for details
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.