Artifact is defined on job level, so that I was expecting artifact copier will happen once at the end of a job. However, when there are two maven tasks in the same job, and the first one does not suppose to generate artifact (i.e. use maven versions plugin to update latest dependencies), the build will fail because Bamboo will invoke artifact copier to look for not existing artifact.
Why bother invoke artifact copier for every build tasks in the same job? Shouldn't only once at the end? Am I mistaken here?
I think you had encountered some kind of bug, at least I'd expect (like you are expecting) the Bamboo to copy the artifact after the second task, not after the first task.
Maybe you can share your task configuration (screenshot), so we can check if there is something odd about it?
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