2019-10-28 - Triage report for "group::continuous integration"

Hi, @jlenny @crystalpoole @dcipoletti

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/triage-operations/index.html#triage-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.
- https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#priority-labels
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

#34524 Ability to add description for CI/CD variables ~"ci variables", customer, devopsverify, feature, ~"group::continuous integration"
#34108 (closed) Select or search/filter manual CI jobs Category:Continuous Integration, customer, devopsverify, feature, ~"group::continuous integration"

Unscheduled feature (non-customer)

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	63	3	0	0
~P3	0	1	193	7	0
~P4	0	0	35	98	0
~"No priority"	0	0	5	3	1

Unscheduled ~bug with customer

#34819 ActiveRecord::QueryCanceled: PG::QueryCanceled: ERROR: canceling statement due to statement timeout Category:Continuous Integration, ~"P2", ~"S2", ~"bug", customer, devopsverify, ~"group::continuous integration", reproduced on GitLab.com

Unscheduled ~bug (non-customer)

Heatmap for ~missed-SLO bugs

	~S1	~S2	~S3
~P1	0	0	0
~P2	1	39	2
~P3	0	0	1
~P4	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:

https://about.gitlab.com/handbook/engineering/quality/triage-operations/index.html#triage-packages

0 of 30 checklist items completed