2019-10-21 - Triage report for "group::runner"
Hi, @DarrenEastman @erushton @jhampton
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.
Unscheduled feature with customer
-
#33737 (closed) Restrict which Docker images can be used in CI jobs Category:Runner, customer, devopsverify, feature, grouprunner, security
Unscheduled feature (non-customer)
-
#32581 (closed) As group owner, hide banners about Gitlab Runner minutes Category:Runner, UX, devopsverify, feature, grouprunner -
#12851 Limit notifications for CI Minutes quota limit to group owners Category:Runner, Enterprise Edition, ~"Shared Runners::Linux", devopsverify, feature, grouprunner, pipeline -
#25315 Add CI runner shared for all user personal projects Category:Runner, ~"Verify [DEPRECATED]", auto updated, devopsverify, feature, grouprunner, potential proposal -
#22382 (closed) Runner and fork configuration Category:Runner, ~"Verify [DEPRECATED]", devopsverify, feature, grouprunner -
#20942 Extending artifacts API to allow upload Category:Runner, ~"Verify [DEPRECATED]", api, ~"artifacts", devopsverify, feature, grouprunner -
#19865 Runner cleanup ability Category:Runner, Manage [DEPRECATED], ~"Verify [DEPRECATED]", admin dashboard, auto updated, devopsverify, feature, grouprunner, potential proposal -
#19682 (closed) Should we allow a runner to generate temporary personal access token in order to push in GitLab API projects ? Category:Runner, ~"Verify [DEPRECATED]", devopsverify, feature, grouprunner -
#19451 (closed) Extend specific runners to be able to pick jobs from forks Category:Runner, ~"Verify [DEPRECATED]", devopsverify, feature, grouprunner -
#18711 Artifact compression method should be configurable Category:Runner, ~"Verify [DEPRECATED]", ~"artifacts", auto updated, devopsverify, feature, grouprunner, potential proposal, settings -
#18685 Create inspectable job list view of runner for everyone ~"Accepting merge requests", Category:Runner, UX, ~"Verify [DEPRECATED]", devopsverify, feature, frontend, grouprunner -
#16579 (closed) Introduce Variable to Indicate Current Build Status Category:Runner, ~"Verify [DEPRECATED]", ~"ci variables", devopsverify, feature, grouprunner -
#16167 (closed) Change Runner back to shared after marking it as specific Category:Runner, ~"Verify [DEPRECATED]", auto updated, devopsverify, feature, grouprunner, potential proposal -
#14500 (closed) Allow non-admin access to gitlab runner information via API Category:Runner, ~"Verify [DEPRECATED]", api, devopsverify, feature, grouprunner -
#15201 (closed) Builds Running counter Category:Runner, Manage [DEPRECATED], ~"Verify [DEPRECATED]", admin dashboard, auto updated, devopsverify, feature, grouprunner, pipeline
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 |
Unscheduled ~bug (non-customer)
-
#34366 (closed) /api/v4/jobs/request error: ActiveRecord::RecordNotSaved: Failed to remove the existing associated runner_session. The record failed to save after its fore... Category:Runner, ~"P3", ~"S3", ~"bug", devopsverify, grouprunner -
#33495 (closed) Gitlab is no longer running pipelines Category:Runner, ~"P2", ~"S2", awaiting feedback, ~"bug", devopsverify, grouprunner -
#30431 (closed) Issue with artifact timeout on private runners. Category:Runner, ~"P3", ~"S3", ~"artifacts", ~"bug", devopsverify, grouprunner
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: