Hi, I've set it to 20 builds now - the artifacts will be now only kept for the last successful build, so space wise that's ok.
At our (work) project, we usually only keep the last 3 release builds (marked as not removable) and the last 2-5 builds. I've picked 10, so the graphs look a bit nicer. For a busy project, I would also recommend something like a 4 hours interval, because I don't like it when it immediately starts after a commit and one has a dependency to another commit (... or a database update). Any committer can start the build, if he (she?) think it's reasonable and as we currently only do occasionally commits, the midnight-rule somehow fit's better to the "nightly builds" term. And now to something completely different: I'd like to draw your attention to two questions, which are already a bit older: - http://thread.gmane.org/gmane.comp.jakarta.poi.devel/25514 - http://thread.gmane.org/gmane.comp.jakarta.poi.user/20086/focus=20104 I'm interested in what you think. Best wishes, Andi On 30.12.2013 20:25, Dominik Stadler wrote:
Hi, I wondered about the same when I looked at the Jenkins builds, I think there is a fairly high limit of max disk space on a Jenkins Job overall, I think I read about 10G somewhere, but not sure. I saw that you set it to 10 latest builds only, no limit on days, I would probably keep it a bit longer as we sometimes have broken builds for a few days and then it might be useful to be able to compare to previous runs... Also the SVN check could be done more than daily or midnight to have quicker feedback on broken builds, what about hourly with some wait time (Extended Job Option, "Ruheperiode" in german) so multiple checkins are collected into one build? Thanks... Dominik.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
