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?
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
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