[Mesa-dev] [Intel-gfx] gitlab.fd.o financial situation and impact on services

Daniel Stone daniel at fooishbar.org
Fri Feb 28 10:43:49 UTC 2020

On Fri, 28 Feb 2020 at 10:06, Erik Faye-Lund
<erik.faye-lund at 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:


More information about the gstreamer-devel mailing list