> > 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.plugins.durabletask.FileMonitoringTask$FileMonitoringController.<init>(FileMonitoringTask.java:99) org.jenkinsci.plugins.durabletask.WindowsBatchScript$BatchController.<init>(WindowsBatchScript.java:94) org.jenkinsci.plugins.durabletask.WindowsBatchScript$BatchController.<init>(WindowsBatchScript.java:92) org.jenkinsci.plugins.durabletask.WindowsBatchScript.doLaunch(WindowsBatchScript.java:60) org.jenkinsci.plugins.durabletask.FileMonitoringTask.launchWithCookie(FileMonitoringTask.java:66) org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:61) As you can see, now it's failing to create the job workspace folder, in fact looking on the slave I see it has failed to create the Jenkins2 filder so I just tried the following... 1) manually created C:\Jenkins2 - Job failed with same stack trace 2) Manually created C:\Jenkins2\workspace - Job failed with different stackl trace Failed to mkdirs: C:\Jenkins2\workspace\pipeline-test2@tmp\durable-e94accb0 hudson.FilePath.mkdirs(FilePath.java:1169) org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.<init>(FileMonitoringTask.java:101) org.jenkinsci.plugins.durabletask.WindowsBatchScript$BatchController.<init>(WindowsBatchScript.java:94) org.jenkinsci.plugins.durabletask.WindowsBatchScript$BatchController.<init>(WindowsBatchScript.java:92) org.jenkinsci.plugins.durabletask.WindowsBatchScript.doLaunch(WindowsBatchScript.java:60) org.jenkinsci.plugins.durabletask.FileMonitoringTask.launchWithCookie(FileMonitoringTask.java:66) org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:61) org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:158) And when I look, I see it has created pipeline-test2! So, I can only conclude that the slave creates pipeline-test2 via a different mechanism to either C:\Jenkins2\workspace or pipeline-test2@tmp -- 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/6233493b-0b4e-44df-98ff-df7ca47f8f46%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
