Too many workspaces generated with Jenkinsfile causing out of disk space

[Øyvind Harboe]

I'm having problems with too many workspaces being created on nodes with my Jenkinsfile pipeline script. Our workspaces are sometimes so large that we have to carefully manage how many workspaces we create for a job by tweaking the number of executors on a slave.

I think the problem occurs as follows(we're running Jenkins 1.647):

1. A job receives a stop signal, but keeps on running for a while until the stop signal is fully processed.
2. A new job is started on the new slave and since the workspace from #1 is not free, a new workspace is created on the new slave

If jobs take a long take to stop after receiving a stop signal, we could end up with a very large number of workspaces for that job.

Is there a way to tell Jenkins wait instead of creating additional workspaces?

I.e. if I have 2 executors on a slave and the job is called 'somejob', then I never want to see "somejob@3".


Cheers,

[Øyvind Harboe]

Strike that. I see what's going on in my code now. To make a long story short, Jenkins is working correctly and I'm getting what I ask for.

Essentially I've got something like the below, which results in multiple 'foo' workspaces('foo', 'foo@2' and 'foo@3'), which is the expected and correct behaviour of the Jenkins 'ws' step.

node('someslave') {
    ws('foo') {
        ws('foo') {
            ws('foo') {
            }
        }
    }
}

 

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/mAYEPNxBNt8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/21008621-213e-4df3-a5c8-681e4ae42ac7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Øyvind Harboe