summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPhilip Withnall <philip@tecnocode.co.uk>2023-08-14 10:20:43 +0100
committerPhilip Withnall <philip@tecnocode.co.uk>2023-08-14 10:20:43 +0100
commite234a4496ef6e2a7a2896fc6b9ddf93044a420ab (patch)
treef71008b9e79efb0ba081c2fee565a35bb45f88de
parent11d051f36ec6cef6ccf27ebccb0ff2ee11aa88c4 (diff)
downloadglib-e234a4496ef6e2a7a2896fc6b9ddf93044a420ab.tar.gz
ci: Only run pages CI job on scheduled job runs
Since commit b9b7816e5a16328ff32fa1cf3b87f9d69457a07c, the `pages` job will still try to be run on `main` after an MR is merged, but will fail because it depends on `coverage` and `style-check-advisory`, which are no longer run on `main` after a merge. See https://gitlab.gnome.org/GNOME/glib/-/pipelines/560680 for an example failure. Instead, make the `pages` job only run at the end of a scheduled CI run. Its dependent jobs will have run then. This means that the ‘canonical’ code coverage report at https://gnome.pages.gitlab.gnome.org/glib/coverage/ will be updated once a week, rather than after every merge into `main`. Signed-off-by: Philip Withnall <philip@tecnocode.co.uk>
-rw-r--r--.gitlab-ci.yml1
1 files changed, 1 insertions, 0 deletions
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index d60262ce8..07ea8957c 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -659,6 +659,7 @@ scan-build:
- "cov-int/build-log.txt"
pages:
+ extends: .only-schedules
stage: deploy
only:
- main