2019-09-09 - 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:

  • 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://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/issue_workflow.md#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.

Unscheduled feature (non-customer)

  • #14402 Ability to add @username on Builds emails Category:Continuous Integration, ~"Verify [DEPRECATED]", devopsverify, feature, ~"group::continuous integration", notifications
  • #14358 (closed) [CI] environment variables in CI scripts Category:Continuous Integration, ~"Verify [DEPRECATED]", ~"ci variables", devopsverify, feature, ~"group::continuous integration"
  • #14338 (closed) Feature Request: Build promotion Category:Continuous Integration, ~"Verify [DEPRECATED]", devopsverify, feature, ~"group::continuous integration"
  • #14335 (closed) Show the type of executor each shared Runner is configured with Category:Continuous Integration, ~"Verify [DEPRECATED]", devopsverify, feature, ~"group::continuous integration"
  • #14300 Add Web hook Trigger that is executed only if a build succeeds Create [DEPRECATED], Manage [DEPRECATED], auto updated, devopsverify, feature, ~"group::continuous integration", pipeline, potential proposal, ~"webhooks"
  • #14256 Feature Request: Treat interrupted builds as "pending" again instead of "failed" Category:Continuous Integration, ~"Verify [DEPRECATED]", devopsverify, feature, ~"group::continuous integration"
  • #14246 (closed) Per Runner Variables Category:Continuous Integration, ~"Verify [DEPRECATED]", ~"ci variables", devopsverify, feature, ~"group::continuous integration"
  • #13950 More featureful base commit_status Category:Continuous Integration, ~"Verify [DEPRECATED]", devopsverify, feature, ~"group::continuous integration"

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 10 0 0
~P3 0 0 27 0
~P4 0 0 5 12
~"No priority" 0 0 0 1

Unscheduled ~bug (non-customer)

  • #14734 (closed) Masked variables still visible in the job log for any member role ~"S4", ~"artifacts", ~"bug", devopsverify, ~"group::continuous integration"
  • #14322 (closed) 8.6.2 CI Uploading artifacts error 500 Category:Continuous Integration, ~"P3", ~"S3", ~"Verify [DEPRECATED]", ~"bug", devopsverify, ~"group::continuous integration"

Heatmap for ~missed-SLO bugs

~S1 ~S2 ~S3 ~S4
~P1 0 0 0 0
~P2 0 4 0 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:

  • https://about.gitlab.com/handbook/engineering/quality/triage-operations/index.html#triage-packages
Edited Sep 09, 2019 by Jason Yavorsky
Assignee Loading
Time tracking Loading