<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 12, 2017 at 1:44 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 12 April 2017 at 13:33, Piotr Kliczewski <<a href="mailto:pkliczew@redhat.com">pkliczew@redhat.com</a>> wrote:<br>
><br>
> I need to merge them and release before I can make the engine build to<br>
> succeed and if<br>
> the are api changes or dependency changes like in this thread I do not want<br>
> my changes<br>
> to be used without the engine update.<br>
><br>
> Sorry but we can't workaround it without making sure that we are using<br>
> correct versions.<br>
<br>
</span>So this is a case where change A in project X needs change B in project<br>
Y. We will eventually allow some syntax of specifying something like<br>
this (probably in the commit message like OpenStack) to ensure they are<br>
merged and tested together. In the meantime the closest approximation we<br>
have is merging such changes as simultaneously as possible.<br></blockquote><div><br></div><div>It is not possible due to maven central taking time to propagate the artifact.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Consider what it means when an API-breaking change is merged into vdsm<br>
master for example without the required engine-side change. It means<br>
that from that point on, all further vdsm changes will need to wait<br>
until the engine change is merged.<br>
<span class=""><br>
>> If we limit the CI system to only use tagged stuff it becomes useless.<br>
><br>
> I makes sense for OST.<br>
<br>
</span>As I've commented before, you need to be clear what you mean when you<br>
say 'OST'. If you clone the OST repo and run it, or use the manual job<br>
you end up using the releases repos or (for master) the 'tested' repos.<br></blockquote><div><br></div><div>Which seems not to be the case for the last failure.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The point of the 'experimental' flow is to tell you if the sum total of<br>
oVirt's 'master' branches (or more general, branches by version) is stable<br>
or not. Not running it on the latest patches would not make sense.<br>
<div class="HOEnZb"><div class="h5"><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>
</div></div></blockquote></div><br></div></div>