2019-09-30 - 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
- #32814 (closed) multiple cache in a same job Category:Continuous Integration, customer, ~"devops", devopsverify, feature, ~"group::continuous integration", pipeline
Unscheduled feature (non-customer)
- #32824 (closed) (confidential) ~"(confidential)"
- #32712 (closed) Retry manual job with different variables Category:Continuous Integration, devopsverify, feature, ~"group::continuous integration"
- #32667 (moved) Allow images and services to override pull policy devopsverify, feature, ~"group::continuous integration"
- #32610 modify commit and retry stage devopsverify, feature, ~"group::continuous integration", pipeline
- #32446 Docs feedback - feature proposal: Support protected environments and manual execution of multi-project pipeline triggers devopsverify, feature, ~"group::continuous integration", ~"multi-project pipelines", pipeline
- #31958 (closed) Add Build Artifacts overview to project's CI/CD menu Category:Continuous Integration, Delivery, ~"artifacts", devopsverify, feature, ~"group::continuous integration"
- #31957 (closed) add proper pagination to project's job view Category:Continuous Integration, Delivery, UX, ~"component::pagination", devopsverify, feature, frontend, ~"group::continuous integration"
- #23423 (closed) Possibility to copy a Pipeline schedule auto updated, awaiting feedback, devopsverify, ~"enhancement", 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 | 0 | 0 | 0 | 0 | 0 |
| ~P2 | 1 | 62 | 2 | 0 | 1 |
| ~P3 | 0 | 1 | 174 | 7 | 0 |
| ~P4 | 0 | 0 | 35 | 92 | 0 |
| ~"No priority" | 0 | 1 | 6 | 2 | 6 |
Unscheduled ~bug with customer
- #32702 (closed) Scheduled Pipeline not kicking off Category:Continuous Integration, ~"bug", customer, devopsverify, ~"group::continuous integration", pipeline
Unscheduled ~bug (non-customer)
- #32912 (closed) GlModal refactor introduces breaking changes Category:Continuous Integration, Deliverable, ~"Verify [DEPRECATED]", ~"backstage", ~"bug", ~"component::modals", devopsverify, ~"group::continuous integration"
- #32837 (closed) all 'interruptible' jobs in a pipeline should be cancellable ~"S3", ~"bug", ci-build, devopsverify, ~"group::continuous integration"
- #32740 (closed) We can't specify Tokyo to timezone in Pipeline Schedule. ~"S4", ~"bug", devopsverify, ~"group::continuous integration"
- #32687 (closed) Setting the value of a variable in an environment sometimes overwrites the value of the same variable in another environment Category:Continuous Integration, Enterprise Edition, ~"bug", ~"ci variables", devopsverify, ~"group::continuous integration", settings
- #32598 Bad interaction of needs and allow_failure keywords. ~"S4", ~"bug", devopsverify, ~"group::continuous integration", pipeline
- #32552 Manual job depending on another manual job: Dependency is ignored ~"S3", ~"bug", devopsverify, ~"group::continuous integration"
- #32257 (closed) Merge when pipeline succeeds accidentally merge before it finishes on commit status creation Category:Continuous Integration, ~"S3", ~"bug", devopsverify, ~"group::continuous integration", merge requests
- #32204 (closed) Gitlab ci validation complains about using rules with && and || at the same time Category:Continuous Integration, ~"S3", ~"bug", devopsverify, ~"group::continuous integration"
- #31909 (closed) Job artefacts without expire_in wouldn't be expired with instance wide expire policy if they were create when instance-wide expire policy wasn't set up Category:Continuous Integration, ~"S3", ~"artifacts", ~"bug", devopsverify, ~"group::continuous integration"
Heatmap for ~missed-SLO bugs
| ~S1 | ~S2 | ~S3 | ~S4 | |
|---|---|---|---|---|
| ~P1 | 0 | 0 | 0 | 0 |
| ~P2 | 1 | 33 | 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:
