Why does my build job not save artefacts on S3 under their build plan code? Edited

I have noticed that most of my build jobs save their artifacts on S3 correctly, under their build plan code and build-number. However, I have one plan - that looks exactly the same in its config (cloned) but is determined to save the artefcts on S3 in the root of the nominated bucket... it stores its one in something dynamic like "plan-110329879" very unhelpful - ... how can I fix this please?

1 answer

1 accepted

This widget could not be displayed.

https://confluence.atlassian.com/bamboo/plan-directory-information-rest-api-750396160.html

All newly created plans will have this name, unfortunately.

I don't think this is relavent. I'm talking about how Baboo uploads to S3. The REST API isn't used.

Yes, it's relevant. That's the new directory structure, you can use the REST endpoint to obtain mapping between plan keys and new-style paths.

OK, I understand better. However, why is it some plans are on way - whilst other plans work the other way? Can I reset all the plans to work one way - so any script I use on the REST API will actually work globally.

The endpoint accepts the plan key as a parameter so it will work for both types.

 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

142 views 1 3
Join discussion

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