Re: Do not delete a completed job workspace under all conditions

2016-09-07 Thread Robert Beddow
Hi, Thanks for the replies. I managed to come up with a solution using the pre-scm plugin. It checks for a file before proceeding. Note, the reason I need this is that my jenkins jobs kick off synthesis jobs which can take >24hrs to complete. These jobs continue even if Jenkins falls over for

Re: Do not delete a completed job workspace under all conditions

2016-09-01 Thread Michael Lasevich
Workspaces are meant to be ephemeral and can be deleted/removed at any time. Counting on same workspace being there for every build is a bad idea for many reasons - not the least of which is that the point of using a build system like Jenkins is to have a reliable and repeatable build - if you

Re: Do not delete a completed job workspace under all conditions

2016-08-30 Thread Martin d'Anjou
On Thursday, August 25, 2016 at 11:15:43 AM UTC-4, Robert Beddow wrote: > Is there anything like this out there? Or does anyone have any suggestions > of how else I could get the functionality I'm looking for? > Yes, you can try the External Workspace Manager Plugin

Re: Do not delete a completed job workspace under all conditions

2016-08-30 Thread Baptiste Mathus
You should treat the workspace filesystem as an internal thing for Jenkins IMO. Archiving artefact is one feature to express the things you wanna keep. If you want to keep a directory structure for later reuse, maybe you could either zip it and archive it. Or push it somewhere else at the end of

Do not delete a completed job workspace under all conditions

2016-08-25 Thread Robert Beddow
Hi, I'm trying to find a way to keep a workspace and prevent it from being deleted by Jenkins. If I have a project called My_Jenkins_Job, and I run it multiple times concurrently, I end up with directories in the form: ./jenkins/workspace/My_Jenkins_Job ./jenkins/workspace/My_Jenkins_Job@2 ./j