Piuparts

Piuparts task

A specific task to represent a binary package check using the piuparts utility.

To use piuparts under one of the container-based executors requires piuparts >= 1.3. This is available in Debian since trixie, so we’d recommend using trixie or later as the environment for piuparts tasks. Select the appropriate base_tgz for the distribution release actually under test.

The task_data associated to this task can contain the following keys:

• input (required): a dictionary describing the input data

  • binary_artifacts (Multiple lookup, required): a list of debian:binary-package, debian:binary-packages, or debian:upload artifacts representing the binary packages to be tested. Multiple artifacts can be provided so as to support e.g. testing binary packages from split indep/arch builds.

• backend (optional, defaults to unshare). If auto, the task uses the default. Supported backends: incus-lxc, incus-vm, and unshare.

• environment (Single lookup with default category debian:environments, required): debian:system-tarball artifact that will be used to run piuparts itself.

• base_tgz (Single lookup with default category debian:environments, required): debian:system-tarball artifact that will be used to run piuparts tests, through piuparts --base-tgz. If the artifact’s data has with_dev: True, the task will remove the files /dev/* before using it.

• host_architecture (required): the architecture that we want to test on.

• extra_repositories (optional): a list of extra repositories to enable. Each repository is described by the same dictionary as the extra_repositories option in the PackageBuild interface.

The task computes dynamic metadata as:

• subject: space-separated list of source package names from input.binary_artifact

• parameter_summary: same as subject with the version (if one package)

• runtime_context: codename:host_architecture where codename is from base_tgz

• configuration_context: codename from base_tgz

The piuparts output will be provided as a new artifact.