Hi,
Sorry, I completely forgot to respond.
I'm not sure if there is an existing reported JIRA bug for this.
https://issues.jenkins-ci.org/browse/JENKINS-15331
Not sure when this fix was release. It does seems like we are running with
it according to the exception it throws. I recall getting a di
fredag 12. oktober 2018 13.35.36 UTC+2 skrev Andreas Tscharner følgende:
>
> Hi Sverre,
>
> On 11.10.2018 09:33, Sverre Moe wrote:
>
> [snip]
> > Is there some other means I can make sure that the build has a clean
> > workspace?
>
> Our Windows agents are virtual machines that get reset to a
I will see if I can find some more information about the problem.
torsdag 11. oktober 2018 10.02.54 UTC+2 skrev Baptiste Mathus følgende:
>
> What is the JIRA number number for the Windows deleteDir() bug you say
> you're seeing?
>
> Le jeu. 11 oct. 2018 à 09:33, Sverre Moe >
> a écrit :
>
>> T
Hi Sverre,
On 11.10.2018 09:33, Sverre Moe wrote:
[snip]
Is there some other means I can make sure that the build has a clean
workspace?
Our Windows agents are virtual machines that get reset to a certain
snapshot to make sure they are clean.
Best regards
Andreas
--
Andreas Tscharn
What is the JIRA number number for the Windows deleteDir() bug you say
you're seeing?
Le jeu. 11 oct. 2018 à 09:33, Sverre Moe a écrit :
> This deleteDir() does not always work on a Windows build slave.
>
> Using Scripted PIpeline I am declaring a node within try-catch-finally.
> The finally wil
This deleteDir() does not always work on a Windows build slave.
Using Scripted PIpeline I am declaring a node within try-catch-finally.
The finally will run deleteDir(), in order to delete the build workspace.
This is done in order to get a fresh build each time. I cannot risk having
stale data
