<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 11, 2016 at 7:07 PM, Nadav Goldin <span dir="ltr"><<a href="mailto:ngoldin@redhat.com" target="_blank">ngoldin@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I think what happened is:<br>
1. The two patches <a href="https://gerrit.ovirt.org/#/c/67976" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/c/<wbr>67976</a> and<br>
<a href="https://gerrit.ovirt.org/#/c/67878/(the" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/#/c/<wbr>67878/(the</a> version bump) were merged<br>
approximately at the same time.<br>
2. The build_artifacts job for the first patch ended after the<br>
build_artifacts job of the version bump, thus that was the 'last<br>
successful build' in Jenkins(build number 25)<br>
3. The nightly publisher job took that RPM(from job 25), which was<br>
before the version bump.<br>
<br>
so this is not a git issue(just a bug in the nightly publisher flow)<br>
<a href="http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-el7-x86_64/25/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/<wbr>vdsm-jsonrpc-java_4.0_build-<wbr>artifacts-el7-x86_64/25/</a></blockquote><div><br></div><div>Since we're planning to decommision it in favor of experimental not sure we have any action item here.</div><div>In experimental this wouldn't fail because the latest rpm will still be there </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<div class="HOEnZb"><div class="h5"><br>
On Sun, Dec 11, 2016 at 4:11 PM, Barak Korren <<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a>> wrote:<br>
> On 11 December 2016 at 16:01, Eyal Edri <<a href="mailto:eedri@redhat.com">eedri@redhat.com</a>> wrote:<br>
>><br>
>><br>
>> AFAIK all of these builds were triggered on merged patches.<br>
><br>
> We need to see which code its cloning - I suspect it is still trying<br>
> to clone the patch instead of the master branch, this may indeed be a<br>
> bug in how we configure the git plugin to work with the Gerrit<br>
> trigger.<br>
> (It just occurred to me it may need to be configured differently fro<br>
> pre and post-merge jobs)<br>
><br>
> We will need to investigate this more deeply (compare git hashes jobs<br>
> get before and after merge, etc.)<br>
><br>
> But if its a ff-only repo, this means that you can't merge a patch<br>
> that needs a rebase, so if patches were rebased, and build_artifacts<br>
> runs post-merge, it should be impossible to get it to run on<br>
> non-rebased code.<br>
><br>
> --<br>
> Barak Korren<br>
> <a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>
> RHCE, RHCi, RHV-DevOps Team<br>
> <a href="https://ifireball.wordpress.com/" rel="noreferrer" target="_blank">https://ifireball.wordpress.<wbr>com/</a><br>
</div></div><div class="HOEnZb"><div class="h5">> ______________________________<wbr>_________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
> <a href="http://lists.phx.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.phx.ovirt.org/<wbr>mailman/listinfo/devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Eyal Edri<br>Associate Manager</div><div>RHV DevOps<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div></div></div>
</div></div>