1BKR-JOB-SUBMIT(1)                   Beaker                   BKR-JOB-SUBMIT(1)
2
3
4

NAME

6       bkr-job-submit - Submit job XML to Beaker
7

SYNOPSIS

9       bkr job-submit [options]
10         [--debug] [--convert] [--combine] [--ignore-missing-tasks]
11         [--dry-run | --wait]
12         [<filename>...]
13
14

DESCRIPTION

16       Reads Beaker job XML descriptions and submits them to Beaker.
17
18       Specify  one  or  more filenames containing job XML to be submitted. If
19       multiple filenames are given, each one is submitted as a separate  job.
20       If  no  filenames  are  given,  job XML is read from stdin. The special
21       filename '-' also reads from stdin.
22

OPTIONS

24       --debug
25              Legacy option, replaced by '--xml'
26
27       --xml  Print the job XML before submitting it.
28
29       --convert
30              Attempt to convert legacy RHTS XML to Beaker XML. Use this  with
31              --xml and --dry-run to grab the converted XML without submitting
32              it.
33
34       --combine
35              If more than one job XML argument is given, the recipe sets from
36              each  job  are  extracted  and combined into a single job before
37              submission.
38
39       --ignore-missing-tasks
40              If the job refers to tasks which are not known to the scheduler,
41              silently discard these from the recipe. Normally this is a fatal
42              error which prevents submission of the job.
43
44       --dry-run
45              Do not submit the job(s) to Beaker. Use this with --xml  to  see
46              what would be submitted.
47
48       --wait Watch  the newly submitted jobs for state changes and print them
49              to stdout.  The command will not exit until all  submitted  jobs
50              have finished. See bkr-job-watch(1).
51
52       --job-owner <username>
53              Submit  the  job on behalf of <username>. The submitted job will
54              be owned by <username> rather than the submitting user.
55
56              The existing user attribute in the job XML will be overridden if
57              set.
58
59              The submitting user must be a submission delegate of <username>.
60              Users can add other users as submission delegates on their Pref‐
61              erences page in Beaker's web UI.
62
63       Common bkr options are described in the Options section of bkr(1).
64

EXIT STATUS

66       1 if any jobs failed submission or execution, otherwise zero.
67

EXAMPLES

69       Submit a job and watch its progress on stdout:
70
71          bkr job-submit --wait my-beaker-job.xml
72

SEE ALSO

74       bkr(1)
75

AUTHOR

77       The Beaker team <beaker-devel@lists.fedorahosted.org>
78

80       2013, Red Hat, Inc
81
82
83
84
8526.3                             Jan 31, 2019                BKR-JOB-SUBMIT(1)
Impressum