Allow `test` command to use conf files

It should be possible to run the `test` command with a custom config.
This allows examination of the XML outputted where config settings can
change the outputted XML. Otherwise any non-default config values will
only be used when running the `update` comand.

Add a simple test to confirm that the custom url that is unlikely to
ever be a valid default value is returned when the command is set to
`test` and a custom config is specified.

Change-Id: I193e83314a35943406bff5b182f20693edd640ba
Show usage of job-group

Make sure the example referenced in the documentation for ``Job Groups``
actually makes use of 'job-group'.

Change-Id: Ib78bdb459db23f57093c1fd4a6dd74a5080dc239
Merge "Show usage of job-group"
Revert "Allow using template variables in "defaults" field."

This reverts commit 70ed22362a9c13ea9f3165e5747dcca281ad439c.

I knew I should have tested the patch with my own templates. Doing so I
discovered a nasty regression:

The defaults can make use of variables passed by the project. By moving
applyDEfaults to be called after deep_format is performed on job
templates, any substitutioncontained withing defaults is no longer
correctly replaced by project parameters.

Change-Id: I69ffb3e28093af6db62962786d9275bf3ba4e115
Test defaults honors project variables

The defaults can make use of variables passed by the project and I am
taking advantage of that feature in my templates.

With 70ed2236 / https://review.openstack.org/#/c/85336/ there is a
regression which cause the test to fail although it pass with parent
commit d833015.

Change-Id: I57d023657eec4f6f8f29980100185fcfd7e77b1f
add include/exclude regions/users in svn scm (doc and tests)

Change-Id: I99ed104cd2cbaba1588dfc31d3b8a028de2e80ee
Add support for 'ignore-notify' in git SCM

This option is named "Don't trigger a build on commit notifications"
in the Jenkins Web UI.

Change-Id: I338af61f8bfdef1545d1ea206e6874cda38957cd
Document default values for git scm

Change-Id: I0a1671c1f4de86f516d6f1605503175e5973e07b
Argparse is required for JJB to parse arguments

Move argparse requirement from tests to install requirements as it is
required when using JJB.

Change-Id: If503ebfe790c904f77ef45b59ea909a2577db5cd
Merge "Add support for 'ignore-notify' in git SCM"
Merge "Test defaults honors project variables"
Merge "Argparse is required for JJB to parse arguments"
Add support for URLTrigger plugin

Change-Id: Ibc96b3ecd65afb27398328f2b6220c32a800f3e6
Replace 'Testing JJB' with the term 'Test Mode'

The term 'testing' is overloaded.  I thought it meant running the actual
JJB tests instead of running the JJB application.  I think a good way to
distinguish the two is to use the term 'test mode' when it's in the
context of running the JJB application with the 'test' parameter.
I've already been using the term 'run in test mode' quite a bit in
my JJB reviews to distiguish it from the actual JJB tests.

Change-Id: I2076189e3ae55caa20d0894fb20859a7c461e46a
Clarify configuration and job definition

The docs was a little confusing in that used a single term 'configuration' to
referred to both the JJB global configuration and the job definitions.
This change clarifies that by changing 'configuration' in a few places
to 'job definition' to make it less confusing.

Change-Id: Ie64e7d899b793c9c8e86e51076c020640e336a40
Merge "Document default values for git scm"
Merge "Clarify configuration and job definition"
Merge "Add support for URLTrigger plugin"
Merge "add include/exclude regions/users in svn scm (doc and tests)"
Merge "Allow `test` command to use conf files"