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
This commit is contained in:
parent
666e9537f7
commit
848ce968e0
@ -101,19 +101,21 @@ Usage
|
||||
^^^^^
|
||||
.. program-output:: jenkins-jobs --help
|
||||
|
||||
Testing JJB
|
||||
^^^^^^^^^^^
|
||||
Once you have a configuration defined, you can test the job builder by running::
|
||||
Test Mode
|
||||
^^^^^^^^^
|
||||
Once you have a configuration defined, you can run the job builder in test mode.
|
||||
|
||||
jenkins-jobs test /path/to/config -o /path/to/output
|
||||
If you want to run a simple test with just a single YAML configuration file
|
||||
and see the XML output on stdout::
|
||||
|
||||
jenkins-jobs test /path/to/foo.yaml
|
||||
|
||||
You can also pass JJB a directory containing multiple configuration files::
|
||||
|
||||
jenkins-jobs test /path/to/configs -o /path/to/output
|
||||
|
||||
which will write XML files to the output directory for all of the jobs
|
||||
defined in the configuration directory.
|
||||
|
||||
If you want to run a simple test with just a single YAML file and see the XML
|
||||
output on stdout::
|
||||
|
||||
jenkins-jobs test /path/to/config
|
||||
defined in the configs directory.
|
||||
|
||||
Updating Jenkins
|
||||
^^^^^^^^^^^^^^^^
|
||||
|
Loading…
x
Reference in New Issue
Block a user