The "backoffice" command:
Run backoffice processing on the repositories listed. If no repository is specified, run it on the repository of the local checkout.
This might be done by a cron job or similar to make sure backoffice processing happens periodically. Or, the --poll option can be used to run this command as a daemon that will periodically invoke backoffice on a collection of repositories.
If only a single repository is named and --poll is omitted, then the backoffice work is done in-process. But if there are multiple repositories or if --poll is used, a separate sub-process is started for each poll of each repository.
- Show what this command is doing.
- --logfile FILE
- Append a log of backoffice actions onto FILE.
- --min N
- When polling, invoke backoffice at least once every N seconds even if the repository never changes. 0 or negative means disable this feature. Default: 3600 (once per hour).
- --poll N
- Repeat backoffice calls for repositories that change in appoximately N-second intervals. N less than 1 turns polling off (the default). Recommended polling interval: 60 seconds.
- Enable debugging output on stderr
Options intended for internal use only which may change or be discontinued in future releases:
- Do not queue up or wait for a backoffice job to complete. If no work is available or if backoffice has run recently, return immediately.
- Always run backoffice, even if there is a lease conflict. This option implies --nodelay. This option is added to secondary backoffice commands that are invoked by the --poll option.