|
A dream implementation for this would be a configurable build file(s) cleanup strategy with options like:
1) "remove build files before every build". Every build will be a clean full checkout build. When the build files are removed based on the above options, set a piece of metadata to indicate this build was a clean full checkout build. Thanks! Folks,
This should now be possible through a checkbox. Bamboo will add repository.common.cleanCheckout=true to the customDataMap for each clean build. I've created BAM-2387 to track more complex conditions for clearing but if a clean build has occurred. 2.0-beta7 which should be out next Tuesday. Mark C Hi guys,
This feature is now officially released in Bamboo 2.0! For more information about the release, check out our release notes You can download the latest release here Regards, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I also like the peace of mind of clean full checkout daily builds. For this to be really useful, Bamboo will need to collect the source control changes between the previous clean build and the current clean build. Currently Bamboo does not capture source control changes when the build files are manually removed.
BAM-1356was raised as improvement to collect build changes for full checkout/clean builds.