openqa-clone-job

NAME

openqa-clone-job - creates a new job based on an existing job

SYNOPSIS

Clones a job from the local or a remote openQA instance. Downloads all assets associated with the job (unless --skip-download is specified). Optionally settings can be modified.

openqa-clone-job [OPTIONS] JOBREF [KEY=[VALUE] ...]
# clones job 42 (and any existing parents) from "openqa.opensuse.org" to the local openQA instance
# note: If job 42 is a parallel parent (e.g. a "server" job), its parallel children (e.g. "client"
# jobs) will be cloned as well.
openqa-clone-job https://openqa.opensuse.org/t42
openqa-clone-job --from https://openqa.opensuse.org/tests/42
openqa-clone-job --from https://openqa.opensuse.org 42
# clones job 42 (and any existing parents) from "openqa.opensuse.org" to the openQA instance "openqa.example.com"
openqa-clone-job --skip-download --from https://openqa.opensuse.org --host openqa.example.com 42
# clones job 42 (and any existing parents) within the local openQA instance modifying some job settings
openqa-clone-job --within-instance 42 MAKETESTSNAPSHOTS=1 TEST+=:PR-123 FOOBAR=
# clones job 42 including all of its direct children but excluding its chained parents
openqa-clone-job --skip-chained-deps --clone-children https://openqa.opensuse.org/tests/42

DESCRIPTION

Call with either a full URL pointing to a test job to clone from or one of both parameters "--from" or "--within-instance". The job ID can be specified as part of the URL or as its own parameter.

API key and secret are read from "client.conf" if not specified via CLI arguments. The config file is checked for under "$OPENQA_CONFIG", "˜/.config/openqa" and "/etc/openqa" in this order. It must look like this:

[openqa.opensuse.org]
key = 45ABCEB4562ACB04
secret = 4BA0003086C4CB95
[another.host]
key = D7345DA7B9D86B3B
secret = A98CDBA9C8DB87BD

Any parent jobs (chained or parallel) are also cloned unless "--skip-deps" or "--skip-chained-deps" is specified. If "--skip-chained-deps" is specified published assets generated by parent jobs are downloaded to be directly used instead of generated. Keep in mind that by default any additionally specified job settings are NOT added to the also cloned parent jobs.

Note that the child job is the one which has the " START_AFTER_TEST" or " PARALLEL_WITH" setting and the parent job is the one mentioned by that setting.

Cloning directly chained dependencies (" START_DIRECTLY_AFTER_TEST" ) is NOT supported.

OPTIONS

--host HOST

Specifies the hostname of the target openQA instance (defaults to localhost).

Assets are still always downloaded to the local machine. When specifying a remote host make sure the assets are already there and use "--skip-download".

--from HOST

Specifies the hostname of the openQA instance to clone the job from (deduced from JOBREF if it is a URL ).

--dir DIR

Specifies the directory to store test assets (defaults to $OPENQA_SHAREDIR/factory).

--skip-deps

Do NOT clone parent jobs (which is done by default).

--skip-chained-deps

Do NOT clone chained parent jobs (jobs specified via " START_AFTER_TEST" ).

This makes the job use the downloaded HDD image instead of running the generator job again which is of course only possible if --host is the local machine.

--skip-download

Do NOT download assets. You need to ensure all required assets are provided yourself.

--ignore-missing-assets

Cloning a job will not fail if an asset is missing.

--clone-children

Clone all direct child jobs as well. By default, only parallel child jobs are cloned.

--max-depth

Specifies the max depth for cloning children. By default, only direct children are cloned. Use 0 to denote infinity.

--within-instance HOST

A shortcut for "--skip-download --from HOST --host HOST" to clone a job within a local or remote instance.

--show-progress

Displays a progress bar when downloading assets.

--parental-inheritance

Provides parental job with settings specified via command line (they go to child job by default).

--export-command

Prints an ‘openqa-cli‘ command to create the jobs instead of creating them directly. This is useful to customize the API call or to review it before submitting.

--apikey <value>

Specifies the public key needed for API authentication.

--apisecret <value>

Specifies the secret key needed for API authentication.

--verbose, -v

Increases verbosity.

--help, -h

Prints help.