2019-08-19 - Triage report for "group::runner"
Hi, @joshlambert @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:
- https://about.gitlab.com/handbook/engineering/quality/guidelines/triage-operations/#current-packages
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.
customer
Unscheduled ~feature with-
#65174 (moved) Get the environment info for a running job in GET /projects/:id/jobs/:id ~"Category::Runner", ~"Verify", api, customer, devopsverify, ~"feature", grouprunner -
#58818 (moved) Allow existing runners to be shared with group ~"Category::Runner", ~"Manage", ~"P4", ~"S4", customer, devopsmanage, ~"feature", grouprunner, ~"groups" -
#58718 (moved) Pending CI jobs time out earlier than the configured time out. ~"Category::Runner", ~"Verify", customer, devopsverify, ~"feature", grouprunner, ~"missed-SLO", needs investigation -
#58092 (moved) Notify administrators if runners are outdated/invalid ~"Category::Runner", customer, devopsverify, ~"feature", grouprunner, ~"logging" -
#51659 (moved) Allow customization of one-click Kubernetes Runner ~"Category::Runner", customer, devopsverify, ~"feature", grouprunner, ~"kubernetes" -
#50373 (moved) Allow a group runner to be shared between multiple groups ~"Category::Runner", ~"Manage", ~"Verify", auto updated, customer, devopsverify, ~"feature", grouprunner, ~"groups", potential proposal, settings -
#46263 (moved) Disable specific runners for a project, group or server ~"Category::Runner", ~"Manage", ~"Verify", admin dashboard, customer, customer+, devopsverify, ~"feature", grouprunner, settings -
#42060 (moved) Show hostname and/or IP of a runner in settings/ci_cd ~"Category::Runner", UX, ~"Verify", customer, devopsverify, ~"feature", grouprunner, settings -
#35196 (moved) Project level tags for shared runners ~"Category::Runner", ~"Verify", customer, devopsverify, ~"feature", grouprunner -
#30142 (moved) GitLab Runner description is not updated in the runner logs when changed through the UI ~"Category::Runner", ~"P4", ~"S4", ~"Verify", customer, devopsverify, ~"feature", grouprunner -
#25772 (moved) Automatically remove a runner after inactivity ~"Category::Runner", ~"Verify", auto updated, customer, devopsverify, ~"feature", grouprunner, pipeline, potential proposal
Unscheduled ~feature (non-customer)
-
#66087 (moved) Automated Runner Key and Registration Rotation ~"Category::Runner", ~"Verify", devopsverify, ~"enhancement", ~"feature", grouprunner -
#66047 (moved) Show estimated wait time when waiting for pipeline runner devopsverify, ~"feature", grouprunner -
#66026 (moved) Admin: Do not allow associate runner with archived projects ~"Category::Runner", devopsverify, ~"feature", grouprunner, settings -
#65879 (moved) Pricing for Mac and Windows Shared Runners Alliances, ~"Category::Runner", devopsverify, ~"feature", grouprunner -
#64452 (moved) Add meta selectors for jobs to select runner on architecture/os/executor ~"Category::Runner", ~"Verify", devopsverify, ~"feature", grouprunner -
#63180 (moved) Only schedule jobs when runner available ~"Category::Runner", ~"Verify", devopsverify, ~"feature", grouprunner -
#62879 (closed) Docs feedback: Write your title ~"Category::Runner", ~"Verify", devopsverify, ~"feature", grouprunner -
#56844 (moved) Pre-initialization of jobs ~"Category::Runner", ~"Verify", ~"devops", devopsverify, ~"feature", grouprunner -
#56675 (moved) docker+machine cloud permissions or middleware ~"Category::Runner", ~"Verify", devopsverify, ~"feature", grouprunner -
#56587 (moved) Gitlab runner won't run for more than two hours, even though the repository was configured to allow eight hour jobs ~"Category::Runner", ~"Verify", devopsverify, ~"feature", grouprunner -
#56565 (closed) Docs feedback: Mention resetting runner token via gitlab-rails console ~"Category::Runner", ~"Documentation", ~"Verify", devopsverify, ~"feature", grouprunner -
#56476 (moved) Increase limitation size for memory of docker containers used in gitlab shared runners ~"Category::Runner", ~"Verify", devopsverify, ~"feature", grouprunner -
#56421 (moved) Accessing the node index of a concurrent Gitlab runner ~"Category::Runner", ~"Verify", devopsverify, ~"feature", grouprunner -
#55920 (moved) Add an ability of sorting runners using cached contacted_at values on the "admin/runners" page ~"Category::Runner", ~"Verify", admin dashboard, devopsverify, ~"feature", grouprunner -
#54248 (moved) Add CI runner shared for all user personal projects ~"Category::Runner", ~"Verify", 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
~S1 | ~S2 | ~S3 | ~S4 | |
---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 |
~P2 | 0 | 1 | 0 | 0 |
~P3 | 0 | 1 | 9 | 0 |
~P4 | 0 | 0 | 1 | 2 |
customer
Unscheduled ~bug with-
#57008 (moved) API: can't access subgroup runner with inherited role ~"Category::Runner", ~"P4", ~"S3", ~"Verify", api, ~"bug", customer, devopsverify, grouprunner, reproduced on GitLab.com -
#53296 (moved) Don't allow group runners to be assigned to projects via admin ~"Category::Runner", ~"P3", ~"S3", ~"Verify", ~"bug", customer, devopsverify, grouprunner -
#45904 (moved) gitlab-runner sometimes ignores jobs ~"Category::Runner", ~"P3", ~"S3", ~"Verify", ~"bug", customer, devopsverify, grouprunner -
#66198 (moved) Clarify in documentation when pagination will be used for API calls ~"Category::Runner", ~"Documentation", ~"P4", ~"S4", api, ~"bug", customer, devopsverify, docs-only, grouprunner
Unscheduled ~bug (non-customer)
-
#65121 (moved) Issue with artifact timeout on private runners. ~"Category::Runner", ~"P3", ~"S3", ~"artifacts", ~"bug", devopsverify, grouprunner -
#65057 (moved) Error 500 for gitlab runners after update from Gitlab CE 12.0.3 -> 12.1.0 ~"Category::Runner", ~"P2", ~"S2", awaiting feedback, ~"bug", devopsverify, grouprunner -
#50458 (moved) pipeline jobs stuck without global runner ~"Category::Runner", ~"P3", ~"S3", ~"Verify", ~"bug", devopsverify, grouprunner, needs investigation, pipeline -
#49387 (moved) Job succeeds if artifact upload fails ~"Category::Runner", ~"P3", ~"S3", ~"Verify", ~"bug", devopsverify, grouprunner, needs investigation -
#40322 (closed) Job timeout neglected ~"Category::Runner", ~"P3", ~"S3", ~"Verify", ~"bug", default-priority, default-severity, devopsverify, grouprunner -
#19770 (moved) gitlab ci cache and python virtualenv issues warnings for symlinked files on re-use "WARNING: ...: chmod ...: no such file or directory" ~"Category::Runner", ~"P3", ~"S3", ~"Verify", ~"artifacts", ~"bug", devopsverify, grouprunner
Heatmap for ~missed-SLO bugs
~S1 | ~S2 | ~S3 | ~S4 | ~"No severity" | |
---|---|---|---|---|---|
~P1 | 0 | 0 | 0 | 0 | 0 |
~P2 | 0 | 0 | 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: