id summary reporter owner description type status priority milestone component version resolution keywords cc os 534 [Patch] Augment bitten-slave exit code for --no-loop. mpotter@… "The `bitten-slave` currently returns various exit codes for various failure cases. If would be nice if when used with the `--no-loop` option, `bitten-slave` could return info on if it built anything or not. `bitten-slave --no-loop --single` will build 0 or 1 targets. `bitten-slave --no-loop` will build 0 or many targets. Since 0 is normally considered a success case for commands, and any other value an error: * If ""`bitten-slave --no-loop ...`"" builds no targets * return 1. * If ""`bitten-slave --no-loop ...`"" builds 1 or more targets, * return 0. * If ""`bitten-slave ...`"" fails, * return the appropriate error code as it currently does. Use-case: I was thinking I could wrap bitten-slave in a script and use the `--no-loop` and `--single` options with various slave configurations to implement a simple priority system. Pseudo-code: {{{ #!sh do { do { # Build all high-priority targets bitten-slave --no-loop -f HighPriority.ini ... # Try to build one medium or high priority target bitten-slave --no-loop --single -f MedOrHighPriority.ini ... # loop back in case a new high priority has appeared } while ( errorlevel == 1 ); # Build one target. Wait if there are not any available. bitten-slave --single -f AnyPriority.ini ... # If not an error, loop back } while ( errorlevel == 0 ); }}}" enhancement new major 0.6.1 Build slave 0.6b2 mpotter@…