21 Sep
2012
21 Sep
'12
10:58 p.m.
Yes,as long as this happens soon, it is a safe assumption that almost all existing tools ignored the return code (because they couldn't use it till recently). Or allow the error code field to be null in the database (shown as blank or not available in the web interface). Peter On Friday, September 21, 2012, Scott McManus wrote:
Excellent. :)
I had considered adding an exit code column but had avoided touching the database at first. Migration could be a little tricky. If we assume that there are few (or even zero) tools checking stdout/stderr/exit codes, then we could assume that a job failed if it had any stderr text. Then we would need appropriate backfilled exit codes - say, 0 for success and -1 for error. Would that make sense?
-Scott