Re: Workspace cleanup after job removal

[Simon Wiest]

Hi Bertrand,

Jenkins does not explicitly delete the workspace of a job when deleting 
the job.

But if your job happens to reside on the master and your workspace 
happens to reside within your job directory (this is the default), 
deleting the job will also remove its workspace implicitly.

If your workspace resides on a slave or outside your job directory, 
Jenkins will not delete it. I guess, this would be also tricky to 
implement: First, it would require Jenkins to keep a list of all slaves 
that have ever built that very job. Second, a slave might be off-line 
during job removal. What would happen with the workspace on this slave 
then? Will it be deleted, when the slave comes on-line again?

Sorry, no extended magic here - yet ;O).

Cheers,
Simon.
--
Jan Seidel (16.05.2012 14:26):
Weird.

I know only about this issue if more than one workspace is available.

Am Mittwoch, 16. Mai 2012 13:02:42 UTC+2 schrieb Bertrand Renuart:

    I’m talking about DELETING the job through the UI on master.

    In this case, the corresponding workspace remains on our single slave.

    *From:*jenkinsci-users@googlegroups.com
    <mailto:jenkinsci-users@googlegroups.com>
    [mailto:jenkinsci-users@googlegroups.com
    <mailto:jenkinsci-users@googlegroups.com>] *On Behalf Of *Jan Seidel
    *Sent:* mercredi 16 mai 2012 10:21
    *To:* jenkinsci-users@googlegroups.com
    <mailto:jenkinsci-users@googlegroups.com>
    *Subject:* Re: Workspace cleanup after job removal

    Hi Bertrand,

    I am a bit confused. Are you talking about DELETING the job itself
    and the workspace remains or after spawning a build job?
    If you delete a job in Jenkins should everything be gone.
    There is a plugin called Jenkins Workspace Cleanup Plugin
    <http://updates.jenkins-ci.org/download/plugins/ws-cleanup/> to
    clean the workspace before or after a build job.

    Take care
    Jan

    Am Montag, 14. Mai 2012 16:44:53 UTC+2 schrieb Bertrand Renuart:

    Dear all,

    After some investigations, it appears Jenkins doesn’t cleanup a
    job’s (latest) workspace after the corresponding job definition is
    removed.

    Is it on purpose or is there any configuration parameter I could
    tweak to enable such workspace garbage collection ?

    Thanks for your advices,

    /Bertrand