<p dir="ltr">With the standard ci is not possible, as the idea of 'unstable' and 'failure' is quite ambiguous and usually leads to confusion.</p>
<p dir="ltr">So we decided not to have that third state, runs either pass, or do not.</p>
<p dir="ltr">You can print/archive/log anything you want to allow you help debugging the issue, but on the ci side, the decision is to -1 or not a patch, so just two states.</p>
<p dir="ltr">Out of the standard you can define post-build scripts that can modify the state of the job (you can set it as failed, unstable or even pass a job that otherwise would be marked as failed).</p>
<p dir="ltr">Though for the reasons I exposed, I don't recommend that.</p>
<p dir="ltr">David Caro</p>
<div class="quote">El 25/4/2016 8:30 p. m., Fabian Deutsch <fdeutsch@redhat.com> escribió:<br type='attribution'><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hey, <br>
<br>
is there a way how a yamlized job can become unstable? <br>
<br>
I'd liek to run some sanity node tests after a run, and mark a run as <br>
unstable if this happens. <br>
According to the jenkins docs, a job is unstable if one or more publishers fail. <br>
<br>
Can this be achieved with yamlized jobs? <br>
<br>
- fabian <br>
_______________________________________________ <br>
Infra mailing list <br>
Infra@ovirt.org <br>
http://lists.ovirt.org/mailman/listinfo/infra <br>
</p>
</blockquote></div>