The values map to these GUI choices
* default -> Default
* local-to-executor -> Local to the executor
* local-to-workspace -> Local to the workspace
This is on the project level what the similar option is on the builder
level.
Change-Id: I90ee3385ee12a46b5ab1eb26e3af1bdbfc36946a
So far it wasn't possible to test the prameters of the
project itself. While If7b749dae7631e8714a9416dfbd82d2443c0302c
already made the job creation consistent this goes one step further
and creates the root_xml using the project's root_xml method.
Change-Id: Ieba4203d3d23ad68df5a1246e90ea8c03ddd54d4
Defining a project (in yaml) without setting any other parameters should
generate a basic jenkins job (in xml). While this works for freestyle jobs,
jjb will throw an error for maven and flow projects. The behavior should be
consistent across all types of projects. This patch just makes it so
that the behavior is consistent.
Change-Id: If7b749dae7631e8714a9416dfbd82d2443c0302c
Add documentation on how to generate documentation and run JJB unit tests.
Also added a unit tests for each category of plugins as examples for others
to follow when adding new JJB plugins. I'm hoping this will help contributors
add tests for new plugins going forward.
Change-Id: I2ab90cdb37d0f3b1e947345d4291d2927b04a0c6
This patch refactors the tests suite to use a base class to declare test cases
just using a class declaration, the existing test class was modified to use it
and new tests are using it as well.
These tests verify the XML generated when the 'node' option is set and
when it's absent.
Change-Id: Iddcdd63e0ab7c459f6513b1d1ebf19e19a362c1d