[
https://issues.jenkins-ci.org/browse/JENKINS-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159707#comment-159707
]
Andy Bigos commented on JENKINS-10606:
--------------------------------------
Yes - that was it. Thanks!
I'd set all the other items that had an 'Import Note' about matrix builds - but
the workspace name didn't have one (though it has plenty of others!). At the
risk of adding even more text I'd suggest adding something about this - or even
better, when a matrix job is detected auto-populate the field with ${JOB_NAME}.
That will at least bring the issue to notice.
Anyway - thanks for sorting the issue out so quickly.
Andy
> 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
