[ https://issues.jenkins-ci.org/browse/JENKINS-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159704#comment-159704 ]
Andy Bigos commented on JENKINS-10606: -------------------------------------- Hi, Given the title of this issue - can I ask what is the general state of Matrix Job support at the moment? I ask as I have some jobs which have some matrix elements that don't sync. It's pretty random which elements don't get a synced. I have selected: * Let Jenkins Manage Workspace View - TRUE * Let Jenkins Create Workspace - TRUE * Clean Workspace Before Each Build - TRUE * Always Force Sync - TRUE * Poll Only on Master - TRUE Does this behaviour sounds like something you might expect given the current level of support for matrix builds, or should I create a new issue and add more details? Or am I simply missing something in the config? Thanks for help, 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