[ https://issues.jenkins-ci.org/browse/JENKINS-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159706#comment-159706 ]
Rob Petti commented on JENKINS-10606: ------------------------------------- Your matrixruns might be running at the exact same time with the same client, so some of them don't sync. Try adding the ${JOB_NAME} token to your client workspace name. That should prevent any collisions, since it's unique for all matrixruns. > Support Matrix Builds > --------------------- > > Key: JENKINS-10606 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10606 > Project: Jenkins > Issue Type: Improvement > Components: perforce > Reporter: Rob Petti > Assignee: Rob Petti > > Currently the perforce plugin does not explicitly support matrix builds, > which can lead to certain features not working correctly. > For example, matrix builds will always use the same client workspace for all > sub jobs, requiring a force sync for each one. In addition, each sub job will > sync to the latest changeset, which could be different depending on when the > jobs run. At the very least, the perforce plugin should sync to the same > changeset for all sub jobs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira