pkgdev tatt - package testing tool

Synopsis

pkgdev tatt [–config CONFIG_FILE] [–domain DOMAIN] [-h] [–debug] [–color BOOLEAN] [–api-key TOKEN] [-j NAME] [-b BUG] [-t] [-u NUMBER] [–ignore-prefixes IGNORE_PREFIXES] [–use-default | –use-random | –use-expand-random] [-p TARGET [TARGET …]] [-s | -k] [–template-file TEMPLATE_FILE] [–logs-dir LOGS_DIR] [–emerge-opts EMERGE_OPTS] [–extra-env-file ENV_FILE]

Options

--api-key TOKEN

The Bugzilla API key to use for authentication. WARNING: using this option will expose your API key to other users of the same system. Consider instead saving your API key in a file named ~/.bugzrc in an INI format like so:

[default]
key = <your API key>

Another supported option is to save your API key in a file named ~/.bugz_token.

-j NAME, --job-name NAME

The job name to use for the job script and report. The name can use the variables {PN} (package name) and {BUGNO} (bug number) to created variable names.

-b BUG, --bug BUG

Single bug to take package list from

Config Options

--config CONFIG_FILE

Load custom pkgdev scan settings from a given file.

Note that custom user settings override all other system and repo-level settings.

It’s also possible to disable all types of settings loading by specifying an argument of ‘false’ or ‘no’.

--domain DOMAIN

custom pkgcore domain to use for this operation

Base Options

-h, --help

Show this help message and exit. To get more information see the related man page.

--debug

Enable debug checks and show verbose debug output.

--color BOOLEAN

Toggle colored output support. This can be used to forcibly enable color support when piping output or other situations where stdout is not a tty.

Use Flags Options

-t, --test

Include a test run for packages which define src_test phase (in the ebuild or inherited from eclass).

-u NUMBER, --use-combos NUMBER

Maximal number USE combinations to be tested

--ignore-prefixes IGNORE_PREFIXES

Comma separated USE flags prefixes that won’t be randomized. This is useful for USE flags such as python_targets_. Note that this doesn’t affect preference, but because of specific REQUIRED_USE will still be changed from defaults.

--use-default

Prefer to use default use flags configuration

--use-random

Turn on random use flags, with default USE_EXPAND

--use-expand-random

Turn on random use flags, including USE_EXPAND

Manual Packages Options

-p TARGET [TARGET ...], --packages TARGET [TARGET ...]

extended atom matching of packages

-s, --stablereq

Test packages for stable keywording requests

-k, --keywording

Test packages for keywording requests

Template Options

--template-file TEMPLATE_FILE

Template file to use for the job script. The template file is a Jinja template file, which can use the following variables:

jobs

A list of jobs to be run. Each job is a tuple consisting of USE flags values, is a testing job, and the atom to build.

report_file

The path to the report file.

emerge_opts

Options to be passed to emerge invocations. Taken from --emerge-opts.

extra_env_files

A list of extra /etc/portage/env/ file names, to be added to package.env entry when testing the package. Taken from --extra-env-file.

log_dir

irectory to save build logs for failing tasks. Taken from --logs-dir.

cleanup_files

A list of files to be removed after the job script is done.

--logs-dir LOGS_DIR

Directory to save build logs for failing tasks

--emerge-opts EMERGE_OPTS

Space separated single argument, consisting og options to be passed to emerge invocations.

--extra-env-file ENV_FILE

Comma separated filenames under /etc/portage/env/, which will all be included in the package.env entry when testing the package.