I have a job that has a dependency on a previous job that defines an artifact. If I disable the previous job, the subsequent job will fail because the artifact is not generated. Is there a way to allow the subsequent job to notice when the previous job is disabled and skip the requirement for its artifact to exist?
For the second job that has a dependency on a previously generated artifact, you should be able to skip the artifact checking stage by navigating to the Artifacts tab for this job and edit or delete the artifact dependencies that you have created for it. This way, it won't be dependent on the artifact created by the previous job that you have disabled, so the build won't fail because of it.
I hope this helps and I understood your question correctly.
Thanks Sepideh. While that solution will work, it's a bit manual for my clients' liking. Suppose they have a plan with multipe jobs. If they disable a job then they will have to manually crawl through all the downstream jobs and delete the checks for any artifacts that job produced. Then, if the original job is re-enabled, someone has to go back and put that artifact check back into those downstream jobs. That's assuming you even know that there is an artifact dependency on those jobs since the plan's audit log does not keep track of the deletion of shared artifacts.
It would be nice if, artifact sharing/checking could be:
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot