[YABI-246] RFC Using exit codes to control aborting, blocking workflows

[ccgbuildbot]

[reporter="ccgadmin", created="Tue, 19 Mar 2013 12:52:14 +0800"]

[ccgbuildbot]

[author="ccgadmin", created="Mon, 27 May 2013 14:33:43 +0800"]

https://code.google.com/p/yabi/issues/detail?id=246&q=RFC

[ccgbuildbot]

[author="ccgadmin", created="Mon, 27 May 2013 14:35:23 +0800"]

An improved method of blocking/aborting automatically based on return code.

[ccgbuildbot]

[author="ccgadmin", created="Mon, 27 May 2013 14:38:09 +0800"]

http://tldp.org/LDP/abs/html/exitcodes.html

..and to quote:

There has been an attempt to systematize exit status numbers (see /usr/include/sysexits.h), but this is intended for C and C++ programmers. A similar standard for scripting might be appropriate. The author of this document proposes restricting user-defined exit codes to the range 64 - 113 (in addition to 0, for success), to conform with the C/C++ standard. This would allot 50 valid codes, and make troubleshooting scripts more straightforward.

[ccgbuildbot]

[author="ccgadmin", created="Mon, 27 May 2013 14:39:40 +0800"]

Just spoke to Kevin. A means to satisfy this requirement is for a specific exit code for a specific task/workflow/tool to trigger an abort for the complete workflow. That is to cascade the abort to all other tasks/jobs in the workflow.