1BKR-JOB-CLONE(1) Beaker BKR-JOB-CLONE(1)
2
3
4
6 bkr-job-clone - Clone existing Beaker jobs
7
9 bkr job-clone [options]
10 [--wait] [--dry-run] [--xml] [--pretty-xml] <taskspec>...
11
12
14 Specify one or more <taskspec> arguments to be cloned. A new job will
15 be created for each argument. The cloned job ids will be printed to
16 stdout.
17
18 The <taskspec> arguments follow the same format as in other bkr subcom‐
19 mands (for example, J:1234). See Specifying tasks in bkr(1).
20
21 Only jobs and recipe sets may be cloned.
22
24 --wait When this option is given, the command will not terminate until
25 the clone job has finished running.
26
27 --xml Print the job XML before submitting it.
28
29 --pretty-xml
30 Print the job XML in a easily readable format before submitting
31 it.
32
33 --dry-run
34 Run through the job-clone process without actually submitting
35 the cloned job
36
37 --job-owner <username>
38 Clone the job on behalf of <username>. The cloned job will be
39 owned by <username> rather than the cloning user.
40
41 The cloning user must be a submission delegate of <username>.
42 Users can add other users as submission delegates on their Pref‐
43 erences page in Beaker's web UI.
44
45 Common bkr options are described in the Options section of bkr(1).
46
48 Non-zero on error, otherwise zero. A failure in cloning any of the ar‐
49 guments is considered to be an error, and the exit status will be 1.
50
52 Clone job 1234 and wait for it to finish:
53
54 bkr job-clone --wait J:1234
55
57 bkr(1)
58
60 The Beaker team <beaker-devel@lists.fedorahosted.org>
61
63 2013-2023 Red Hat, Inc.
64
65
66
67
6828.3 Nov 17, 2023 BKR-JOB-CLONE(1)