<p dir="ltr">This could be done, but not trival to do, and also requires you to know, before merging, that this is the patch you are gonna release.</p>
<p dir="ltr">A differnt but somewhat common practice is to use git tagging and 'git describe' to set the package version. <br>
We can make build_artifacts trigger when a tag is pushed, AFAIK Lago already does that...</p>
<div class="gmail_quote">בתאריך 22 ביוני 2016 18:39, "Vojtech Szocs" <<a href="mailto:vszocs@redhat.com">vszocs@redhat.com</a>> כתב:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I'm just curious whether it's possible to do the following:<br>
<br>
Let's say we have a project (ovirt-engine-dashboard) built by Jenkins,<br>
which means there's a Jenkins job that runs build-artifacts.sh script<br>
whenever a patch gets merged via gerrit.<br>
<br>
Can we somehow pass custom parameters to build-artifacts.sh for such<br>
(Jenkins CI) builds?<br>
<br>
For example, putting something like this into commit message:<br>
<br>
My-Param 123<br>
<br>
would reflect into `My-Param` env. variable when running the script?<br>
<br>
Motivation: for release builds (which shouldn't contain the "snapshot"<br>
part [*] in RPM release string), pass parameter to build-artifacts.sh<br>
that ensures the "snapshot" part is empty. This way, we don't need to<br>
patch the project prior to release (remove "snapshot" in spec) & then<br>
patch it again after the release (re-add "snapshot" in spec).<br>
<br>
[*] {date}git{commit}<br>
<br>
Thanks,<br>
Vojtech<br>
_______________________________________________<br>
Infra mailing list<br>
<a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
</blockquote></div>