I don't know. I didn't do the research to understand precisely why it
behaves that way.
On Tuesday, March 6, 2018 at 11:26:59 AM UTC-7, Dan wrote:
> What technical requirement does the master checkout satisfy?
> Listing the SCM Changes doesn't require a full checkout.
> And the Workspace can be viewed for the nodes as well as the master.
> On Tuesday, March 6, 2018 at 12:45:49 PM UTC-5, Mark Waite wrote:
>> No, it can't be turned off.
>> If your repositories are large or bandwidth to the git server is low, you
>> might consider the hints from "Git in the Large
>> <https://www.slideshare.net/markewaite/git-inthelarge>". Those are the
>> slides I presented at the Jenkins World 2017 community booth. A Jenkins
>> Online Meetup is available if you prefer to hear me talking through the
>> Mark Waite
>> On Tue, Mar 6, 2018 at 10:38 AM Dan <daniel....@remcom.com> wrote:
>>> We use Jenkins multi-configuration projects exclusively to build on both
>>> Windows and Linux on a variety of compilers. The builds are executed on
>>> several Virtual Machines. However, Jenkins always performs a checkout on
>>> the master node *before* doing an SCM checkout for each matrix job.
>>> Why is this extra checkout necessary? Can it be turned off to save
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.