Piuparts task
A specific task to represent a binary package check using the
piuparts
utility.
The task_data
associated to this task can contain the following keys:
input
(required): a dictionary describing the input databinary_artifacts
(Multiple lookup, required): a list ofdebian:binary-packages
ordebian: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 tounshare
). Ifauto
, the task uses the default. Supported backends:incus-lxc
,incus-vm
, andunshare
.environment
(Single lookup with default categorydebian:environments
, required): artifact of categorydebian:system-tarball
that will be used to run piuparts itself.base_tgz
(Single lookup with default categorydebian:environments
, required): artifact of categorydebian:system-tarball
that will be used to run piuparts tests, throughpiuparts --base-tgz
. If the artifact’s data haswith_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 theextra_repositories
option in the Task PackageBuild.
The piuparts
output will be provided as a new artifact.