I take it you have thought about the obvious - but just incase I will restate it.
Use a clean workspace each time. I actually consider this good practice as it will remove any crud that bad code/tests etc has left behind. /James From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Øyvind Harboe Sent: 13 December 2013 15:41 To: jenkinsci-users@googlegroups.com Subject: Problems with Gerrit not aborting jobs cleanly I'm having problems with Gerrit and Jenkins in combination not aborting jobs in a nice manner(*). This causes followon jobs to see a corrupted workspace and then these subsequent jobs fail. I want to enable the "Build Current Patches Only" which will get rid of queued jobs that are no longer necessary to build because there is a more recent patches, thus improving throughput. However, the problem is that "Build Current Patches Only" also aborts currently running jobs and therefore I'm tripped over by JENKINS-17116. Any idea on how this could be addressed? Ideally, I'd like JENKINS-17116 to be fixed, but it would help *greatly* if I could tell the Gerrit trigger not to abort jobs that have already started. (*) This is a known problem: https://issues.jenkins-ci.org/browse/JENKINS-17116 -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com<mailto:jenkinsci-users+unsubscr...@googlegroups.com>. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
