CODEWITHSUNDEEP
continuous-integrationbamboo
Cyber
Cyber

Reputation: 75

Please explain Bamboo (Plan, Branch, and the build-dir)

So I feel like this is a pretty basic question but I'm not wrapping my head around this.

In Bamboo, how do you remove the folders in build-dir after the code has been merged? I currently have 21 directories of checked out code, with only 5 active plan branches (develop + 4 active pull request).

Also, what is with the folder names? I have PROJ-DAPP[x]-JOB1, and PROJ-SMIT[x]-JOB1 (with SMIT being from my last name, and x being various numbers or no number). I'm thinking these somehow tie to the plan name but not fully sure. (it was PROJ_SMITH, but now is PROJ_Basic)

Our setup:

Upvotes: 1

Views: 1667

Answers (1)

Wesley Rolnick
Wesley Rolnick

Reputation: 891

In Bamboo, how do you remove the folders in build-dir after the code has been merged?

Even though your setup is deleting branches and force cleaning builds, you will still get multiple folders on the system. This is because Bamboo keeps previous builds for logging and artifacts. However, you can configure how long and how many builds Bamboo keeps. The best way to do this is under settings go to Administration and then select Expiry. From here you can set how many builds your project will keep and when it will update. If you need space you can go into the build-xml folder and delete some of the older builds manually, but this may cause issues in Bamboo if you try to load logs or artifacts for that build.

Also, what is with the folder names?

The folder names are built on Plan Key, Job, and Build number. The structure and convention may vary depending on whether your build has multiple stages and plans.

Upvotes: 0

Related Questions