Hi, This is a follow on from a previous thread, where I thought the issue was specifically tmp folders, but now after a little experimentation, things are a bit clearer.
Firstly, I want to state that this problem did not originally exist on this slave, SOMETHING (not the pipeline code) has changed. Whether that is Jenkins itself, or something on the slave (I've tried turning off malware protection in case I inadvertantly changed settings on that). This also only happens on one of my windows machines, running windows 7, when I run my laptop (windows 10) as the slave, it works ok. Anyway, what I have found is this. If the slave needs to create a folder, e.g. C:/Jenkins/workspace/pipeline-test2 It can do so if C:/Jenkins/workspace exists, but otherwise it fails with Failed to mkdirs: C:\Jenkins\workspace\pipeline-test2 hudson.FilePath.mkdirs(FilePath.java:1169) This seems to be consistent, it does not depend on the characters in the file path, and it can create the folder if the parent exists, what it cannot do for some reason is create the chain of nested folders as it should be able to. Does anybody have any ideas before I file this as a bug? thanks Jon -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/57e8b2e9-b749-4460-a220-186d364fa2a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
