Yes,as long as this happens soon, it is a safe assumption that almost<div>all existing tools ignored the return code (because they couldn&#39;t use</div><div>it till recently).</div><div><br></div><div>Or allow the error code field to be null in the database (shown as blank</div>
<div>or not available in the web interface).</div><div><br></div><div>Peter<span></span><br><div><br>On Friday, September 21, 2012, Scott McManus  wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div style="font-size:12pt;font-family:times new roman,new york,times,serif">Excellent. :)<br><br>I had considered adding an exit code column but had avoided touching <br>the database at first. Migration could be a little tricky. If we assume that<br>
there are few (or even zero) tools checking stdout/stderr/exit codes, then<br>we could assume that a job failed if it had any stderr text. Then we would<br>need appropriate backfilled exit codes - say, 0 for success and -1 for error.<br>
Would that make sense?<br><br>-Scott<br><br></div></div></blockquote></div></div>