A strange thing has happened to my bamboo installation.... Our builds are configured to use a common ant build file and ivy. All of our projects reference ../CoreProject/common-build.xml, and ivy has been using a similar scheme to get it's artifacts. Since version 1 we have sym-linked the bamboo name to the "real" project name, and all this has worked pretty well.
Up until recently, bamboo has been organizing my code in $BAMBOO_HOME/xml-data/build-dir. Today i notice that some of my builds started failing and our projects were suddenly being stored in a sub-directory:
is now: $BAMBOO_HOME/xml-data/build-dir/131073/COREPROJECT-TRUNK-JOB1
some projects are in still another sub-directory... Clicking around it looks like the numbers might corrspond to agent id's.
Does anyone have any insight on what might be going on here? Is this normal or do I have some corruption somewhere??
note: even though I was a "charter" bamboo user, I decided to get rid of some "upgrade cruft" by starting fresh and reinstalling Bamboo when I upgraded to 3.2 recently.
That's normal if you have concurrent builds enabled. If you disable them, you will get back to the previous layout.
If we stuck to the previous directory layout, a directory would have to be shared between two concurrent builds of the same job. So, concurrent builds -> all job directories are per agent.
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