BKR-JOB-CLONE(1)

📦
version 29.2 · 3 versions
, in epel 9

💖 NAME 💖

bkr-job-clone — clone existing Beaker jobs ✨ and welcome to the bkr-job-clone(1) bestie era 💅

🎀 SYNOPSIS 🎀

bkr job-clone [options]
  [--wait] [--dry-run] [--xml] [--pretty-xml] <taskspec>...

🌸 DESCRIPTION 🌸

Okay so bestie, you 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. Slay. 💖

The <taskspec> arguments follow the same format as in other bkr subcommands (for example, J:1234). See Specifying tasks in bkr(1).

🚨 No cap: only jobs and recipe sets may be cloned.

✨ OPTIONS ✨

  • --wait — when this option is given, the command will not terminate until the clone job has finished running. main character patience energy 🫶
  • --xml — print the job XML before submitting it. show us the XML, iconique 🔥
  • --pretty-xml — print the job XML in a easily readable format before submitting it. pretty XML supremacy 🎀
  • --dry-run — run through the job-clone process without actually submitting the cloned job. practice run, no commitment 💅
  • --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. delegation vibes, iykyk 🌈

Common bkr options are described in the Options section of bkr(1).

💀 EXIT STATUS 💀

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. Not me getting a 1… 😭

🦋 EXAMPLES 🦋

Clone job 1234 and wait for it to finish:

bkr job-clone --wait J:1234

👑 SEE ALSO 👑

🍓 AUTHOR 🍓

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

2013-2025 Red Hat, Inc.

💖 That’s the whole vibe from Beaker 29.2, dated May 26, 2025 — go off and clone some jobs, bestie! 🫶

📦 where this page comes from