- Documentation updated with correct links and options
- New openshift-creator builder added
- Two new publishers openshift-build-canceller and openshift-deploy-canceller
- Added verbose option to all existing builders and scm
Change-Id: I63f19bec6ea8a2344f48d59ad751a8bc5c3be9eb
Currently JJB warns over 700 times when checking project-config with:
WARNING:jenkins_jobs.registry:You have a macro ('tox') defined for
'builder' component type that is masking an inbuilt definition
Warn only once for this.
Change-Id: I010765269c499320fc9a84b9493d22949080e9a0
Documentation on trigger-parameterized-builds option 'fail-on-missing'
does not mention what kind of files are being tested for existance.
According to Parameterized Trigger Plugin settings, 'fail-on-missing'
checks if files which are set in 'property-file' option exist.
Story: 2000448
Change-Id: I408838a7b02e602a3da09add7f322204d2106eea
This changes the Credentials Binding support to emit a single
credentials binding XML block no matter how many credentials binding
entries there are in the YAML. This is needed because the Credentials
Binding plugin doesn't handle more than one XML block.
Change-Id: I3c1ac4391920104666d86fa85b06fb2c5543cf4a
New plugin version of stashNotifier now supports credentialsId
to be setup. This PR aims to manage this new feature
Change-Id: I4b3c33efba8cfd1cce01a4b7a1c8f6f95db56a30
Let a multijob phase specify a subset of a matrix job via a
Groovy filter, as the Parameterized Trigger plug-in does.
This is from a builder, not a publisher.
A project can define a filter via 'restrict-matrix-project'.
Two plug-ins are involved in this: Parameterized Trigger and
Multijob.
Change-Id: Ifa5f91ed080c4eb43c31a593b70b5e1e5169e77e
Signed-off-by: Daniel Díaz <daniel.diaz@linaro.org>
Multijob builder is missing the "Abort all other job" parameter configuration
This PR adds its management setup
Change-Id: I5efe677ba644e5e9b104248d44b669b1d4a75f10
This builder uses the ShiningPanda plugin. It is implemented as a
"tox" builder independent of the "shining-panda" one since the latter
defines "common" arguments (such as `nature` or `command`) that do not
apply to this tox builder.
Change-Id: Ia78cf6cf5c4b5807562032fc9936e589877564df
Prefer user defined macros over inbuilt entry points, as JJB may
accidentally use a name that has already been used by an end-user to
define a custom macro.
Warn users when they have a macro defined that masks an in-built
component to avoid accidentally changing XML generated with new
releases.
Change-Id: I6cae62d7cc40be6c4a5636a74f151fcce4cdd856
Use the component type entry points to infer modules to scan
corresponding modules and automatically construct entry points for any
functions associated with yaml entries in JJB definitions.
This removes the need for new JJB modules added directly to the project
to also need to be listed in the setup.cfg to be reachable. Simply
adding the needed functionality to the correct file ensures that it is
available.
Change-Id: I2a0fd8f6720ddfd8582b58e47556a87ed1ad553d
Move remaining examples to unit tests, remove unnecessary '\' and align
docstrings to the predominate standard throughout the project.
Fix broken authenticated-build highlighted by the added unit test.
Change-Id: Ic9700f587073946be17be543920a4a3ed7cd19d0