Hi Martin,
yes.
please let me know once you merge the patches and if they fail running
together I will re-add them to run at the same time on 4.2.
thanks,
Dafna
On Mon, Jul 9, 2018 at 9:30 AM, Martin Perina <mperina(a)redhat.com> wrote:
Hi,
so WildFly 13 successfully landed on all master repos, but it's still
missing in 4.2 repos [1], both ovirt-engine-wildfly and
ovirt-engine-wildfly-overlay packages are not there. So do we need to have
the same hack for 4.2 CQ as for master? I'm asking because both wildfly and
wildfly-overlay uses their master branches for both oVirt master and oVirt
4.2 releases, so what do we need to do to make them available for oVirt 4.2?
Thanks
Martin
[1]
https://plain.resources.ovirt.org/repos/ovirt/tested/4.2/rpm/el7
On Wed, Jul 4, 2018 at 8:58 AM, Barak Korren <bkorren(a)redhat.com> wrote:
>
>
> On 4 July 2018 at 08:41, Martin Perina <mperina(a)redhat.com> wrote:
>
>> Hi,
>>
>> I've just checked [1] and [2] repos and ovirt-engine-wildfly*-13
>> packages are not yet available on those repos. Any luck with passing those
>> packages through CQ?
>>
>
> Unfortunately an unrelated regressions caused the dependent changes to
> end up in different batches during the bisection search, and they were
> dropped again.
>
> Here is finally a test running with the two of them together and nothing
> else:
>
https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8563/
>
>
>
>>
>> Thanks
>>
>> Martin
>>
>> [1]
https://plain.resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/
>> [2]
https://plain.resources.ovirt.org/repos/ovirt/tested/master/rpm/el7/
>>
>>
>> On Tue, Jul 3, 2018 at 12:30 PM, Barak Korren <bkorren(a)redhat.com>
>> wrote:
>>
>>>
>>>
>>> On 3 July 2018 at 12:26, Martin Perina <mperina(a)redhat.com> wrote:
>>>
>>>>
>>>>
>>>> On Tue, Jul 3, 2018 at 11:03 AM, Ehud Yonasi <eyonasi(a)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?
>>>
>>>
>>>
>>>
>>> --
>>> 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.
>>
>
>
>
> --
> 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.
_______________________________________________
Infra mailing list -- infra(a)ovirt.org
To unsubscribe send an email to infra-leave(a)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/infra@ovirt.org/
message/RBQCLG2NDSIWUWAYWMGC7YCSAYP6WQ3H/