On Wed, Jun 22, 2016 at 5:39 PM, Vojtech Szocs <vszocs@redhat.com> wrote:

I'm just curious whether it's possible to do the following:

Let's say we have a project (ovirt-engine-dashboard) built by Jenkins,
which means there's a Jenkins job that runs build-artifacts.sh script
whenever a patch gets merged via gerrit.

Can we somehow pass custom parameters to build-artifacts.sh for such
(Jenkins CI) builds?

For example, putting something like this into commit message:

  My-Param 123

would reflect into `My-Param` env. variable when running the script?

you should be able to use "git show|grep My-Param" from build-artifacts.sh itself and act on it


Motivation: for release builds (which shouldn't contain the "snapshot"
part [*] in RPM release string), pass parameter to build-artifacts.sh
that ensures the "snapshot" part is empty. This way, we don't need to
patch the project prior to release (remove "snapshot" in spec) & then
patch it again after the release (re-add "snapshot" in spec).

[*] {date}git{commit}

Infra mailing list

Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com