[JENKINS-3401] Multi configuration projects tied to nodes checkout code on the machine that triggers the builds as well

When setting up a multi-configuration job in hudson, the checkout of the

workspace(s) happens on the machines from which the builds are triggered on

specific nodes. This is a problem when the workspace is particularly large, like

glassfish for example.

---
Originally reported by mode, imported from: Multi configuration projects tied to nodes checkout code on the machine that triggers the builds as well

• status: Open
  
• priority: Major
  
• component(s): matrix-project-plugin
  
• resolution: Unresolved
  
• votes: 6
  
• watchers: 9
  
• imported: 2025-12-06
  

Raw content of original issue

When setting up a multi-configuration job in hudson, the checkout of the

workspace(s) happens on the machines from which the builds are triggered on

specific nodes. This is a problem when the workspace is particularly large, like

glassfish for example.

• environment: Platform: All, OS: All

Start by reproducing a multi-configuration job tied to specific nodes and tracing where workspace checkout occurs in the matrix-project-plugin. Confirm the behavior for a large workspace such as glassfish, then define completion as checkout occurring only on the target build nodes rather than on the machine triggering the builds, with regression coverage.

Written by the indexing model from the issue text.