Updated test cases as well, The tag has been introduced after 2.35.2
therefore the parameter is also >=2.35.2
Change-Id: Ie0801108a16969b420b341e2deaa6ba62deb116c
Signed-off-by: Eren ATAS <eatas.contractor@libertyglobal.com>
When configuring the trigger_builds Builder in the Jenkins web
interface, you can add the parameter "Pass-through Git Commit that was
built". You could not configure this in a jobs.yml.
This commit adds that functionality (both to the builder
"trigger_builds " and the publisher "trigger_parameterized_builds").
I still want to be backwards compatible with the old version
(true/false) and maintain the similarity with the svn-revision param.
Which means that you can either configure it as
git-revision: true/false
or
git-revision:
combine-queued-commits: true/false
There were no prior case of shared code between builders and
publishers, so (by recommendation) I put the common logic in
builders.py, and then imported it in publishers.py.
I added thorough tests for the feature in the builders fixtures,
and only a basic test in the publishers fixtures, as suggested.
Change-Id: I72cdcae3fac1094ffcc9367369556b8bcbe2d5d7
Since Jenkins parameterized build trigger publisher supports comma-separated
list of jobs to build, this simply joins a list of jobs specified in JJB yaml on
a comma.
Change-Id: I4fefeeaae1b39b7932d11ce88f1d75a9ca5faff5
For supporting ability to run downstream project on the same node
parameter 'NodeParameters' should be present in output xml.
Adding same parameter to 'trigger_parameterized_builds' publisher.
Change-Id: I7769507d8da138fe0944e1b5bc24ab595e787587
Add support for using the NodeLabel Parameter plugin to
specify which node should run a job when triggering a
parameterized build.
Requires the Jenkins NodeLabel Parameter Plugin:
https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin
Change-Id: Ie947a2a3069b477419db7eaa35307088712467e3
Eren ATAS