summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuca Boccassi <luca.boccassi@microsoft.com>2021-09-15 13:49:04 +0100
committerFrantisek Sumsal <frantisek@sumsal.cz>2021-09-15 14:58:38 +0200
commite236711fd7815eb93690d166959660c7d82666bf (patch)
tree4369500f759204ce473507f9579c29562e12c24a
parent65bf08dd4afcb09dfb74fd44c9788e1d689ad9d7 (diff)
downloadsystemd-e236711fd7815eb93690d166959660c7d82666bf.tar.gz
test: document autopkgtest CI infrastructure
-rw-r--r--test/README.testsuite15
1 files changed, 15 insertions, 0 deletions
diff --git a/test/README.testsuite b/test/README.testsuite
index da989c1e0d..2f10c7370c 100644
--- a/test/README.testsuite
+++ b/test/README.testsuite
@@ -148,3 +148,18 @@ The cloud-side infrastructure, that is hooked into the Github interface, is
located at:
https://git.launchpad.net/autopkgtest-cloud/
+
+In case of infrastructure issues with this CI, things might go wrong in two
+places:
+
+- starting a job: this is done via a Github webhook, so check if the HTTP POST
+ are failing on https://github.com/systemd/systemd/settings/hooks
+- running a job: all currently running jobs are listed at
+ https://autopkgtest.ubuntu.com/running#pkg-systemd-upstream in case the PR
+ does not show the status for some reason
+- reporting the job result: this is done on Canonical's cloud infrastructure,
+ if jobs are started and running but no status is visible on the PR, then it is
+ likely that reporting back is not working
+
+For infrastructure help, reaching out to Canonical via the #ubuntu-devel channel
+on libera.chat is an effective way to receive support in general.