Hello Ondra. Thanks. It seems that the manual job populates SDK from custom repo only for the VMs under test, but the mock where the python test code runs does not use it from there. So the release of bumped version will be good idea. Anton. On Thu, May 11, 2017 at 8:20 PM, Ondra Machacek <omachace@redhat.com> wrote:
On Thu, May 11, 2017 at 8:11 PM, Anton Marchukov <amarchuk@redhat.com> wrote:
On Thu, May 11, 2017 at 8:03 PM, Ondra Machacek <omachace@redhat.com> wrote:
*15:50:44* [basic_suit_el7] Updated:
*15:50:44* [basic_suit_el7] python-ovirt-engine-sdk4.x86_64 0:4.2.0-1.a0.20170511git210c375.el7.centos
This is incorrect version. The correct one is:
python-ovirt-engine-sdk4-4.2.0-1.a0.20170511gitcd0adb4.el7. centos.x86_64.rpm <http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_master_build-artifacts-el7-x86_64/71/artifact/exported-artifacts/python-ovirt-engine-sdk4-4.2.0-1.a0.20170511gitcd0adb4.el7.centos.x86_64.rpm>
From this build:
http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_maste r_build-artifacts-el7-x86_64/71/
Sounds like we have a problem if the version different only by git hashes. They are not ordered.
I suggest we just merge the version bump at https://gerrit.ovirt.org/#/ c/76732/ and then see which version it will install.
Any objections to that?
OK, I will do a proper release.
-- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat
-- Anton Marchukov Senior Software Engineer - RHEV CI - Red Hat