Matrix job by design require both head build and all axes to run SCM operations :

  • head to determine the revision to build, and trigger all axes builds accordingly
  • axes to prepare workspace in sync with revision to build.

see for sample Git-plugin support for matrix jobs : https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCM.java#L845

probably some SCM can do some light weight operation when they already know the revision to checkout, vs a full fetch from matrix head, but they will anyway have to do some stuff BOTH on axes and head.

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.

Reply via email to