diff options
| author | Luca Boccassi <bluca@debian.org> | 2024-02-22 15:19:08 +0100 |
|---|---|---|
| committer | Luca Boccassi <bluca@debian.org> | 2024-02-28 02:08:57 +0100 |
| commit | 132f78542979c412b233dd03496d277e4fffc8fa (patch) | |
| tree | e34420d4e3890fc1f23f4c122b603940d4f10b1d /test/README.testsuite | |
| parent | test/README: update ubuntu IRC channel for CI help (diff) | |
| download | systemd-132f78542979c412b233dd03496d277e4fffc8fa.tar.xz systemd-132f78542979c412b233dd03496d277e4fffc8fa.zip | |
test/README: document how to add a new empty release to the PPA to migrate the CI to a new version
Diffstat (limited to '')
| -rw-r--r-- | test/README.testsuite | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/test/README.testsuite b/test/README.testsuite index 5c93457c34..48c871f5e8 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. |