Re: [ovirt-devel] 4.0.x dependency failure (vdsm-jsonrpc-java)
I think what happened is:
1. The two patches https://gerrit.ovirt.org/#/c/67976 and
https://gerrit.ovirt.org/#/c/67878/(the version bump) were merged
approximately at the same time.
2. The build_artifacts job for the first patch ended after the
build_artifacts job of the version bump, thus that was the 'last
successful build' in Jenkins(build number 25)
3. The nightly publisher job took that RPM(from job 25), which was
before the version bump.
so this is not a git issue(just a bug in the nightly publisher flow)
http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-el7-x8...
On Sun, Dec 11, 2016 at 4:11 PM, Barak Korren <bkorren(a)redhat.com> wrote:
On 11 December 2016 at 16:01, Eyal Edri <eedri(a)redhat.com>
wrote:
>
>
> AFAIK all of these builds were triggered on merged patches.
We need to see which code its cloning - I suspect it is still trying
to clone the patch instead of the master branch, this may indeed be a
bug in how we configure the git plugin to work with the Gerrit
trigger.
(It just occurred to me it may need to be configured differently fro
pre and post-merge jobs)
We will need to investigate this more deeply (compare git hashes jobs
get before and after merge, etc.)
But if its a ff-only repo, this means that you can't merge a patch
that needs a rebase, so if patches were rebased, and build_artifacts
runs post-merge, it should be impossible to get it to run on
non-rebased code.
--
Barak Korren
bkorren(a)redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/devel