since these issues seem rare from my POV, we do not prioritize the effort to create a syntax to specify inter-change dependencies, even though the CQ core algorithm was written with that in mind.
So for the time being you need to ask us to resolve this when it arises. On 3 July 2018 at 13:34, Greg Sheremeta <gsher...@redhat.com> wrote: > I've also had this same need with projects that can't be combined, so I > think we need an official solution. Is it just to ask you? There is no way > for us to do it? > > Greg > > On Tue, Jul 3, 2018, 6:32 AM 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- >>>> tester/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? >> >> >> >> >> -- >> Barak Korren >> RHV DevOps team , RHCE, RHCi >> Red Hat EMEA >> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted >> _______________________________________________ >> Infra mailing list -- in...@ovirt.org >> To unsubscribe send an email to infra-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/in...@ovirt.org/ >> message/MJIFEI4U3M4SJHEP7GO4CJLHHYO2SOEI/ >> > -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
_______________________________________________ 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/AXYGHELGSGGMIK3IQBLBB7HGXMTJAY4A/
