[JIRA] [workflow-plugin] (JENKINS-29713) Failed to mkdir errors encountered when using the workflow plugin parallel functionality.
Title: Message Title JT Chu commented on JENKINS-29713 Re: Failed to mkdir errors encountered when using the workflow plugin parallel functionality. Unfortunately, I am unable to reproduce this issue today. If I encounter this issue again, I will use your prescribed method to track it down. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29713) Failed to mkdir errors encountered when using the workflow plugin parallel functionality.
Title: Message Title
Jesse Glick commented on JENKINS-29713
Re: Failed to mkdir errors encountered when using the workflow plugin parallel functionality.
No clue offhand. Unfortunately the presence of a file does not indicate what code created it. If you have any idea how to reproduce from scratch, let me know. Or if it only happens in a particular system, but you are able to clone that into a test environment, you can try disabling other plugins to see if one of them is responsible.
It is possible, but rather difficult, to patch Java to give you a stack trace when a file is written. The File Leak Detector plugin tracks the events but normally discards the information when the file handle is closed. You can try running the following (untested!) in /script after installing that plugin:
org.kohsuke.file_leak_detector.ActivityListener.LIST.add(new org.kohsuke.file_leak_detector.ActivityListener() {
public void open(Object obj, File file) {
if (file.name == 'TASKMANAGER_IT_WORKFLOW_PoC@2') {
java.util.logging.Logger.getLogger('JENKINS-29713').log(java.util.logging.Level.WARNING, null, new IllegalStateException())
}
}
})
and then check /log/all for a stack trace if it happens again.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29713) Failed to mkdir errors encountered when using the workflow plugin parallel functionality.
Title: Message Title JT Chu commented on JENKINS-29713 Re: Failed to mkdir errors encountered when using the workflow plugin parallel functionality. Empty Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29713) Failed to mkdir errors encountered when using the workflow plugin parallel functionality.
Title: Message Title Jesse Glick commented on JENKINS-29713 Re: Failed to mkdir errors encountered when using the workflow plugin parallel functionality. Strange. I do not know of anything that would be causing the workspace folder to be created as a plain file. Maybe a bad plugin. Does it have any contents or is it empty? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29713) Failed to mkdir errors encountered when using the workflow plugin parallel functionality.
Title: Message Title JT Chu commented on JENKINS-29713 Re: Failed to mkdir errors encountered when using the workflow plugin parallel functionality. I encountered the same issue. Found out the workspace folder name was created as a file and not a directory. For example, using the above use case TASKMANAGER_IT_WORKFLOW_PoC@2 was created as a file during the deployment and prevented jenkins to create the workdir /opt/ltsapps/jenkins/workspace/TASKMANAGER_IT_WORKFLOW_PoC@2/.887fa578 The current workaround is to create this folder manually in the Jenkins slave before Jenkins workflow deployment. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29713) Failed to mkdir errors encountered when using the workflow plugin parallel functionality.
Title: Message Title Jesse Glick resolved as Incomplete Not enough information here to tell exactly what is going wrong, much less reproduce. Jenkins / JENKINS-29713 Failed to mkdir errors encountered when using the workflow plugin parallel functionality. Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29713) Failed to mkdir errors encountered when using the workflow plugin parallel functionality.
Title: Message Title
Troy Punch created an issue
Jenkins / JENKINS-29713
Failed to mkdir errors encountered when using the workflow plugin parallel functionality.
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
29/Jul/15 9:41 PM
Environment:
Jenkins workflow plugin 1.8 Jenkins ver. 1.609.1
Labels:
workflow
Priority:
Major
Reporter:
Troy Punch
When using the parallel functionality of Jenkins Workflow, I encounter a ParallelStepException Caused by: java.io.IOException: Failed to mkdirs: /opt/ltsapps/jenkins/workspace/TASKMANAGER_IT_WORKFLOW_PoC@2/.887fa578.
I am using node { with no label as when I used a lable (either'linux' or 'llt95nxassafe000.opr.test.statefarm.org' the name of my linux executor, the build hung with Still wating to schedul task / there are no nodes with the label linux messages. We need to be able to run our acceptance tests in parallel to get feedback in a timely manner.
