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?
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.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot