<div dir="ltr">Does anyone have any other input or objections about anything *other than* which repos we're using?<div><br></div><div>Best wishes,</div><div>Greg</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 14, 2017 at 7:11 AM, Sandro Bonazzola <span dir="ltr"><<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Tue, Feb 14, 2017 at 10:14 AM, Martin Perina <span dir="ltr"><<a href="mailto:mperina@redhat.com" target="_blank">mperina@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_-4453750956656469916h5">On Tue, Feb 14, 2017 at 9:54 AM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 14 February 2017 at 09:53, Martin Perina <<a href="mailto:mperina@redhat.com" target="_blank">mperina@redhat.com</a>> wrote:<br>
><br>
><br>
> On Mon, Feb 13, 2017 at 9:59 PM, Greg Sheremeta <<a href="mailto:gshereme@redhat.com" target="_blank">gshereme@redhat.com</a>> wrote:<br>
>><br>
>> On Mon, Feb 13, 2017 at 3:55 PM, Eyal Edri <<a href="mailto:eedri@redhat.com" target="_blank">eedri@redhat.com</a>> wrote:<br>
>>><br>
>>><br>
>>><br>
>>> On Mon, Feb 13, 2017 at 10:34 PM, Martin Perina <<a href="mailto:mperina@redhat.com" target="_blank">mperina@redhat.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Hi,<br>
>>>><br>
>>>> why is this package not contained also in ovirt-master-snapshot<br>
>>>> repository [6]? Most of developers are using ovirt-master-snapshot, because<br>
>>>> this is the official repository for oVirt depelopers as mentioned in [7] and<br>
>>>> [8]. AFAIK there was not yet any official announcement that every developer<br>
>>>> should switch from ovirt-master-snapshot to ovirt-tested-master ...<br>
>>><br>
>>><br>
>>> I think we should make it official then for master, we've hit too many<br>
>>> issues in the past weeks due to this repository, that I don't want to see<br>
>>> new projects added to it.<br>
><br>
><br>
> You've run into issues, because<br>
><br>
> migration to the "new" system is not well prepared. I'm still a bit angry<br>
> that you have forced me to migrate all ovirt-engine-extensions* projects<br>
> into standard CI (which took me more than 2 days) by breaking existing build<br>
> jobs which worked fine until recent changes. And I had to do fast that<br>
> otherwise I won't be able to provide new build for upstream 4.1.0 async and<br>
> 4.1.1 builds ...<br>
<br>
I think there is some miss-communication here. The old '-snapshot'<br>
repo is causing issues because of the way it is built. We want people<br>
to move away from it. However, we did not intend to force anyone to<br>
move. It is still there, and the nightly jobs still update it with all<br>
the packages that have been in it so far.<br>
<br>
<a href="http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/" rel="noreferrer" target="_blank">http://jenkins.ovirt.org/job/o<wbr>virt_master_publish-rpms_night<wbr>ly/</a><br>
<br>
I really don't see how any of the recent changes forced you to change<br>
your project's own jobs, but it is a good thing if you did.<br></blockquote></div></div><div><br><div>Well, build jobs just started to fail and I discussed with either you or Gil and you just told me that why it's failing and the only solution is to move std CI.<br></div><div>But let's leave this behind us, </div> <div>ovirt-engine-extensions* move to std-CI and build jobs are working now correctly ...<br><br></div></div><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> So I don't have an issue to move from ovirt-master-snapshot repos to<br>
> ovirt-tested-master repos, but please do that properly:<br>
><br>
> 1. Announce on mailing lists that every developer should switch at least a<br>
> week before the change<br>
<br>
We were planning, since all repos currently exist side-by-side we saw<br>
no rush to do that.<br>
<br>
> 2. Update all developer related documentation about this change<br>
<br>
Well, I'm not sure where such things are documented currently, but<br>
that is a reasonable request.<br>
<br>
> 2. Maintain both repos for a week and only after that turn off<br>
> ovirt-master-snapshots repos<br>
<br>
We did not turn it off yet. It is still there. The only thing that<br>
happened is that the new JS projects, that were never in that repo to<br>
begin with, chose to forgo publishing to it.<br></blockquote></span><div><br><div>Sure, that's why I asked to put this ovirt-js-dependencies package into ovirt-master-snapshot repo, which all developers are using ...<br></div> </div><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> Exported artifacts is not enough, please provide ovirt-release-tested-master<br>
> RPM which will include all necessary repositories same way as we currenlty<br>
> have in ovirt-release-master<br>
<br>
There is some subtle distinction here that needs to be well understood.<br>
Some repos are build to emulate an oVirt release, and all or most of<br>
the packages are collected in them. The 'tested' repo is an example of<br>
such a repo. For such repos it makes sense to create a<br>
'*-release-*.rpm'.<br></blockquote></span><div><br><div>So ovirt-release-master RPM will add repositories with needed packages to develop engine/VDSM. For engine development it means you have following packages:<br><br></div><div>ovirt-master-snapshot:<br></div><div> otopi<br></div><div> ovirt-host-deploy<br></div><div> ovirt-setup-lib<br></div><div> ovirt-vmconsole<br><br></div><div>ovirt-master-snapshot-static<br></div><div> ovirt-engine-wildfly<br></div><div> ovirt-engine-wildfly-overlay<br><br>ovirt-master-patternfly1-noarc<wbr>h-epel<br> patternfly1<br><br></div><div>There are other packages, but those are needed only when developing relevant parts of engine (for example "unboundid-ldapsdk" needed for ovirt-engine-extension-aaa-lda<wbr>p).<br><br></div><div>So in my opinion if you want to switch to ovirt-latest-tested repo, we need to have available also those dependencies, that's why I think it's required to have ovirt-release-latest-tested RPM which will install all repos to develop and even install/run master oVirt from RPM.<br><br></div></div></div></div></div></blockquote><div><br></div></div></div><div>Make sense to me. Current effort anyway it to reach a point where nothing need to be changes, just the content of ovirt-master-snapshot will be genertared from latest-tested instead of from jenkins master nightly publisher job.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div></div></div><span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
The 'exported-artifacts' repos are meant to allow "upstream" or<br>
"build-dependency" projects to have their own release stream that is<br>
independent of oVirt's release stream. For such repos it makes little<br>
sense to keep a '*-release-*.rpm'.<br>
<br>
All projects that have a 'build-articats job now have an<br>
'exported-artifacts' repo and their packages are submitted to OST so<br>
eventually also end up in the 'tested' repo. It is left to the<br>
consuming projects to pick which repo to use depending on how tightly<br>
are they coupled with consumed packages.<br>
<span class="m_-4453750956656469916m_1790693455426653032gmail-HOEnZb"><font color="#888888"><br>
<br>
--<br>
Barak Korren<br>
<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a><br>
RHCE, RHCi, RHV-DevOps Team<br>
<a href="https://ifireball.wordpress.com/" rel="noreferrer" target="_blank">https://ifireball.wordpress.co<wbr>m/</a><br>
</font></span></blockquote></span></div><br></div></div>
<br></span><span class="">______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org" target="_blank">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/devel</a><br></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><span class=""><div class="m_-4453750956656469916gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Sandro Bonazzola<br>Better technology. Faster innovation. Powered by community collaboration.<br>See how it works at <a href="http://redhat.com" target="_blank">redhat.com</a></div></div></div></div></div></div></div></div>
</span></div></div>
<br>______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Greg Sheremeta, MBA<br>Red Hat, Inc.<br>Sr. Software Engineer<br><a href="mailto:gshereme@redhat.com" target="_blank">gshereme@redhat.com</a><br></div></div></div>
</div>