bkr-job-clone man page
bkr-job-clone — Clone existing Beaker jobs
bkr job-clone [options] [–wait] [–dry-run] [–xml] [–pretty-xml] <taskspec>…
Specify one or more <taskspec> arguments to be cloned. A new job will be created for each argument. The cloned job ids will be printed to stdout.
The <taskspec> arguments follow the same format as in other bkr subcommands (for example, J:1234). See Specifying tasks in bkr(1).
Only jobs and recipe sets may be cloned.
When this option is given, the command will not terminate until the clone job has finished running.
Print the job XML before submitting it.
Print the job XML in a easily readable format before submitting it.
Run through the job-clone process without actually submitting the cloned job
- --job-owner <username>
Clone the job on behalf of <username>. The cloned job will be owned by <username> rather than the cloning user.
The cloning user must be a submission delegate of <username>. Users can add other users as submission delegates on their Preferences page in Beaker’s web UI.
Common bkr options are described in the Options section of bkr(1).
Non-zero on error, otherwise zero. A failure in cloning any of the arguments is considered to be an error, and the exit status will be 1.
Clone job 1234 and wait for it to finish:
bkr job-clone --wait J:1234
The Beaker team <email@example.com>
2013, Red Hat, Inc