Modify ↓
#371 closed enhancement (fixed)
Slave -s option should cause exit?
| Reported by: | anonymous | Owned by: | cmlenz |
|---|---|---|---|
| Priority: | major | Milestone: | 0.6 |
| Component: | General | Version: | dev |
| Keywords: | Cc: | ||
| Operating System: | Linux |
Description
The bitten-slave -s option causes the slave to run only once, then exit. However, the slave waits for a build to become available if none is available.
Surely it would be more helpful if the slave exited immediately if there was no build available? That way it would be easier to put bitten-slave in a cron job etc.
As it happens, in order to integrate bitten-slave so that it only runs at certain times of the day is quite complex.
Attachments (0)
Change History (2)
comment:1 Changed 15 years ago by dfraser
- Resolution set to fixed
- Status changed from new to closed
comment:2 Changed 15 years ago by osimons
#353 closed as duplicate.
Note: See
TracTickets for help on using
tickets.
r599 adds a --no-loop option which will cause the slave to run a single check, run any required builds, and then exit. This should work in concert with -s or --single-build if both are specified (i.e. it will run at most one build after checking and then quit).