2019-09-16 - Triage report for "group::continuous integration"
Hi, @jlenny @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
-
#17577 Create a build status view suitable for a large display and readable from across a room Category:Continuous Integration, UX, ~"Verify [DEPRECATED]", customer, devopsverify, feature, ~"group::continuous integration" -
#17518 Retrying a pipeline retries only the failed jobs Category:Continuous Integration, ~"Verify [DEPRECATED]", customer, devopsverify, feature, ~"group::continuous integration", pipeline -
#17407 Different maximum artifacts size for different repositories (and/or dynamically changing artifacts size) Category:Continuous Integration, ~"Verify [DEPRECATED]", ~"artifacts", customer, devopsverify, feature, ~"group::continuous integration", settings -
#16442 (closed) CI variables silently expanding variables Category:Continuous Integration, ~"Verify [DEPRECATED]", ~"ci variables", customer, devopsverify, feature, ~"group::continuous integration" -
#16398 (closed) GitLab API for CI/CD pipeline settings Category:Continuous Integration, ~"Verify [DEPRECATED]", api, auto updated, customer, devopsverify, feature, ~"group::continuous integration", pipeline, potential proposal, settings -
#16274 gitlab ci: allow jobs to be triggered based on some sort of 'expiry' Category:Continuous Integration, ~"Verify [DEPRECATED]", ~"artifacts", customer, devopsverify, feature, ~"group::continuous integration" -
#16259 (closed) Cancel all pipelines for a project Category:Continuous Integration, ~"Verify [DEPRECATED]", customer, devopsverify, feature, ~"group::continuous integration", pipeline -
#16057 Show browser notification after build when on build log page Category:Continuous Integration, UX, ~"Verify [DEPRECATED]", customer, devopsverify, feature, ~"group::continuous integration" -
#15117 (closed) Exclude configuration files for builds Category:Continuous Integration, ~"Verify [DEPRECATED]", customer, devopsverify, feature, ~"group::continuous integration" -
#15150 (closed) Escaping GitLabCI Variables in Lint Category:Continuous Integration, ~"Verify [DEPRECATED]", customer, devopsverify, feature, ~"group::continuous integration"
Unscheduled feature (non-customer)
-
#31882 Visually distinguish between branch and external pull request pipeline Category:Continuous Integration, devopsverify, feature, ~"group::continuous integration" -
#31491 Pipeline-level hooks devopsverify, feature, ~"group::continuous integration", ~"hooks", internal customer, pipeline, ~"webhooks" -
#31448 (closed) Jobs API browse Artifacts api, devopsverify, feature, ~"group::continuous integration" -
#31772 (closed) Pipeline access to get a single file using CI_JOB_TOKEN devopsverify, feature, ~"group::continuous integration", pipeline -
#31754 build status and coverage badges should be relative paths devopsverify, feature, ~"group::continuous integration" -
#14954 Provide API to retrieve test case durations from a pipeline api, backend, devopsverify, feature, ~"group::continuous integration", internal customer -
#14855 Show shared runner minutes usage by label Category:Continuous Integration, devopsverify, feature, ~"group::continuous integration" -
#31683 Allow fetching extra git refs in CI when shallow cloning is enabled devopsverify, feature, ~"group::continuous integration" -
#31581 (closed) Allow rules to set the needs of job attributes devopsverify, feature, ~"group::continuous integration" -
#31229 Allow CI runner tag "preference" Category:Continuous Integration, devopsverify, feature, ~"group::continuous integration" -
#30916 Show estimated wait time when waiting for pipeline runner Category:Continuous Integration, devopsverify, feature, ~"group::continuous integration" -
#30084 (closed) Improved visibility into Shared Runner usage Category:Continuous Integration, devopsverify, feature, ~"group::continuous integration" -
#29626 (closed) Move multi-project-pipeline to the Community Edition ~"Accepting merge requests", Category:Continuous Integration, ~"Verify [DEPRECATED]", auto updated, devopsverify, direction, feature, ~"group::continuous integration", ~"multi-project pipelines", potential proposal, stewardship -
#29568 (closed) Ability to view the merged .gitlab-ci.yml file in the pipeline Category:Continuous Integration, devopsverify, feature, ~"group::continuous integration", pipeline -
#29540 How to find out whether the pipeline event is the result of user trigger, scheduler, API trigger? Category:Continuous Integration, ~"Verify [DEPRECATED]", devopsverify, feature, ~"group::continuous integration", 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 | ~"No severity" | |
|---|---|---|---|---|---|
| ~P1 | 1 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 61 | 2 | 0 | 1 |
| ~P3 | 0 | 1 | 174 | 7 | 0 |
| ~P4 | 0 | 0 | 35 | 90 | 0 |
| ~"No priority" | 0 | 1 | 1 | 1 | 3 |
Unscheduled frontend ~bug (non-customer)
-
#14956 (closed) pipeline view is cropped on Firefox ~"S4", ~"bug", devopsverify, frontend, ~"group::continuous integration" -
#31607 Gitlab CI doesn't include warnings in notification email ~"P3", ~"S3", ~"bug", devopsverify, emails, frontend, ~"group::continuous integration", pipeline
Unscheduled ~bug (non-customer)
-
#14965 (closed) Tag artifacts link stopped working ~"S2", ~"artifacts", ~"bug", devopsverify, ~"group::continuous integration" -
#31694 (closed) Bad characters in CI_COMMIT_MESSAGE environment variable ~"S3", ~"bug", ~"ci variables", devopsverify, ~"group::continuous integration", pipeline -
#31673 (closed) Subsequent jobs are executed although dependency failed ~"bug", devopsverify, ~"group::continuous integration", pipeline -
#31657 Error on uploading artifacts to coordinator (403 Forbidden) devops::verify ~"artifacts", awaiting feedback, ~"bug", devopsverify, ~"group::continuous integration", support request -
#14757 (closed) Failed to load code climate report Category:Code Quality, ~"P3", ~"S3", ~"bug", devopsverify, ~"group::continuous integration" -
#14734 (closed) Masked variables still visible in the job log for any member role Category:Continuous Integration, ~"P4", ~"S4", ~"artifacts", ~"bug", devopsverify, ~"group::continuous integration" -
#31560 (closed) Pipeline Retry does not satisfy 'needs' depdendency Category:Continuous Integration, ~"P2", ~"S2", ~"bug", devopsverify, ~"group::continuous integration", pipeline -
#31352 (moved) GIT_DEPTH specified per env. in gitlab-runner configuration doesn't work. Category:Continuous Integration, ~"P3", ~"S3", ~"bug", devopsverify, ~"group::continuous integration" -
#31108 (closed) Merge Requests Ignore Failing Pipelines Delivery, ~"P3", ~"S3", ~"bug", devopsverify, ~"group::continuous integration", pipeline -
#29638 (closed) "Could not retrieve the pipeline status." merge request error with external CI Category:Continuous Integration, ~"P4", ~"S4", ~"Verify [DEPRECATED]", ~"bug", devopsverify, ~"group::continuous integration", pipeline -
#29635 (closed) Multiple jobs for same environment Category:Release Orchestration, ~"P4", ~"Release [DEPRECATED]", ~"S4", ~"bug", ~"devops::release", environments, ~"group::continuous integration" -
#29605 (closed) pipeline trigger twice when push to remote Category:Continuous Integration, ~"P3", ~"S3", ~"Verify [DEPRECATED]", ~"bug", devopsverify, ~"group::continuous integration", needs investigation, pipeline -
#29586 (closed) CI/CD "only" for jobs does not work Category:Continuous Integration, ~"P3", ~"S3", ~"Verify [DEPRECATED]", ~"bug", devopsverify, ~"group::continuous integration", pipeline -
#29571 (closed) NoMethodError: undefined method `any?' for nil:NilClass Category:Continuous Integration, ~"P4", ~"S4", ~"Verify [DEPRECATED]", ~"bug", devopsverify, ~"group::continuous integration", workflowready for development -
#29542 (closed) Retrying a job doesn't notify the user that triggered that Category:Continuous Integration, ~"P3", ~"S3", ~"Verify [DEPRECATED]", ~"bug", devopsverify, ~"group::continuous integration", notifications
Heatmap for ~missed-SLO bugs
| ~S1 | ~S2 | ~S3 | ~S4 | |
|---|---|---|---|---|
| ~P1 | 1 | 0 | 0 | 0 |
| ~P2 | 0 | 32 | 2 | 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 Jason Yavorsky