qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>
Subject: [PULL 17/18] gitlab: make the schedule rules a bit more general
Date: Mon, 17 Nov 2025 15:49:46 +0000	[thread overview]
Message-ID: <20251117154948.4122164-18-alex.bennee@linaro.org> (raw)
In-Reply-To: <20251117154948.4122164-1-alex.bennee@linaro.org>

By default no jobs should run under the schedule and then we can be
more explicit for the ones that we need to. Otherwise I trigger all my
custom runners every time I do a scheduled run.

Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Message-ID: <20251117115523.3993105-18-alex.bennee@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>

diff --git a/.gitlab-ci.d/base.yml b/.gitlab-ci.d/base.yml
index 60a24a9d14d..921c5620008 100644
--- a/.gitlab-ci.d/base.yml
+++ b/.gitlab-ci.d/base.yml
@@ -45,8 +45,8 @@ variables:
     - if: '$CI_PROJECT_NAMESPACE == $QEMU_CI_UPSTREAM && $CI_COMMIT_TAG'
       when: never
 
-    # Scheduled runs on mainline don't get pipelines except for the special Coverity job
-    - if: '$CI_PROJECT_NAMESPACE == $QEMU_CI_UPSTREAM && $CI_PIPELINE_SOURCE == "schedule"'
+    # Scheduled jobs should explicitly enable the run in their job rules
+    - if: '$CI_PIPELINE_SOURCE == "schedule"'
       when: never
 
     # Cirrus jobs can't run unless the creds / target repo are set
-- 
2.47.3



  parent reply	other threads:[~2025-11-17 15:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 15:49 [PULL 00/18] testing updates for 10.2 Alex Bennée
2025-11-17 15:49 ` [PULL 01/18] tests/docker: drop --link from COPYs in emsdk docker Alex Bennée
2025-11-17 15:49 ` [PULL 02/18] libvirt-ci: bump libvirt-ci to latest version Alex Bennée
2025-11-17 15:49 ` [PULL 03/18] tests/lcitool: update ENV stazas outputted by refresh Alex Bennée
2025-11-17 15:49 ` [PULL 04/18] tests/docker: add coreutils to the package list Alex Bennée
2025-11-17 15:49 ` [PULL 05/18] docs/about/emulation: update assets for uftrace plugin documentation Alex Bennée
2025-11-17 15:49 ` [PULL 06/18] tests: move test_xen assets to share.linaro.org Alex Bennée
2025-11-17 15:49 ` [PULL 07/18] tests: move test_virt " Alex Bennée
2025-11-17 15:49 ` [PULL 08/18] tests: move test_netdev_ethtool " Alex Bennée
2025-11-17 15:49 ` [PULL 09/18] tests: move test_kvm_xen " Alex Bennée
2025-11-17 15:49 ` [PULL 10/18] tests: move test_kvm " Alex Bennée
2025-11-17 15:49 ` [PULL 11/18] tests: move test_virt_gpu " Alex Bennée
2025-11-17 15:49 ` [PULL 12/18] gitlab: add initial ppc64le custom-runner test Alex Bennée
2025-11-17 15:49 ` [PULL 13/18] gitlab: use template for ubuntu-24.04-s390x jobs Alex Bennée
2025-11-17 15:49 ` [PULL 14/18] gitlab: simplify the ubuntu-24.04-aarch64 rules Alex Bennée
2025-11-17 15:49 ` [PULL 15/18] gitlab: suppress custom runners being triggered by schedule Alex Bennée
2025-11-17 15:49 ` [PULL 16/18] gitlab: make custom runners need QEMU_CI to run Alex Bennée
2025-11-17 15:49 ` Alex Bennée [this message]
2025-11-17 15:49 ` [PULL 18/18] gitlab: add a weekly container building job Alex Bennée
2025-11-17 16:49 ` [PULL 00/18] testing updates for 10.2 Alex Bennée

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251117154948.4122164-18-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).