<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 10, 2017 at 3:17 PM, Martin Sivak <span dir="ltr"><<a href="mailto:msivak@redhat.com" target="_blank">msivak@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> The thing about specifying the oVirt releases in a test file is that<br>
> this can lead to weird edge cases. Suppose for example we have the<br>
> same text file in two branches, specifying the same oVirt releases?<br>
> I'd like the specification to at least guarantee that an oVirt release<br>
> can take builds from at most one branch.<br>
<br>
Right, this can indeed be an issue. But the only way you can enforce<br>
this without touching repository metadata is to have a separate repo<br>
with the publisher configuration.<br>
<br>
I believe Sandro uses something like that here:<br>
<a href="https://gerrit.ovirt.org/gitweb?p=releng-tools.git;a=summary" rel="noreferrer" target="_blank">https://gerrit.ovirt.org/<wbr>gitweb?p=releng-tools.git;a=<wbr>summary</a></blockquote><div><br><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;display:inline">Yes, adding exact package version</div> <div class="gmail_default" style="font-family:arial,helvetica,sans-serif;display:inline">into a specific file under releases worked fine so far and I don't see any issue with that.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;display:inline">And I definitely don't want to create branches per oVirt version in smaller projects, because we reuse the same version for multiple oVirt major releases. So adding branch per version is a waste of time, when we can compose repository for a version using text file under releases directory.<br><br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
You can always chose to trust us to not misconfigure the project like that :)<br>
<br>
Martin<br>
<br>
On Tue, Jan 10, 2017 at 2:51 PM, Barak Korren <<a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a>> wrote:<br>
> On 10 January 2017 at 15:32, Martin Sivak <<a href="mailto:msivak@redhat.com">msivak@redhat.com</a>> wrote:<br>
>> This is on topic. We can (and should) take inspiration in how others<br>
>> are doing it or we will be repeating the mistakes again and again.<br>
>><br>
>> Travis automation notices pushes to all branches and then uses<br>
>> conditional checks to decide if anything needs to be done. We should<br>
>> do the same and put all that to the automation directory. Including<br>
>> patch testing, building, platforms and publishing.<br>
><br>
> I still stand behind my assertion that Travis does not do integration.<br>
> I'll try to clarify what I mean by that. The thing is that Travis<br>
> always looks at a single repo. AFAIK it never tries to look across<br>
> different repositories and compose them together to create a final<br>
> product. You can of-course rig things together so that this sort of<br>
> happens - you make it upload the artifacts somewhere and then trigger<br>
> something else to do the composite test.<br>
><br>
> The thing about specifying the oVirt releases in a test file is that<br>
> this can lead to weird edge cases. Suppose for example we have the<br>
> same text file in two branches, specifying the same oVirt releases?<br>
> I'd like the specification to at least guarantee that an oVirt release<br>
> can take builds from at most one branch.<br>
><br>
> --<br>
> Barak Korren<br>
> <a href="mailto:bkorren@redhat.com">bkorren@redhat.com</a><br>
> RHCE, RHCi, RHV-DevOps Team<br>
> <a href="https://ifireball.wordpress.com/" rel="noreferrer" target="_blank">https://ifireball.wordpress.<wbr>com/</a><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></div></div>