|
||||||||
|
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.
Yes
JENKINS-14618would fit the description. The nodes of the matrix run on different machines, where the matrix job is to be executed. The master's only job is to distribute the job to the slaves. As Daniel Beck says, the issue JENKINS-4960 describes the exact opposite where the master is supposed to do the checkout.If I follow the idea of JENKINS-4960, I would indeed have a problem since the master is on a slow network subnet, where-as the slaves have direct access to the SCM. Having the master do the checkout and then somehow transfer the data to the slaves would mean a big increase in performance/time loss.
So yes, as Daniel Beck already stated,
JENKINS-14618describes my point, altho somewhat more compact... JENKINS-4960 is not related to my problem.I intent to save time by directly passing the job to the slaves configured in the job. The master has no actual work to do except hand the job to the slaves and receive the result of the job.