Skip to content

Add video discussion on average time to first failure for Quality PI

James Komara requested to merge ja-me-sk-master-patch-43447 into master

Why is this change being made?

Out of the Quality Key review, there was an extended discussion around the question if we are measuring time to failure.

This update adds a link to the video at the starting point of that discussion.

To add some of the text of the discussion, the outcome was the desire to show average time to first failure to optimize scheduling the tests and improve the feedback cycle to the developer.

We can separately explain the rationale for the related test. The goal is to schedule the last failed pipelines first, which would be a big help to developers and reduce the time.

Closes https://gitlab.com/gitlab-com/ceo-shadow/tasks/-/issues/195

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)

Merge request reports