From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Cleber Rosa" <crosa@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Erik Skultety" <eskultet@redhat.com>,
"Stefan Hajnoczi" <stefanha@gmail.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Andrea Bolognani" <abologna@redhat.com>,
"Willian Rampazzo" <wrampazz@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>
Subject: Re: [PATCH v5 4/4] Jobs based on custom runners: add job definitions for QEMU's machines
Date: Wed, 24 Feb 2021 13:00:54 +0100 [thread overview]
Message-ID: <247471f5-1b65-b93c-8c23-18857653e3b8@redhat.com> (raw)
In-Reply-To: <20210223182539.GH987581@amachine.somewhere>
On 2/23/21 7:25 PM, Cleber Rosa wrote:
> On Tue, Feb 23, 2021 at 03:56:19PM +0000, Daniel P. Berrangé wrote:
>>
>> Urgh, well that's a big problem. We certainly don't want *anything* being
>> placed on the custom runners without explicit opt-in, otherwise jobs run
>> in the main repo have a different environment from when users run on their
>> personal forks.
>>
>> IOW, we need anti-affinity against our custom runners really.
>>
>
> I'm assuming Phil missed that documentation, because that's a
> non-issue, really.
>
> Just unchecking the "Run untagged jobs" check box on the runner
> configuration makes sure that the custom runners won't pickup any jobs
> not *specifically* tagged for them.
Can we explicit this when registering the runner instead of having to
access the WebUI?
$ gitlab-runner register --help
--run-untagged
Register to run untagged builds; defaults to 'true'
when 'tag-list' is empty [$REGISTER_RUN_UNTAGGED]
next prev parent reply other threads:[~2021-02-24 12:02 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 21:58 [PATCH v5 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI) Cleber Rosa
2021-02-19 21:58 ` [PATCH v5 1/4] Jobs based on custom runners: documentation and configuration placeholder Cleber Rosa
2021-02-23 11:18 ` Alex Bennée
2021-02-23 11:25 ` Thomas Huth
2021-02-23 16:37 ` Philippe Mathieu-Daudé
2021-02-23 16:47 ` Cleber Rosa
2021-02-23 17:24 ` Philippe Mathieu-Daudé
2021-02-23 17:34 ` Philippe Mathieu-Daudé
2021-02-23 18:09 ` Cleber Rosa
2021-02-24 11:57 ` Philippe Mathieu-Daudé
2021-02-24 15:47 ` Cleber Rosa
2021-02-23 17:45 ` Daniel P. Berrangé
2021-02-23 21:34 ` Wainer dos Santos Moschetta
2021-02-19 21:58 ` [PATCH v5 2/4] Jobs based on custom runners: build environment docs and playbook Cleber Rosa
2021-02-22 19:36 ` Wainer dos Santos Moschetta
2021-02-23 14:01 ` Alex Bennée
2021-02-23 14:51 ` Erik Skultety
2021-02-23 15:17 ` Alex Bennée
2021-02-23 17:23 ` Cleber Rosa
2021-02-23 18:18 ` Alex Bennée
2021-02-23 17:13 ` Cleber Rosa
2021-02-23 15:01 ` Alex Bennée
2021-02-23 17:44 ` Cleber Rosa
2021-02-23 18:23 ` Alex Bennée
2021-02-23 19:47 ` Cleber Rosa
2021-02-23 17:08 ` Cleber Rosa
2021-02-23 18:16 ` Alex Bennée
2021-02-19 21:58 ` [PATCH v5 3/4] Jobs based on custom runners: docs and gitlab-runner setup playbook Cleber Rosa
2021-02-22 6:36 ` Erik Skultety
2021-02-22 20:35 ` Wainer dos Santos Moschetta
2021-02-23 13:52 ` Philippe Mathieu-Daudé
2021-02-23 13:55 ` Philippe Mathieu-Daudé
2021-02-23 14:14 ` Philippe Mathieu-Daudé
2021-02-23 15:15 ` Alex Bennée
2021-02-19 21:58 ` [PATCH v5 4/4] Jobs based on custom runners: add job definitions for QEMU's machines Cleber Rosa
2021-02-23 15:17 ` Philippe Mathieu-Daudé
2021-02-23 15:56 ` Daniel P. Berrangé
2021-02-23 16:41 ` Philippe Mathieu-Daudé
2021-02-23 18:25 ` Cleber Rosa
2021-02-24 12:00 ` Philippe Mathieu-Daudé [this message]
2021-02-24 15:54 ` Cleber Rosa
2021-02-23 18:21 ` Cleber Rosa
2021-02-23 15:27 ` Philippe Mathieu-Daudé
2021-02-23 15:35 ` Philippe Mathieu-Daudé
2021-02-23 15:45 ` Daniel P. Berrangé
2021-03-05 10:14 ` [PATCH v5 0/4] GitLab Custom Runners and Jobs (was: QEMU Gating CI) Philippe Mathieu-Daudé
2021-03-05 10:27 ` Philippe Mathieu-Daudé
2021-05-21 10:29 ` 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=247471f5-1b65-b93c-8c23-18857653e3b8@redhat.com \
--to=philmd@redhat.com \
--cc=abologna@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=eskultet@redhat.com \
--cc=fam@euphon.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wrampazz@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).