From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: "Michel Dänzer" <michel@daenzer.net>,
"Erik Faye-Lund" <erik.faye-lund@collabora.com>,
"Daniel Stone" <daniel@fooishbar.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
"X.Org development" <xorg-devel@lists.x.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
wayland <wayland-devel@lists.freedesktop.org>,
"X.Org Foundation Board" <board@foundation.x.org>,
Xorg Members List <members@x.org>,
amd-gfx list <amd-gfx@lists.freedesktop.org>,
Mesa Dev <mesa-dev@lists.freedesktop.org>,
gstreamer-devel@lists.freedesktop.org
Subject: Re: [Mesa-dev] [Intel-gfx] gitlab.fd.o financial situation and impact on services
Date: Fri, 28 Feb 2020 15:08:17 +0200 [thread overview]
Message-ID: <800a567b-c00d-dcc3-0ea2-7ea61a0cd4b6@intel.com> (raw)
In-Reply-To: <8915813c-ec74-6b1c-6021-bb67219174a0@daenzer.net>
On 28/02/2020 13:46, Michel Dänzer wrote:
> On 2020-02-28 12:02 p.m., Erik Faye-Lund wrote:
>> On Fri, 2020-02-28 at 10:43 +0000, Daniel Stone wrote:
>>> On Fri, 28 Feb 2020 at 10:06, Erik Faye-Lund
>>> <erik.faye-lund@collabora.com> wrote:
>>>> On Fri, 2020-02-28 at 11:40 +0200, Lionel Landwerlin wrote:
>>>>> Yeah, changes on vulkan drivers or backend compilers should be
>>>>> fairly
>>>>> sandboxed.
>>>>>
>>>>> We also have tools that only work for intel stuff, that should
>>>>> never
>>>>> trigger anything on other people's HW.
>>>>>
>>>>> Could something be worked out using the tags?
>>>> I think so! We have the pre-defined environment variable
>>>> CI_MERGE_REQUEST_LABELS, and we can do variable conditions:
>>>>
>>>> https://docs.gitlab.com/ee/ci/yaml/#onlyvariablesexceptvariables
>>>>
>>>> That sounds like a pretty neat middle-ground to me. I just hope
>>>> that
>>>> new pipelines are triggered if new labels are added, because not
>>>> everyone is allowed to set labels, and sometimes people forget...
>>> There's also this which is somewhat more robust:
>>> https://gitlab.freedesktop.org/mesa/mesa/merge_requests/2569
>> I'm not sure it's more robust, but yeah that a useful tool too.
>>
>> The reason I'm skeptical about the robustness is that we'll miss
>> testing if this misses a path.
> Surely missing a path will be less likely / often to happen compared to
> an MR missing a label. (Users which aren't members of the project can't
> even set labels for an MR)
>
>
Sounds like a good alternative to tags.
-Lionel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-02-28 13:08 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 21:27 gitlab.fd.o financial situation and impact on services Daniel Vetter
2020-02-27 23:45 ` Matt Turner
2020-02-28 7:59 ` Daniel Stone
2020-02-28 10:09 ` Jan Engelhardt
2020-02-28 11:11 ` Daniel Stone
2020-02-28 21:20 ` Matt Turner
2020-02-28 0:21 ` Luc Verhaegen
2020-02-28 0:33 ` Carsten Haitzler
2020-02-28 1:00 ` [Mesa-dev] " Tom Stellard
2020-02-28 1:08 ` Tom Stellard
2020-02-28 3:37 ` [Intel-gfx] " Dave Airlie
2020-02-28 7:44 ` Daniel Vetter
2020-02-28 8:17 ` Daniel Stone
2020-02-28 8:48 ` Dave Airlie
2020-02-28 9:26 ` Daniel Stone
2020-02-28 19:34 ` [Mesa-dev] " Eric Anholt
2020-02-28 20:30 ` Dave Airlie
2020-02-28 21:22 ` Daniel Vetter
2020-02-28 21:37 ` Nuritzi Sanchez
2020-04-04 13:55 ` Andreas Bergmeier
2020-04-05 14:07 ` Nicolas Dufresne
2020-02-28 9:28 ` Erik Faye-Lund
2020-02-28 9:40 ` Lionel Landwerlin
2020-02-28 10:06 ` Erik Faye-Lund
2020-02-28 10:43 ` Daniel Stone
2020-02-28 11:02 ` Erik Faye-Lund
2020-02-28 11:46 ` Michel Dänzer
2020-02-28 13:08 ` Lionel Landwerlin [this message]
2020-02-29 18:14 ` Timur Kristóf
2020-02-29 19:46 ` Nicolas Dufresne
2020-02-29 20:28 ` Timur Kristóf
2020-02-29 21:54 ` Jason Ekstrand
2020-02-29 22:20 ` Nicolas Dufresne
2020-03-01 5:46 ` Marek Olšák
2020-04-03 14:12 ` Michel Dänzer
2020-04-04 15:11 ` Rob Clark
2020-04-04 17:47 ` Nicolas Dufresne
2020-04-04 18:16 ` Rob Clark
2020-04-04 18:41 ` Rob Clark
2020-04-04 18:47 ` Rob Clark
2020-04-04 23:39 ` Peter Hutterer
2020-04-04 23:32 ` Peter Hutterer
2020-04-06 15:42 ` Adam Jackson
2020-04-06 16:34 ` Rob Clark
2020-04-06 17:04 ` Michel Dänzer
2020-04-06 18:00 ` Rob Clark
2020-03-01 14:14 ` [Mesa-dev] [Intel-gfx] " Michel Dänzer
2020-03-01 14:27 ` Nicolas Dufresne
2020-03-01 19:51 ` Jacob Lifshay
2020-03-01 20:18 ` [Intel-gfx] [Mesa-dev] " Jason Ekstrand
2020-03-01 20:30 ` Bridgman, John
2020-03-01 20:49 ` Nicolas Dufresne
2020-03-02 4:53 ` Jason Ekstrand
2020-02-28 9:47 ` [Mesa-dev] [Intel-gfx] " Daniel Vetter
2020-02-28 10:10 ` Erik Faye-Lund
2020-02-28 10:27 ` Lucas Stach
2020-02-28 11:43 ` Michel Dänzer
2020-02-28 17:00 ` [Intel-gfx] [Mesa-dev] " Rob Clark
2020-02-29 15:58 ` Jason Ekstrand
2020-02-28 18:03 ` [Intel-gfx] " Kristian Høgsberg
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=800a567b-c00d-dcc3-0ea2-7ea61a0cd4b6@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=board@foundation.x.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@fooishbar.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=erik.faye-lund@collabora.com \
--cc=gstreamer-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=members@x.org \
--cc=mesa-dev@lists.freedesktop.org \
--cc=michel@daenzer.net \
--cc=wayland-devel@lists.freedesktop.org \
--cc=xorg-devel@lists.x.org \
/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).