From: Luca Boccassi Date: Thu, 22 Feb 2024 14:19:08 +0000 (+0000) Subject: test/README: document how to add a new empty release to the PPA to migrate the CI... X-Git-Tag: v256-rc1~709^2~2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=132f78542979c412b233dd03496d277e4fffc8fa;p=thirdparty%2Fsystemd.git test/README: document how to add a new empty release to the PPA to migrate the CI to a new version --- diff --git a/test/README.testsuite b/test/README.testsuite index 5c93457c349..48c871f5e81 100644 --- a/test/README.testsuite +++ b/test/README.testsuite @@ -170,6 +170,17 @@ places: if jobs are started and running but no status is visible on the PR, then it is likely that reporting back is not working +The CI job needs a PPA in order to be accepted, and the upstream-systemd-ci/systemd-ci +PPA is used. Note that this is necessary even when there are no packages to backport, +but by default a PPA won't have a repository for a release if there are no packages +built for it. To work around this problem, when a new empty release is needed the +mark-suite-dirty tool from the https://git.launchpad.net/ubuntu-archive-tools can +be used to force the PPA to publish an empty repository, for example: + + $ ./mark-suite-dirty -A ppa:upstream-systemd-ci/ubuntu/systemd-ci -s noble + +will create an empty 'noble' repository that can be used for 'noble' CI jobs. + For infrastructure help, reaching out to Canonical via the #ubuntu-quality channel on libera.chat is an effective way to receive support in general.