<div dir="ltr">I think there's a rush to add FC27 and S390 (unrelated?) to the build. If either fail, right now, I don't think we should be too concerned with them.<div>In the very near future we should be, though.</div><div>Y.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 22, 2018 at 9:06 PM, Dafna Ron <span dir="ltr"><<a href="mailto:dron@redhat.com" target="_blank">dron@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><div><div>Hi All, <br><br></div>We have been seeing a large amount of changes that are not deployed into tested lately because of failed build-artifacts jobs so we decided that perhaps we need to explain the importance of fixing a failed build-artifacts job. <br><br></div>If a change failed a build-artifacts job, no matter what platform/arch it failed in, the change will not be deployed to tested. <br><br></div><div>Here is an example of a change that will not be added to tested: <br></div><div><br><img src="cid:ii_161bed0f92ce8b2b" alt="Inline image 1" width="534" height="264"><br><br></div><div>As you can see, only one of the build-artifacts jobs failed but since the project specify that it requires all of these arches/platforms, the change will not be added to tested until all of the jobs are fixed. <br><br></div><div>So what can we do? <br><br></div><div>1. Add the code which builds-artifacts to 'check-patch' so you'll get a -1 if a build failed (assuming you will not merge with -1 from CI). <br></div><div>2. post merge - look for emails on failed artifacts on your change (you will have to fix the job and then re-trigger the change)<br></div><div>3. you can see all current broken failed artifacts jobs in jenkins under 'unstable critical' view [1] and you will know if your project is being deployed. <br>4. Remove the broken OS from your project ( either from Jenkins or from
your automation dir if you're using V2 ) - ask us for help! this should
be an easy patch<br>5.Don't add new OS builds until you're absolutly sure they work ( you can
add check-patch to keep testing it, but don't add build-artifacts until
its stable ).<br><br></div><div>Please contact myself or anyone else from the CI team for assistance or questions and we would be happy to help. <br><br>[1] <a href="http://jenkins.ovirt.org/" target="_blank">http://jenkins.ovirt.org/</a><br><br></div><div>Thank you, <br><br></div><div>Dafna<br><br></div><div><br></div><div><br></div><div><br></div><div><br></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></div>