Adding infra as well.

I see a very strange thing happening on the build artifacts jobs:

On [1] we see a successful build of 1.2.10 built in build-artifacts, but on the 2 patches merged after it, its back to 1.2.9 [2].
Is it possible that the 2 patches merged after the version bump weren't rebased on the version branch and were built using older code? 
I think what we're seeing is a race of 3 patches merged all at the same time ( jenkins shows same datetime on the builds ) and it might be that the 2 builds that show older version
run before the version bump was done, even if it shows otherwise on CI.

I've run manually the job again and it nows produces 1.2.10 as expected [3], so the job should work once the rpms are deployed ( 30 min ~ )


I believe this is one of the things Zuul will solve, I can't think on something we can do at the moment to prevents such issues, 

Barak - any ideas?

The project has 'fast forward only' mode in Gerrit.

[1] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-el7-x86_64/23/
[2] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-el7-x86_64/24/
[3] http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-el7-x86_64/26/console

On Sun, Dec 11, 2016 at 11:01 AM, Piotr Kliczewski <pkliczew@redhat.com> wrote:
Yes, version bump was merged.

11 gru 2016 09:57 "Eyal Edri" <eedri@redhat.com> napisał(a):
Was the version bumped pushed to the repo itself in Gerrit? 
I.e - does build-artifacts builds now the new version 1.2.10? 

On Fri, Dec 9, 2016 at 9:33 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:


Il 09/Dic/2016 18:45, "Piotr Kliczewski" <pkliczew@redhat.com> ha scritto:
Here [1] is the manual build. We need to check publisher.


Manual builds are not published by nightly publisher. Manual builds are meant for releases or for testing. I haven't the laptop with me tonight and tomorrow. Didi, Lev can you handle Sunday morning?




9 gru 2016 18:36 "Piotr Kliczewski" <pkliczew@redhat.com> napisał(a):
Both us and ds rpms were built. Is it possible to check why new version was not published to the repo?

9 gru 2016 18:07 "Martin Perina" <mperina@redhat.com> napisał(a):
Piotr, are you able to publish new vdsm-jsonrpc-java 1.2.10 into ovirt-4.0-snapshot repo [1]? Or only someone from integration team can do that?

Thanks


On Fri, Dec 9, 2016 at 4:54 PM, Yaniv Kaul <ykaul@redhat.com> wrote:
See [1]:

+ yum install --nogpgcheck -y --downloaddir=/dev/shm ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*'
13:55:25 Error: Package: ovirt-engine-backend-4.0.7-0.0.master.20161208233116.git3dff5ce.el7.centos.noarch (alocalsync)
13:55:25            Requires: vdsm-jsonrpc-java >= 1.2.10
13:55:25            Available: vdsm-jsonrpc-java-1.2.9-1.20161208102442.gite5c0c8e.el7.centos.noarch (alocalsync)
13:55:25                vdsm-jsonrpc-java = 1.2.9-1.20161208102442.gite5c0c8e.el7.centos



[1] http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86_64/319/console

_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/devel


_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/devel


_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/devel



--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)



--
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)