-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
Platform: All, OS: All
Just tried setting up a first Matrix build and was a bit surprised with the
SCM/workspace interaction.
Having Axes:
Config=Debug Release
Platform=Win32 x64
I had 5 copies of the project checked out. First into the main workspace, then
into the 4 Axes matrix.
The one build area would have been fine for use on these 2 Axes as the workspace
already knows through parameterisation how to separate the build results.
- is related to
-
JENKINS-8317 Matrix jobs with custom workspaces should be able to share the root with no axis-specific subtree
-
- Resolved
-
We don't need the checkout into the main workspace too. It is only a waste of
resources.
I would also propose to have a check box to select if the main workspace may be
used for all axes. If the axes should use separate workspaces, no checkout into
the main workspace is necessary.
The main project then acts only as a starter of the axes projects. Therefor it
may not be necessary to occupy a queue slot for this main project.
So my proposal was:
This proposal is from my view as a user of hudson, I haven't look deep inside to
hudson yet.