Pipeline Execution N+1 Aged S2 Bug Triage

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue
• Close this issue

Summary

As part of grouppipeline execution's goal to reduce the median age of S2 bugs we will create a bug triage issue each milestone until we hit our goal of Median Age of Less than 1 year.

Tasks to complete this issue

1. Review the list of aged S2 bugs below
2. Pick and assign a bug to yourself
3. Try to replicate the bug locally
   • If you cannot replicate the bug tag the bug author asking for more information, apply the label Cannot reproduce and close the issue.
   • If the bug does not meet the criteria for a Severity 2 bug (there is an easy workaround) change Severity and Priority labels accordingly. Tag PM/EM if you are not sure.
   • If you can replicate the bug update the issue description with steps to reproduce and anything else that would be helpful to implement a fix.
   • If you can fix the bug as fast as replicating it feel free to do so, please consult EM/PM about moving other issues out of the milestone to accommodate the work.
4. Pat yourself on the back for helping improve the user experience and improving a Quality KPI !!

Bugs to investigate

• Runner does not retry CI/CD jobs that should be... (#118482 - closed) there's a comment about a new CI_variable that might solve this. A docs update could come out of it?
• Scheduled pipelines appear in the post-merge MR... (#225653)
• Generate a new pipeline when merge request targ... (#233830 - closed) - It looks like this needs validated and some new steps to reproduce.
• $CI_JOB_TOKEN starts with a `-` causes job to fail (#244974 - closed) - I think we could document the workarounds, maybe add a note to the conan docs page about this known limitation and then de-prioritize this since it hasn't had any activity in a year.
• Pipeline change webhook never contains merge re... (#241057 - closed)