Skip to content

Commit

Permalink
doc: add chapter about nested SCMs
Browse files Browse the repository at this point in the history
  • Loading branch information
jkloetzke committed Dec 10, 2023
1 parent 067fcba commit 138ac60
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions doc/manual/configuration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -868,6 +868,14 @@ be given as IfExpression (see :ref:`configuration-principle-booleans`). By
default the SCMs check out to the root of the workspace. You may specify any
relative path in ``dir`` to checkout to this directory.

Special care must be taken if SCMs are nested, that is the ``dir`` attribute of
one SCM is a subdirectory of another. Bob requires that the SCM with the upper
directory has to be in the list before the SCMs that are checked out into
subdirectories. Additionally, SCMs that are natively supported by Jenkins
plugins (git, svn), cannot be nested into the other SCMs (cvs, import, url).
The reason is that Jenkins SCM plugins always execute before anything else in a
Jenkins job.

By using ``if`` you can selectively enable or disable a particular SCM using
either a string or a expression. In case a string is given to the ``if``-keyword
it is substituted according to :ref:`configuration-principle-subst` and the final
Expand Down

0 comments on commit 138ac60

Please sign in to comment.