Bamboo OnDemand Artifacts Directory

I've currently configured a plan to publish artifacts as part of a build phase on our OnDemand config. However, the artifact directory that the build agent tries to publish to doesn't exist:


There is no /data/jirastudio structure. I found the following post referring to configuring artifact directories:

However, when inspecting the bamboo-agent.cfg.xml upon SSH'ing into the EC2 instance, any changes to that file are always overwritten after the bamboo agent starts.

Interestingly, the buildWorkingDirectory is valid and appears to be generated during the elastic-agent startup, however, no artifacts directory entry is created mimicing the /home/bamboo/bamboo-agent-home directory structure. How can I feed the appropriate artifacts directory path to the elastic agent?

1 answer

1 accepted

0 votes
Accepted answer

/data/jirastudio artifact directory is located on the server, not on the agent.

Thanks! I was a bit confused by some of the labeling around those values. Got artifacts working, but ran into the git issue.

Would be nice to have a way to turn off that the Ant default exclude patterns via a bamboo config setting or just by default.

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

498 views 2 5
View question

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