2019-11-11 - Triage report for "group::runner"
Hi, @DarrenEastman @erushton @dcipoletti
This is a group or stage level triage package that aims to summarize the feature proposals and bugs which have not been scheduled or triaged. For more information please refer to the handbook:
Scheduling the workload is a collaborative effort by the Product Managers and Engineering Managers for that group. Please work together to provide a best estimate on priority and milestone assignments. For each issue please:
- Determine if the issue should be closed if it is no longer relevant or a duplicate.
- If it is still relevant please assign either a best estimate versioned milestone, the %Backlog or the %Awaiting further demand milestone.
- Specifically for ~bug, if there is no priority or clarity on a versioned milestone, please add a Priority label. Priority labels have an estimate SLO attached to them and help team members and the wider community understand roughly when it will be considered to be scheduled.
- Once a milestone has been assigned please check off the box for that issue.
- Please work with your team to complete the list by the due date set.
Feature Proposal Section
For the following feature proposals. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.
feature with customer
Unscheduled-
#33737 (closed) Restrict which Docker images can be used in CI jobs Category:Runner, awaiting feedback, customer, devopsverify, feature, grouprunner, security
feature (non-customer)
Unscheduled-
#35806 Run only on none-protected jobs. Category:Continuous Integration, Category:Runner, devopsverify, feature, grouprunner -
#35693 (closed) Install and configure GitLab runners from GitLab Category:Runner, devopsverify, feature, grouprunner -
#35292 (closed) Docs feedback: Why not call "disable_cache" simply "enable_cache"? Category:Runner, devopsverify, feature, grouprunner
Bug Section
For the following bugs. Please either close or assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone and ensure that a priority label is set.
Heatmap for all bugs
Bugs for their priority and severity label are counted here. Every bug should have severity and priority labels applied. Please take a look at the bugs which fall into the columns indicating that the priority or severity labels are currently missing.
~S1 | ~S2 | ~S3 | ~S4 | |
---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 |
~P2 | 0 | 3 | 0 | 0 |
~P3 | 0 | 1 | 10 | 0 |
~P4 | 0 | 0 | 1 | 4 |
Heatmap for ~missed-SLO bugs
~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 0 |
~P2 | 0 | 1 | 0 | 0 | 0 |
~P3 | 0 | 0 | 0 | 0 | 0 |
~P4 | 0 | 0 | 0 | 0 | 0 |
~"No priority" | 0 | 0 | 0 | 0 | 1 |
This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook: