[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.
[JIRA] [artifactory] (JENKINS-25151) access denied errors encountered downloading repo artifacts in multi-configuration jobs
Troy Punch commented on JENKINS-25151 access denied errors encountered downloading repo artifacts in multi-configuration jobs I found a work-around for this. Root cause is preventing the concurrency lock on the same artifact in the repo, but not sure how to accomplish that. So I created a second user defined axis with sleep times defined and used the combination filter to tie the sleep times to each of the BDD folder names that I was splitting the job with originally. Ie Combination filter = (storyFoldersToRun=="navigation" && sleepTime=="0") || (storyFoldersToRun=="cart" && sleepTime=="60") I then added a build step to execute a shell script with sleep $sleepTime, and this worked as by the time the second configuration job wakes up the lock on the maven-metadata.xml file has been released by the first configuration job. Just need to tune the sleep times between each configuration. This is not an optimal solution but should work for now to get us to split our test suites into parallel tests and get the desired performance boost and faster feedback times. If anyone has any info on how to address the root cause artifactory locking issue however it would still be nice to have a more elegant solution to this issue. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory] (JENKINS-25151) access denied errors encountered downloading repo artifacts in multi-configuration jobs
Troy Punch commented on JENKINS-25151 access denied errors encountered downloading repo artifacts in multi-configuration jobs No, The access to artifactory is via a global settings.xml file that all users on the same jenkins server all use via the defaults set for maven jobs. I did configure the Invoke top-level Maven targets -> Advanced -> Settings file -> Settings file in filesystem to point to the file that is used by default in Maven 2/3 jobs: /opt/ltsapps/apache-maven-3.0.3/conf/settings.xml and I am seeing it echoed in my console output debug logs so it is using the correct file to get artifactory repo credentials. Also I have a freestyle job which uses the same Invoke top-level maven targets and the same configuration but runs the build only once, and it passes every time, only the multi-configuration job gets this error on 1 of it's two configurations. [DEBUG] Reading global settings from /opt/ltsapps/apache-maven-3.0.3/conf/settings.xml [DEBUG] Reading user settings from /opt/ltsapps/apache-maven-3.0.3/conf/settings.xml 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
