-
New Feature
-
Resolution: Unresolved
-
Critical
-
None
-
Platform: All, OS: All
When a project got a configuration matrix, the source code is checked out multiple times:
- Once for reference incase of poll scm on schedule.
- Once per matrix item, increasing proportionaly to the complexity.
It would be great to have a strategy, which runs checkout only once in the master build.
A patch proposal from @asolsson (initial implementation before creation of SCMCheckoutStrategy )
I've implemented an enhancement to the matrix project to avoid a SCM checkout
for each target in the matrix. This can be useful if checkout takes a long time
and if the build step can build concurrent builds from the same SCM area.
It's implemented as a option when setting up the Matrix project, if not
used/checked the Matrix project will work as usual.
- is duplicated by
-
JENKINS-5078 It should be possible to skip sources checkout either on master or on slaves
- Closed
- is related to
-
JENKINS-6902 Errors fetching from remote repos don't fail the build
- Closed
-
JENKINS-13042 Unable to checkout SCM repository once for complex configuration matrixes
- Closed
-
JENKINS-3401 Multi configuration projects tied to nodes checkout code on the machine that triggers the builds as well
- Open
-
JENKINS-6184 SCM poll must run on master
- Closed
-
JENKINS-7350 Option to tie Cleartool operations to the master node in case of distributed build
- Open