On Tue, Jul 3, 2018 at 12:30 PM, Barak Korren <bkor...@redhat.com> wrote:
> > > On 3 July 2018 at 12:26, Martin Perina <mper...@redhat.com> wrote: > >> >> >> On Tue, Jul 3, 2018 at 11:03 AM, Ehud Yonasi <eyon...@redhat.com> wrote: >> >>> Suspected patch: >>> >>> https://gerrit.ovirt.org/#/c/91555/ >>> >>> Link to job: >>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8542/ >>> >>> Link to all logs: >>> http://jenkins.ovirt.org/job/ovirt-master_change-queue-teste >>> r/8542/artifact/exported-artifacts/ >>> >>> Relevant error snippet: >>> >>> Error: ovirt-engine-wildfly-overlay conflicts with >>> ovirt-engine-wildfly-13.0.0-1.el7.x86_64 >>> >>> >> OK, I thought that I can do stepped approach: >> >> 1. Push ovirt-engine-wildfly-13 RPM into the repos >> 2. Push ovirt-engine-wildfly-overlay-13 RPM, which requires >> ovirt-engine-wildfly-13, into repos >> >> But it seems that due to serial nature of our CQ it's not possible, so >> can we pass both patches [1] and [2] though CQ at once? >> >> > Ehud will handle pushing them through the CQ together (its a matter of > timing things so they both get added to the CQ while it is busy with other > things). > > I wonder - could we merge those projects together to avoid this situation > in the future? What is the relationship between 'ovirt-engine-wildfly' > and the Wildfly upstream? > ovirt-engine-wildfly is packaged upstream WildFly project ovirt-engine-wildfly-overlay could contain our customization which we need to run oVirt, but which are not (yet) released on upstream WildFly distribution So I'd really like to keep them separate > > > > > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > -- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o.
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/57V2JPNC5YKO5TO34J4G2BI5YAZ3EZ75/
