Skip to content

Label known issues for use in doctor

Without knowing much at all about how it works - I was really curious on how much manual work we could minimize by simply labeling specific issues. This is more of a pie in the sky can we do it? type of brainstorming but I think it's possible and it doesn't seem like it was on the roadmap.

For example, let's say that you are the first person to come across a weird sidekiq issue in 17.2. So you create a RFH issue and then eventually a bug report that will be fixed in the next 1-3 releases. Rather than having to create a gitlab-doctor issue or MR, you could:

  1. Label your bug report with gl-doctor::known-issues-17.2
  2. Run a pipeline in the gitlab-doctor repo that would collect all newly labelled issues.
  3. Automagically generate the required .yml files for basic alerts for these known issues.

The idea would be that if you ran a check on GitLab 17.2 and wanted to check for sidekiq issues it would at least alert you of known issues targeted at that version and component regardless if a "check" needed to be done.