Why Artifact Copier executed for multiple build tasks in the same job

Bamboo 4.2

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?

1 answer

Hello,

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?

regards,

Can you confirm none of these are the final tasks?

unfortunately, I deleted the old plan. the job configuration is simple, three tasks:

# Source code checkout (git)

# Maven 3.x goal as "versions:use-latest-release"

# Maven 3.x goal as "clean package"

yes, none of them are defined as final tasks.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

287 views 0 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you