Skip to content

Geo: Disable pipeline ref created events by default

What does this MR do and why?

We validated that "pipeline ref created" events are not needed here. These events cause a lot of unnecessary Gitaly noise.

So, this MR disables "pipeline ref created" Geo events, by default.

In the next milestone, I will remove the FF.

By taking this staged approach, the first Geo customers to upgrade to 16.9 can re-enable this event as a workaround if removal causes a problem. And then we could re-enable the FF in 16.10 and backport to 16.9 without requiring a backport exception.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Set up Geo with Unified URL
  2. Set up a Runner and register it with the Unified URL https://docs.gitlab.com/ee/administration/geo/secondary_proxy/runners.html
  3. Ensure that the Runner requests are routed to the secondary site (e.g. point the Unified URL only at the secondary site)
  4. See if new pipelines work
Edited by Michael Kozono

Merge request reports