Ticket #2225 (closed enhancement: fixed)
LoggingBuildStep should take an option to specify which exit codes indicate errors.
| Reported by: | tom.prince | Owned by: | tom.prince |
|---|---|---|---|
| Priority: | major | Milestone: | 0.8.7 |
| Version: | 0.8.2 | Keywords: | |
| Cc: |
Change History
comment:1 Changed 13 months ago by Tom Prince
- Status changed from new to closed
- Resolution set to fixed
comment:2 Changed 13 months ago by Dustin J. Mitchell
Remove local 'FakeCmd?' fake, add more interface tests for FakeRemoteCommand?
Refs #2225
Changeset: 94ccf27b379a68a247ded9090fbb807879442a61
comment:3 Changed 13 months ago by Tom Prince
Factor checking of cmd.rc to allow other successful results.
This provides an argument successfulRC to RemoteCommand?, to specify some non-zero RCs as successes.
Fixes #2225.
Changeset: eaf13be615110d18c7c1aec7ea474c5ac34b0273
comment:4 Changed 13 months ago by Dustin J. Mitchell
Remove local 'FakeCmd?' fake, add more interface tests for FakeRemoteCommand?
Refs #2225
Changeset: 94ccf27b379a68a247ded9090fbb807879442a61
Note: See
TracTickets for help on using
tickets.
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
Factor checking of cmd.rc to allow other successful results.
This provides an argument successfulRC to RemoteCommand?, to specify some non-zero RCs as successes.
Fixes #2225.