The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have a multi stage YAML spec. 4 artifacts are defind in job 1 of stage 1 - Compile (Debug).
In stage 2 job one I want to pull down 2 of the 4 artifacts, sln and backend.
This YAML parses fine and the plan is created.
You can see the artifact download task correctly defining the 2 artifacts I specified
However, all artifacts are registered to be downloaded at the job level. Both frontend and source are incorrectly defined here.
At run time, you can see bamboo processing both the job artifacts and the task.
How do you stop a job from registering the artifacts if using the artifact-download task?
Sorry, I have no answer, but have you resolved this?
Any response from Atlassian would be appreciated, because we see the same on Bamboo 6.10.4!
We did not find a solution. Unfortunately we halted our configuration as code project. To date we can only use yaml for very basic plans.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.