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
* Support for configuring all options for polling with a groovy script.
* Added script-file-path in bash script trigger documentation (support
was present in code but not included in documentation)
Change-Id: Ide3ccbb585644c2d89daa46d8eccf79fbba93f96
Following options are added -
* Other jobs on which this job depends
* Notification Level
* Unsuccessful Message File
* Silent Start Mode
Gerrit docstring cleanup for better indentation.
Change-Id: I2d0988973dcdd7ff32e7cdcd2c2676da3235e7fc
Listing jobs as a comma separated list is fine with small amounts of
jobs however when this list gets too long it can be difficult to
maintain.
This patch adds support to list jobs as a list and the code will
automatically change it to a python separated list. Also retains support
for the old style comma separated list.
Change-Id: I0a419bb1f2ec83979f46990430f874381680cac8
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
Adds ability to keep base64 encoded gerrit trigger
variables (such as commit message) in human readable
format.
Change-Id: Ie96d633ab9dc96dacf859409fd649bd981f9eb7c
Adds support for having all members of a
whitelisted organization automatically have
admin rights for the github pull request builder
trigger. Details on this functionality can be found
at https://wiki.jenkins-ci.org/display/JENKINS/
GitHub+pull+request+builder+plugin
Change-Id: Ieca5a789a79d1ad91783fcd4608d26a8d6d61878
New exclude features added to Gerrit Trigger plugin version 2.12.0.
Exclude Features:
- Drafts
- Trivial Rebase
- No Code Change
This patch still supports the old trigger non-dict format yaml config:
- patchset-created-event
Using the old configuration (non-dict) works in the new Gerrit Trigger
v2.12.0 as well as the previous versions.
In addition the newer configuration (dict) format also works in old
<2.12.0 and new >2.12.0 versions of Gerrit Trigger.
Added additional unit tests to verify old and new formats working.
Change-Id: I923b0be47085dc50da48f5ed271a13eae7e1dfa0
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
Adds support for specifiying the specific branches that will be
monitored by the github pull request builder. Details on this
functionality can be found at
https://wiki.jenkins-ci.org/display/JENKINS/
GitHub+pull+request+builder+plugin
Change-Id: If98ce3ca037d3ce33506cf1ffea372e7c18eefda
In order to be able to react on multiple verdict categories (for example
Verify +1, Review +2) with one job, we need multiple definitions of
trigger-on events of the same-kind (comment-added-event). This was not
possible with the previous structure of event definitions.
The new yaml structure definition also better reflects the XML structure.
Change-Id: Idec0f2b07479c0611497126e984c13adf543ffc0
Gerrit trigger in addition to project name, branch and
file-path also supports when-to-trigger limitation
based on topic of the change, this adds support for that.
Change-Id: Icfcb3f02903a61294d23dd53308287a67927c777
Since version 2.11.0 the Gerrit Trigger Plugin can be configured to
generate patchset-created events for changes that were uploaded while
the connection to Gerrit was down.
Change-Id: I59608e4f01355944fed9e44b288fc25a897950c7
Since version 2.11.0 the Gerrit Trigger Plugin can be configured
to trigger on more than one server.
Change-Id: I2082c5cfd14cd2494e2a7192beeb4909552cb7f6
Allow to specify multiple branch patterns in a 'branches' block
within the 'project' block.
If no 'branches' block is present, fall back to using the single
branch specified directly in the 'project' section.
If a branch is specified both at the project level, and in the
'branches' section, ignore the one at project level.
Closes-Bug: #1302502
Change-Id: I1fb2ce0bb3776d365f2c0e98a703c6dfba5fac7f
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