Run unit and system tarball tests on schedules

To prevent problems with unit and system tarball tests being revealed
during release process, run these tests on schedules.

(cherry picked from commit 439fe9bc3cdb3e2da14c602e5caaed4e60e86855)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 9166bc617f997a6c6bc326a119e47567af88e7ee..6d36ae0ffb85360371214147a324892b63f797e5 100644 (file)
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -739,6 +739,7 @@ gcc:tarball:
     - job: tarball-create
       artifacts: true
   only:
+    - schedules
     - tags
 
 system:gcc:tarball:
@@ -751,6 +752,7 @@ system:gcc:tarball:
     - job: gcc:tarball
       artifacts: true
   only:
+    - schedules
     - tags
 
 unit:gcc:tarball:
@@ -762,6 +764,7 @@ unit:gcc:tarball:
     - job: gcc:tarball
       artifacts: true
   only:
+    - schedules
     - tags
 
 # Jobs for regular GCC builds on Debian Sid (i386)