|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
+1 on AIX with Jenkins 1.502 and JDK 1.6
java.io.IOException: Failed to mkdirs: /path/to/.jenkins/workspace/my-project
at hudson.FilePath.mkdirs(FilePath.java:990)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1340)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588)
at hudson.model.Run.execute(Run.java:1568)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:237)
The workspace directory of the slave had mode 666 (drw-rw-rw-).
A developer has renamed a job and cancel the request. Is-it related ?
I had to delete the renamed project workspace, give 755 access rights to /path/to/.jenkins/workspace and the slave seems to be ok for now.