Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Artifact handler question

I have a remote agent that I want to generate 2 artifacts. One, A,  is very large that I want to store on the remote agent. The second, B, is small and is needed by a local agent on the bamboo server as input to another build. So, if I enable the Agent-local artifact handler for the plan, A and B will stay on the remote agent, but will the server be able to get B since another plan has it as a depedency?

If not, is there another way to do this? (Artifacts A and B need to be generated from the same version in the repository)



1 answer

0 votes

Hi Terry,

If you store the artifacts only on the remote agent, it will be available only for plans running on this agent.

Is artifact A also shared? What you can try is to keep non-shared artifacts on agent's environment and move only the shared ones to the server or to an S3 Bucket.

The following documentation exemplifies some use-case scenarios that I'm sure will help you to understand how this feature works:

Let us know if you have any other question.


Thanks for your reply.

A is also shared so it can be used by a deployment. I looked at the link previously, but I found it confusing. It didn't seem my use-case was covered. What I did to work around this was to create an intermediate plan that runs on the remote agent that has remote and agent-local enabled. The plan simply downloads B and then publishes it as a new artifact. I think the root issue is that you cannot control how each individual artifact it managed, its all or nothing.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

223 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you