gitlab.fd.o financial situation and impact on services

Michel Dänzer michel at
Mon Apr 6 17:04:47 UTC 2020

On 2020-04-06 6:34 p.m., Rob Clark wrote:
> The ideal thing would be to be able to click any jobs that we want to
> run, say "arm64_a630_gles31", and for gitlab to realize that it needs
> to automatically trigger dependencies of that job (meson-arm64, and
> arm_build+arm_test).  But not sure if that is a thing gitlab can do.

Not that I know of. The dependency handling is still pretty rudimentary
in general.

> Triggering just the first container jobs and having everything from
> there run automatically would be ok if the current rules to filter out
> unneeded jobs still apply, ie. a panfrost change isn't triggering
> freedreno CI jobs and visa versa.  But tbh I don't understand enough
> of what that MR is doing to understand if that is what it does.  (It
> was suggested on IRC that this is probably what it does.)

It is. Filtered jobs don't exist at all in the pipeline, so they can't
be triggered by any means. :)

Earthling Michel Dänzer               |     
Libre software enthusiast             |             Mesa and X developer

More information about the wayland-devel mailing list