Hi, We have many pipeline jobs that work against a large Subversion repository. A full checkout of branch or trunk is about 2.5GB. Our repo also uses externals.
This means /var/lib/jenkins is ~250GB and growing. It seems very wasteful for Jenkins master to have to checkout the entire trunk just to get the jenkinsfiles. But I’m not sure that the alternative ‘Lightweight Checkout’ is useful.
The pipeline help, concerning Lightweight Checkout reads:
If selected, try to obtain the Pipeline script contents directly from the SCM without performing a full checkout. The advantage of this mode is its efficiency; however, you will not get any changelogs or polling based on the SCM. (If you use
checkout scm during the build, this will populate the changelog and initialize polling.) Also build parameters will not be substituted into SCM configuration in this mode. Only selected SCM plugins support this mode.
Is it true that polling, in particular, does not work with a lightweight checkout?
Can anyone offer advice on how to get around large checkouts please?