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:
/data/jirastudio/bamboo/home/artifacts/BR-STGF/shared/build-00003
There is no /data/jirastudio structure. I found the following post referring to configuring artifact directories:
https://confluence.atlassian.com/display/BAMBOO/Moving+Bamboo-Home+of+an+agent
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?
/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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.