plans being built in sub-directory of xml-data/build-dir??

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:

was: $BAMBOO_HOME/xml-data/build-dir/COREPROJECT-TRUNK-JOB1

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??

Thanks,Dennis

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.

2 answers

1 accepted

0 vote

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.

That's it, Someone clicked "Enable". Time to revoke some admin privs :-)

Przemek:

Can you have that tidbit added to the Bamboo documentation somewhere? Also, if an agent is disabled or deleted, an Admin might like to know that the ./build-dir/<agentID> directory can be deleted to recover disk space.

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

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...

1,096 views 0 5
Read article

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot