|author||Arnout Vandecappelle (Essensium/Mind) <firstname.lastname@example.org>||2018-10-21 11:03:03 +0100|
|committer||Peter Korsgaard <email@example.com>||2018-10-21 23:34:18 +0200|
.gitlab-ci.yml: do runtime tests only on explicit trigger
When the runtime tests were first introduced, they still ran pretty quickly. Nowadays, however, there are a lot of runtime tests, and some of them take a really long time. So running them on every push is really too much. Just like we do for the defconfigs, run them on explicit trigger only. The explicit trigger is now done every week, but it can be increased to e.g. twice or three times per week. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <firstname.lastname@example.org> Signed-off-by: Peter Korsgaard <email@example.com>
Diffstat (limited to '.gitlab-ci.yml.in')
1 files changed, 5 insertions, 0 deletions
diff --git a/.gitlab-ci.yml.in b/.gitlab-ci.yml.in
index 38e24c8d01..db526c4b5a 100644
@@ -62,6 +62,11 @@ check-package:
+ # Running the runtime tests for every push is too much, so limit to
+ # explicit triggers through the API.
+ - triggers
+ - tags
# Keep build directories so the rootfs can be an artifact of the job. The
# runner will clean up those files for us.
# Multiply every emulator timeout by 10 to avoid sporadic failures in