instead of using inline examples in docstrings. With literalinclude, we
know the examples are tested.
Change-Id: I95fbb4726bd6731d9687d09a3d6e7d4e5a445131
This plugin allows the specification of critical blocks for builders.
Once a set of builders is "wrapped" by a critical block start/critical
block end pair, any resources (string) specified in the exclusion build
wrapper will cause any jobs with those same resources to block and allow
only one of those builds to proceed at a time.
Change-Id: I0bf4ab003709917aa7fe6ad57b31200f466658da
In `trigger-builds` builder, create the
'<hudson.plugins.parameterizedtrigger.NodeParameters/>'
element if 'same-node' parameter is set to 'true'.
This adds the configurability of the 'Build on the same node'
parameter.
Change-Id: I3b6fa0a50b74932ad9837c7b88835b8b0c9c23ec
Some options to the trigger-builds builder were not present in the test
fixture. As a side effect that enhance our documentation.
Change-Id: Ic2755f76f02f7eba3842dc9a41f7db8907acda75
In order for the conditional step plugin to work properly, a more
detailed status is required otherwise the current build status is not
evaluated properly and is set to SUCCESS in all cases.
A local mapping of the java hudson.model.Result class was created to
unify build statuses names, ordinal and color scheme.
Change-Id: If8a0090b7cd51551ef6756361f6e45af3df1218d
Done to enable private repository for jobs making it more safe to
run concurrent maven builds and for allowing to control javavm and other
maven settings for maven build.
Includes moving doc example for maven-target as a test fixture.
Change-Id: Ic34958e9bf1008fbc71c45da85208ac1fda7aeb4
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
