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.
Hi,
This issue was solved in Bamboo 6.1.0 - https://jira.atlassian.com/browse/BAM-18489
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.