- Add plugin="delivery-pipeline-plugin" attribute
- Rename test files to be more descriptive
Change-Id: I9db5315e425da6bd5c69b533c79d6d5ab4ed1e70
Signed-off-by: Kien Ha <kienha9922@gmail.com>
- Update doc to use 4 space indent syntax
- Update test file to be more descriptive
- Add minimal test
- Add plugin="xvnc" attribute
Change-Id: I6b669d3b18fd6efadcbaf1b801242a46d9c2db21
Signed-off-by: Kien Ha <kienha9922@gmail.com>
- Update to use convert xml
- Update doc options to have default values
- Rename test files to be more descriptive
Change-Id: I83ada14df074805333eb50d746a0bc90fd7b5619
Signed-off-by: Kien Ha <kienha9922@gmail.com>
- Rename full and minimal test files to be more descriptive
Change-Id: Ia70f4c23341c4bd5aa137f9620cb945aa9cce5fc
Signed-off-by: Kien Ha <kienha9922@gmail.com>
- Rename test file to be more descriptive
- Add plugin="livescreenshot" attribute
Change-Id: I587e52c2cc2ba601b9d610ee6916edba4c9e3367
Signed-off-by: Kien Ha <kienha9922@gmail.com>
This patch adds support for the Maven release build wrapper.
The Maven release plugin makes use of the concept of jenkins Actions
to trigger the actual release -
https://wiki.jenkins-ci.org/display/JENKINS/Action+and+its+family+of+subtypes
The actual code for the action -
https://github.com/jenkinsci/m2release-plugin/blob/master/
src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java,
seems to put together all the required
parameters and makes a call to scheduleBuild2 and passes an Action object with it.
Afaik, JJB doesn't support the concept of Actions. If the M2ReleaseAction was an
instance of Builder, instead of Action it would work with this. Currently, I don't
see how the actual build (release) can be triggered from JJB config, and it seems
like we can define the build wrapper alone as part of the job definition, and would
still have to trigger the release from the UI for the job like - <jobname>/m2release
Change-Id: Ifc979cdb8e40ad31debff04f745649f23f7ef91a
We can inject access and secret key in environment variables using
Amazon Web Services Credentials plugin.
This allows us to use amazon web service command line client and api
into builders.
Change-Id: I2569cad0e873f2ff80b8b8549c7fcacdf5909ea3
Signed-off-by: Thomas Desvenain <thomas.desvenain@gmail.com>
This commit adds support for controlling whether cleanup runs via a job
parameter and using an external deletion command.
Change-Id: Ib80317c0e4cf95526ed59b719a1fd8df9c5e3f4f
Update Urls broken in the documentation and code to results of
redirects or where the correct endpoint is known.
Change-Id: Ie4ef2d1e207c7a98295625ed2cb74ab37e85730d
(cherry picked from commit 63ca017d0a728a96e8a8a1128d309f79bea7c769)
This build wrapper uses the "Cloudbees Docker Custom Build Environment
plugin". It allows to define build environment using either a Dockerfile
stored in project SCM, or a docker image from docker registry directly.
Change-Id: I11f94a10b8a06bd4aa61a817c21a1ee1dd885072
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
Since copy to slave plugin version 1.4 (released on January 2012),
an additional value 'somewherElse' is permited for "paths are relative to"
option.
Relevant bug and commit:
https://issues.jenkins-ci.org/browse/JENKINS-1228174f4fc505b
Additional changes: re-order alphabetically the options as the plugin
itself does.
Change-Id: Ie0f738120e0fb95c9826d61871e6bdda461b5b5a
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
Capture logs to attach them on exceptions to simplify the debugging of
errors in tests when they occur.
Change-Id: I5c1b5c306aba37789a8d41eabf65e0ac628af838
Remove the test options suppressing ignoring differences in whitespace
outputted in the XML to allow capturing of issues where the code
incorrectly adds or removes significant whitespace.
Add a helper function to deal with the edge case of parsing XML directly
that contains non significant whitespace to avoid accidentally adding
excess whitespace when minidom outputs the resulting document.
Change-Id: I9936042cd82c204ba2b3c19f575703e33564f7fd
* Adding the option to select Username and Password (separated) -
Allows the user to set one variable to the username and
one to the password in the credentials.
Change-Id: I926bbd166ca00846fe280dda61eb821c5bb89b13
https://wiki.jenkins-ci.org/display/JENKINS/LiveScreenshot+Plugin
You can find the original version of this patch here:
a1be29b0a3
My (Philip Hands's) contribution is limited to moving the one line from
setup.py to setup.cfg, fixing a couple of very minor pep8 errors, adding
the unit test, and submitting it upstream (now).
I've therefore set the Author to be Holger.
It is being submitted upstream by me (Philip Hands) with Holger's approval,
because he doesn't have the time available to do it himself.
Change-Id: I57a19786f202ebdb2f98cd63252b1a1e1639d9b3
Co-Authored-By: Philip Hands <phil@hands.com>
Add support specifically for BuildTimeoutWrapper plugin version 1.14 and later;
leave module behavior intact for previous versions.
Change-Id: I6e9459271172540eda4fdb576d788fa2ae6f4d68
'raw' allow users to have a fallback in case
a plugin is not yet supported or the plugin is not generating the
expected result.
Only intended as a last fallback, but useful when waiting for
review to complete.
Change-Id: If0d22d7d43d35649e78aa7481e1c0f1ed21a6025
- Adds additional support for Config File Provider to builder sections
- Move builder/wrapper configuration to a common helper function for
reuse
Change-Id: Ie80a3abbd42bdd06d138dcd0c5beea26c9a81f26
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
The Job Log Logger plugin writes the Jenkins job log to the underlying Jenkins
log system in addition to the normal build log.
Change-Id: I17b73ade974edf3d7a2d1e08c4e4c584dbe32c51