Skip to content

Prevent spam creation of failure issues

Harsha Muralidhar requested to merge hmuralidhar-stop-spam-failure-issues into master

What does this MR do and why?

Relates to: gitlab-org/quality/quality-engineering/team-tasks#730 (closed)

During pipeline triage it has been observed that there can be many failure issues created due to an incident/common failure etc. This MR tries to address that by checking if:

  1. There are similar stack trace issues
  2. Those issues belong to the same pipeline env as the current run, for eg., staging
  3. Checks for issues created in last 2 hours (may be we can make this configurable)
  4. Checks for failure: new label

If the number of such issues has exceeded the threshold, then it won't create a new failure issue.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

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

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports