|
||||||||
|
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/d/optout.
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.