2019-09-30 - Triage report for "group::release management"
Hi, @ogolowinski @darbyfrey @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.
Unscheduled feature (non-customer)
-
#32827 (closed) Create a page per Release entry Category:Release Orchestration, UX, ~"devops::release", feature, frontend, ~"group::release management"
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 | 11 | 1 | 0 |
| ~P3 | 0 | 1 | 41 | 2 |
| ~P4 | 0 | 0 | 13 | 22 |
Unscheduled ~bug with customer
-
#32599 Invalid environment name generated using $CI_COMMIT_REF_NAME silently fails to create environment Category:Continuous Delivery, ~"Category:Release Governance", ~"P4", ~"S4", ~"bug", ~"ci variables", customer, ~"devops::release", environments, ~"group::release management"
Unscheduled ~bug (non-customer)
-
#32893 The GitLab Pages auth page says "Please note that this application is not provided by GitLab and you should verify its authenticity before allowing access." which is incorrect on fresh install of omnibus Category:Pages, ~"P4", ~"S4", ~"bug", ~"devops::release", ~"group::release management" -
#31869 (closed) Duplicate rows with the same tag name in Release Category:Release Orchestration, ~"P2", ~"S2", ~"bug", ~"devops::release", ~"group::release management" -
#27606 (closed) Download source code from Release page return error 404 Category:Release Orchestration, ~"P3", ~"Release [DEPRECATED]", ~"S3", awaiting feedback, ~"bug", ~"devops::release", ~"group::release management", permissions -
#27565 (closed) CI Validation false positive, checks before variable expansion Category:Release Orchestration, ~"P4", ~"Release [DEPRECATED]", ~"S4", ~"bug", ~"devops::release", environments, ~"group::release management", pipeline -
#27254 (closed) Redirection from pages to docker registry Category:Pages, ~"P2", ~"Release [DEPRECATED]", ~"S2", ~"bug", ~"devops::release", ~"group::release management", ~"missed-SLO", ~"release::validation::backlog", support request -
#27238 (closed) Re-deployment does not create git ref for deployment Category:Release Orchestration, ~"P2", ~"Release [DEPRECATED]", ~"S2", ~"bug", ~"devops::release", environments, ~"group::release management", ~"missed-SLO", repository -
#26876 (closed) Gitlab Pages: 404, and work fine after restart gitlab or restart gitlab pages Category:Pages, ~"P3", ~"Release [DEPRECATED]", ~"S3", awaiting feedback, ~"bug", ~"devops::release", ~"group::release management", ~"release::validation::backlog" -
#26007 (closed) Improve error handling in UpdatePagesServiceCategory:Pages, ~"P4", ~"Release [DEPRECATED]", ~"S4", ~"bug", ~"devops::release", ~"group::release management" -
#25777 (closed) Unable to create custom domain without a certificate via API Category:Pages, ~"P3", ~"Release [DEPRECATED]", ~"S3", api, ~"bug", ~"devops::release", ~"group::release management", ~"release::validation::backlog" -
#25763 (closed) Force HTTPS (requires valid certificates) checkbox doesn't work ~"Accepting merge requests", Category:Pages, ~"P3", ~"Release [DEPRECATED]", ~"S3", ~"bug", ~"devops::release", ~"group::release management", ~"release::validation::backlog" -
#25573 (closed) Environments are not stopped when project is archived and cannot be stopped after archiving Category:Release Orchestration, ~"P3", ~"Release [DEPRECATED]", ~"S3", ~"bug", deploy, ~"devops::release", environments, ~"group::release management" -
#25411 (closed) Pages access control doesn't pick-up custom CA certs on authentication Category:Pages, ~"P3", ~"Release [DEPRECATED]", ~"S3", ~"bug", ~"devops::release", ~"group::release management", ~"release::validation::backlog" -
#23302 (closed) GitLab Pages doesn't load assets when using absolute paths Category:Pages, ~"P3", ~"S3", ~"bug", ~"devops::release", documentation, ~"group::release management" -
#21884 (closed) Environment seeding validation fails Category:Release Orchestration, ~"P4", ~"Release [DEPRECATED]", ~"S4", ~"bug", deploy, ~"devops::release", environments, ~"group::release management" -
#21858 (closed) Projects::UpdatePagesService::FailedToExtractError: pages failed to extract Category:Pages, Object Storage, ~"P3", ~"Release [DEPRECATED]", ~"S3", ~"bug", ~"devops::release", ~"group::release management"
Heatmap for ~missed-SLO bugs
| ~S1 | ~S2 | ~S3 | ~S4 | |
|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 7 | 1 | 0 |
| ~P3 | 0 | 0 | 0 | 0 |
| ~P4 | 0 | 0 | 0 | 0 |
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:
Edited by Orit Golowinski