jjb/jenkins-job-builder
Code Issues Proposed changes

Validate the use of [] as an scm value

Browse Source 
This is necessary in the case where global defaults sets a templated `scm` value
used by most jobs but which is undesirable for a minority of jobs and where it
would be inconvenient to copy all the desired settings out of the global
defaults into a custom defaults just for that particular set of jobs.

Change-Id: I201c29215a7090b81e84b9d494bd2cf6ea0370ad
This commit is contained in:
Wayne 2015-06-19 08:23:37 -07:00
parent 6fe4626518
commit 815b7f0f69
3 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
jenkins_jobs/modules/scm.py
View File

@ -16,7 +16,10 @@
"""
The SCM module allows you to specify the source code location for the
project. It adds the ``scm`` attribute to the :ref:`Job` definition,
which accepts any number of scm definitions.
which accepts any number of scm definitions. It is also possible to pass
``[]`` to the ``scm`` attribute. This is useful when a set of configs has a
global default ``scm`` and you want to a particular job to override that
default with no SCM.
**Component**: scm
:Macro: scm
@ -28,6 +31,9 @@ Note: Adding more than one scm definition requires the Jenkins
Example of multiple repositories in a single job:
.. literalinclude:: /../../tests/macros/fixtures/scm/multi-scms001.yaml
Example of an empty ``scm``:
.. literalinclude:: /../../tests/scm/fixtures/empty.yaml
"""
import logging

4
tests/scm/fixtures/empty.xml Normal file
View File

@ -0,0 +1,4 @@
<?xml version="1.0" encoding="utf-8"?>
<project>
<scm class="hudson.scm.NullSCM"/>
</project>

1
tests/scm/fixtures/empty.yaml Normal file
View File

@ -0,0 +1 @@
scm: []