I have a job that operates on files from a shared artifact by a previous stage. The job generates new files (ruby -> Gemfile.lock).
I would assume every build starts with a clean working dir, but it looks like the generated files from the previous build are still there. How can I ensure that every build of this job automatically starts in a clean state?
Each job under the configuration -> Miscellaneous has a "Clean working directory after each build" option. Setting this option later in the process, now that you have unclean working directories, becuase is cleans the directory after the build and is a pain because you'll have to cycle through all your agents with "bad" builds to get it working. If you can spare the down-time you can clear the entire build-dir folder (in bamboo-home\xml-data) to delete all your working copies once.
This does solve the problem in case of successful build but makes it impossible to debug a failed build.
Cleaning the xml-data directory in a distributed environmen with several parralles plans is not an option (and does feel quite hacky too ;-) )
I just execute a script with the single line: "rm -R *" before anything else. This allows me to have a clean build folder before the tests, and a dirty one afterwards for analysis.
I'm really not too happy about this solution, but since there is nothing of value on the bamboo machine I don't care if it messes up
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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