Skip to content

Follow ups for dummy tier jobs

Context

Follow-up MR of !155294 (merged).

What does this MR do and why?

I did not exclude docs-only pipelines from being counted as pipelinetier-1 in Snowflake, because:

  • !155294 (merged) is a workaround until the pipeline name is available in Snowflake (and the pipeline name wouldn't have a tier for docs-only pipelines)
  • In the last 30 days, we had 1423 docs pipelines, but probably only a subset of those are docs-only (which are the pipelines that wouldn't need tier information)
  • Even if the tier-1 number is a bit overvalued, I would argue the first tier it's not the the one we should optimize for the most now (as we already did this in the last quarter), so I'm okay having this imprecision for a month or so. Open to feedback/wild criticism as well on this 😆

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.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

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

Merge request reports