Further to the above.
I just forced it to run multiple builds simultaneously, and it generates
new folders for them as pipeline-test2@2 and pipelin-test2@3.
So the @ symbol is most certainly not the issue.
On Sunday, December 11, 2016 at 7:23:01 PM UTC, Jonathan Hodgson wrote:
>
>
>
> On Sunday
On Sunday, December 11, 2016 at 4:36:24 PM UTC, Daniel Beck wrote:
>
> Is this a file system that doesn't like the @ character?
>
Seems unlikely, since
1) I created the folder manually without issue (and then things worked
correctly)
2) Jenkins previously created those folders just fine, this
Is this a file system that doesn't like the @ character?
Set the system property hudson.slaves.WorkspaceList to e.g. _ to use a
different separator as described on
https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties
> On 11.12.2016, at 14:30, Jonathan Hodgson
>
> Ok, adding to the confusion...
>
I just tried changing the slave configuration to give a compleely new root
folder (C:\Jenkins2 rather than C:\Jenkins)
Ran the same same job
Failed to mkdirs: C:\Jenkins2\workspace\pipeline-test2
hudson.FilePath.mkdirs(FilePath.java:1169)
org.jenkinsci.plu
I tried a couple of experiments today.
Launching a cmd windows as an administrator and running the slave from
there... no difference.
Manually created the pipeline-test2@tmp directory - build was successful
Deleted both pipeline-test2 and pipeline-test2@tmp and ran build - jenkins
recreated pi
Hi,
I've been experiementing trying to get some information which might give a
clue to the issues I'm having with my Windows slave.
It's rather confusing, since to start with it worked fine. and the errors
aren't consistent (looking for past logs I see an error with unstashing
which I don't se
