Multibranch Pipeline job creating multiple Checkout Directories in Workspace

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Multibranch Pipeline job creating multiple Checkout Directories in Workspace

Ven H
Hi,

I have a Multibranch Pipeline job setup for SVN. In Trunk, I have a directory called Platform which has a Jenkins file. The workspace structure is something like Drive\Workspace_Dir\trunk%2FPlatform.

After a few builds, I can see some strange things happening with this.
The Workspace_Dir has these many directories now.

trunk%2FPlatform
trunk%2FPlatform@tmp
trunk%2FPlatform@2
trunk%2FPlatform@2@tmp
trunk%2FPlatform@3
trunk%2FPlatform@3@tmp
trunk%2FPlatform@4
trunk%2FPlatform@4@tmp
and so on...

Although, this doesn't always happen, it happens every now and then. I am not sure of the reason and would like to fix this. Can anyone please help me with this? Because of this, the drive itself runs out of space sometimes, since the code base is very large.

 
Regards,
Venkatesh

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28eqrWwCPnD2NmZ5kgxYsLweYnpUQHHhrZOvw4ZMKNbEfmw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Multibranch Pipeline job creating multiple Checkout Directories in Workspace

Björn Pedersen
This standard behaviour if jobs run in parallel. The first run uses:
trunk%2FPlatform => the workdir for the job
trunk%2FPlatform@tmp => the checkout for the Jenkinsfile to set up the job.

the @n dirs are created for further parallel runs. 

Björn


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5219e400-ad91-48c8-ac50-dd9f81767c3bn%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Multibranch Pipeline job creating multiple Checkout Directories in Workspace

Ven H
Thanks a lot. Can you please advise on how to stop / control this behavior?

Regards,
Venkatesh


On Thu, Aug 20, 2020 at 3:34 PM 'Björn Pedersen' via Jenkins Users <[hidden email]> wrote:
This standard behaviour if jobs run in parallel. The first run uses:
trunk%2FPlatform => the workdir for the job
trunk%2FPlatform@tmp => the checkout for the Jenkinsfile to set up the job.

the @n dirs are created for further parallel runs. 

Björn


--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5219e400-ad91-48c8-ac50-dd9f81767c3bn%40googlegroups.com.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPp28eo7h-dRd6K1BvLGGMZgWhWS9i%2BOXsBspTOkrB-mu-iOGA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Multibranch Pipeline job creating multiple Checkout Directories in Workspace

Anton Shepelev
In reply to this post by Björn Pedersen
Bjorn Pedersen to Ven H:

> > I have a Multibranch Pipeline job setup for SVN. In
> > Trunk, I have a directory called Platform which has a
> > Jenkins file. The workspace structure is something like
> > Drive\Workspace_Dir\trunk%2FPlatform.
> >
> > After a few builds, I can see some strange things
> > happening with this.  The Workspace_Dir has these many
> > directories now.
> >
> > trunk%2FPlatform
> > trunk%2FPlatform@tmp
> > trunk%2FPlatform@2
> > trunk%2FPlatform@2@tmp
> > trunk%2FPlatform@3
> > trunk%2FPlatform@3@tmp
> > trunk%2FPlatform@4
> > trunk%2FPlatform@4@tmp
> > and so on...
>
> This standard behaviour if jobs run in parallel.

Does the official documentation tell about it, or is it
considred an internal part of the implementation?

Ven H:

> Can you please advise on how to stop / control this
> behavior?

Try limiting the number of executors to unity.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20200820162541.e1737ad14f672cc5e2e656b5%40gmail.com.