2020-10-05 - Triage report for "group::continuous integration"
Hi, @thaoyeager @cheryl.li @samdbeckham @v_mishra
This is a group or stage level triage report 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.
feature with customer
Unscheduled-
#258606 Allow both global and step-specific before_script to work when using 'extends' GitLab.com Feature Request, ~"ci::usage", customer, devopsverify, feature, ~"group::continuous integration", sectionops, ~"support-fix" -
#255908 Specify a fallback branch when triggering pipelines customer, devopsverify, feature, ~"group::continuous integration", sectionops -
#249140 (closed) Increment max size of artifacts for child/dynamic pipelines ~"ci::artifacts", customer, devopsverify, feature, ~"group::continuous integration", sectionops -
#248941 CI Pipeline Subscriptions without tags Category:Continuous Integration, ~"ci::interactions", customer, devopsverify, feature, ~"group::continuous integration", sectionops -
#246842 Disable scheduled pipeline jobs in Gitlab Globally not just at the job level Category:Continuous Integration, ~"ci::interactions", customer, devopsverify, feature, ~"group::continuous integration", sectionops -
#8177 (closed) Usage of variables in only: changes: paths Category:Continuous Integration, Enterprise Edition, auto updated, customer, devopsverify, feature, ~"group::continuous integration", pipeline, popular proposal, potential proposal, sectionops
feature (non-customer)
Unscheduled-
#260872 (closed) Store historical CI minute usage data Category:Continuous Integration, backend, ~"ci::usage", devopsverify, feature, ~"feature::maintenance", ~"group::continuous integration", sectionops -
#260422 (closed) Follow-up: Move pipeline header actions to mutations GraphQL, ~"ci::api-interactions", devopsverify, feature, ~"feature::maintenance", frontend, ~"group::continuous integration", ~"technical debt" -
#260395 (confidential) ~"(confidential)" -
#259619 (closed) Calculate checksum of an archived build trace feature, ~"group::continuous integration" -
#259010 Separate dry run pipeline creation service ~"ci::artifacts", devopsverify, feature, ~"feature::maintenance", ~"group::continuous integration", sectionops -
#258656 Audit CI/CD variable mask and unmask setting Category:Continuous Integration, ~"ci::variables", devopsverify, feature, ~"group::continuous integration", sectionops, sectionops -
#257889 (closed) Artifact download Category:Continuous Integration, ~"ci::artifacts", devopsverify, feature, ~"group::continuous integration" -
#255983 (closed) 'dotenv: report' artifacts replaced by newly run pipelines on the same commit ref backend, ~"ci::variables", devopsverify, feature, ~"group::continuous integration", sectionops -
#255975 Custom job shell Category:Continuous Integration, ci-build, devopsverify, feature, ~"group::continuous integration", sectionops, sectionops -
#252397 (closed) 'needs:' with logical OR Category:Continuous Integration, devopsverify, feature, ~"group::continuous integration", sectionops -
#250745 (confidential) ~"(confidential)" -
#250305 (closed) Re-trigger generated child pipeline Category:Continuous Integration, devopsverify, feature, featureaddition, ~"group::continuous integration", pipeline, sectionops -
#247679 Expose "this code previously succeeded" CI environment variables ~"ci::processing", devopsverify, feature, ~"group::continuous integration", sectionops -
#247074 (closed) "Checking pipeline status" for a merge request should include the reason why the check is still in progress Category:Continuous Integration, ~"ci::merge-request", devopsverify, feature, ~"group::continuous integration", sectionops -
#245221 Trigger unprotected pipelines on protected branches Category:Continuous Integration, ~"ci::permissions", devopsverify, feature, ~"group::continuous integration", sectionops -
#244878 Prevent pushes to a branch once an MR is on the Merge Train Category:Merge Trains, UX, ~"ci::merge-request", devopsverify, feature, featureaddition, ~"group::continuous integration", sectionops -
#244831 (closed) Split "Pipelines for merged results" and "Merge Train" check boxes Category:Continuous Integration, UX, ~"candidate::13.6", ~"ci::interactions", devopsverify, feature, featureaddition, ~"group::continuous integration", internal customer, sectionops, workflowdesign -
#244714 Artifacts with the same name from different jobs overwrite each other ~"ci::artifacts", devopsverify, feature, featureaddition, ~"group::continuous integration", pipeline, sectionops -
#244466 (closed) Remove ignore_column for Ci::JobArtifact#locked Category:Continuous Integration, backend, ~"ci::artifacts", database, devopsverify, feature, ~"feature::maintenance", ~"group::continuous integration", sectionops, ~"technical debt" -
#244287 Feature proposal: Mark-as-expected-to-have-built button on jobs. Category:Continuous Integration, ~"ci::interactions", devopsverify, feature, featureaddition, ~"group::continuous integration", sectionops -
#243784 Pipeline overview hides scrollbar from user at the bottom of the page Category:Continuous Integration, UI polish, UX, ~"ci::interactions", devopsverify, feature, ~"feature::maintenance", frontend, ~"group::continuous integration", priority2, sectionops, severity3 -
#243717 CI report artifacts unavailable to subsequent CI stages/jobs Category:Continuous Integration, Category:SAST, ~"ci::artifacts", devopsverify, feature, featureaddition, ~"group::continuous integration", sectionops -
#243339 (closed) Prevent artifact download for pipelines Category:Continuous Integration, ~"ci::artifacts", devopsverify, feature, featureaddition, ~"group::continuous integration", sectionops
UX debt Section
For the following UX debt issues. 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 UX debt
UX debt issues for their priority and severity label are counted here. Every UX debt issue should have severity and priority labels applied. Please take a look at the UX debt issues which fall into the columns indicating that the priority or severity labels are currently missing.
severity1 | severity2 | severity3 | severity4 | No severity | |
---|---|---|---|---|---|
priority1 | 0 | 0 | 0 | 0 | 0 |
priority2 | 0 | 0 | 0 | 0 | 0 |
priority3 | 0 | 0 | 0 | 0 | 0 |
priority4 | 0 | 0 | 0 | 0 | 0 |
No priority | 0 | 0 | 11 | 4 | 3 |
UI polish Section
For the following UI polish issues. 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 UI polish
UI polish issues for their priority and severity label are counted here. Every UI polish issue should have severity and priority labels applied. Please take a look at the UI polish issues which fall into the columns indicating that the priority or severity labels are currently missing.
severity1 | severity2 | severity3 | severity4 | No severity | |
---|---|---|---|---|---|
priority1 | 0 | 0 | 0 | 0 | 0 |
priority2 | 0 | 0 | 1 | 0 | 0 |
priority3 | 0 | 0 | 6 | 3 | 0 |
priority4 | 0 | 0 | 1 | 9 | 0 |
No priority | 0 | 0 | 1 | 6 | 67 |
Unscheduled UI Polish Issues
-
#243784 Pipeline overview hides scrollbar from user at the bottom of the page Category:Continuous Integration, UI polish, UX, ~"ci::interactions", devopsverify, feature, ~"feature::maintenance", frontend, ~"group::continuous integration", priority2, sectionops, severity3
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.
- Engineering Managers: Please add a severity label for those issues without one
- Product Designers: Please add a severity label to UX ~bug issues without one
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.
severity1 | severity2 | severity3 | severity4 | No severity | |
---|---|---|---|---|---|
priority1 | 0 | 1 | 0 | 0 | 0 |
priority2 | 0 | 70 | 14 | 0 | 0 |
priority3 | 0 | 5 | 193 | 8 | 1 |
priority4 | 0 | 0 | 21 | 81 | 1 |
No priority | 0 | 0 | 1 | 3 | 6 |
frontend ~bug with customer
Unscheduled-
#249552 (closed) "Could not retrieve the pipeline status" appears for merged MRs that only have a pipeline for merge requests backend, ~"bug", ~"ci::merge-request", customer, devopsverify, frontend, ~"group::continuous integration", pipeline, priority3, sectionops, severity3 -
#245312 Pipeline Stage shows pending despite successful external jobs Category:Continuous Integration, ~"bug", ~"ci::pipeline-graphs", customer, devopsverify, frontend, ~"group::continuous integration", pipeline, priority4, sectionops, severity4 -
#243676 CI/CD timestamps are inconsistent and hard to find Category:Continuous Integration, UX, ~"UX CI/CD Team", ~"bug", ~"ci::interactions", customer, devopsverify, frontend, ~"group::continuous integration", priority4, reproduced on GitLab.com, sectionops, severity3
frontend ~bug (non-customer)
Unscheduled-
#258977 (closed) Cross project arrow triangle is in the wrong position in the pipeline graph for upstream/downstream projects ~"bug", ~"ci::pipeline-graphs", devopsverify, frontend, ~"group::continuous integration", sectionops, sectionops -
#258630 (closed) Environment variables are not getting used under the flag new_pipeline_form Category:Continuous Integration, ~"bug", devopsverify, frontend, ~"group::continuous integration", sectionops, workflowverification -
#255932 (closed) Pipeline job graph isn't positioned properly ~"bug", devopsverify, frontend, ~"group::continuous integration", sectionops, severity4
customer
Unscheduled ~bug with-
#247856 Accessing CI jobs of a deleted environment results in 500 Internal Server Error Category:Continuous Integration, ~"bug", ~"ci::interactions", customer, devopsverify, ~"group::continuous integration", priority3, sectionops, severity3 -
#246992 (closed) ActionView::Template::Error: PG::QueryCanceled: ERROR: canceling statement due to statement timeout Category:Continuous Integration, backend, ~"bug", ~"ci::interactions", customer, devopsverify, ~"group::continuous integration", priority3, sectionops, severity3 -
#246822 (closed) Inconsistent Artifact API failure with ref_name Category:Continuous Integration, api, backend, ~"bug", ~"ci::artifacts", customer, devopsverify, ~"group::continuous integration", priority4, sectiondev, severity3 -
#244974 $CI_JOB_TOKEN starts with a -
causes job to fail Category:Continuous Integration, backend, ~"bug", ~"ci::permissions", customer, devopsverify, ~"group::continuous integration", priority2, sectionops, severity2 -
#240945 (closed) Code Quality and License Scanning jobs start immediately, regardless of position of 'test' stage in pipeline Category:Code Quality, Category:Continuous Integration, backend, ~"bug", ~"ci::processing", customer, devopsverify, ~"group::continuous integration", priority2, sectionops, severity3
Unscheduled ~bug (non-customer)
-
#260878 (closed) Fail jobs with missing artifact file for need/dependency Category:Continuous Integration, backend, ~"bug", ~"ci::artifacts", devopsverify, ~"group::continuous integration", sectionops -
#258982 (closed) Docs feedback: remove "Re-using a before_script template" section ~"bug", devopsverify, documentation, ~"group::continuous integration", priority4, sectionops -
#258632 (closed) To header in emails missing Category:Continuous Integration, ~"bug", ~"ci::notifications", devopsverify, emails, ~"group::continuous integration", notifications, sectionops, sectionops, severity4 -
#257885 (closed) [bug] New Pipeline does not forward variables to the runner's environment Category:Continuous Integration, ~"bug", ~"ci::variables", devopsverify, ~"group::continuous integration" -
#255292 (closed) Branch overview indicates running pipeline for multiple branches although only one pipeline running Category:Continuous Integration, ~"bug", devopsverify, ~"group::continuous integration", sectionops, severity3 -
#254956 Pending "Checking pipeline status" ~"bug", devopsverify, ~"group::continuous integration", priority3, sectionops -
#251091 (confidential) ~"(confidential)" -
#250850 Gitlab API does not provide pipeline variables that are coming from the pipeline schedule Category:Continuous Integration, api, backend, ~"bug", ~"ci::api-interactions", devopsverify, ~"group::continuous integration", priority3, sectionops, severity4 -
#249100 (confidential) ~"(confidential)" -
#249087 (closed) Kaminari::ZeroPerPageOperation: Current page was incalculable. Perhaps you called .per(0)? Category:Continuous Integration, ~"VerifyP1", ~"bug", ~"ci::api-interactions", devopsverify, ~"group::continuous integration", priority4, sectionops, severity4 -
#247951 (closed) Multi-project pipelines triggered via API do not display trigger variables Category:Continuous Integration, backend, ~"bug", ~"ci::api-interactions", devopsverify, ~"group::continuous integration", priority3, reproduced on GitLab.com, sectionops, severity2 -
#247480 (closed) Jobs with CI_COMMIT_REF_SLUG in image
do not get included on merge request Category:Continuous Integration, backend, ~"bug", devopsverify, ~"group::continuous integration", priority3, sectionops, severity3 -
#246505 (closed) Docker build failed but job suceed Category:Continuous Integration, backend, ~"bug", ~"ci::processing", devopsverify, ~"group::continuous integration", pipeline, priority3, sectionops, severity3 -
#245187 (closed) negative storage size reported Category:Continuous Integration, backend, ~"bug", ~"ci::usage", devopsverify, ~"group::continuous integration", priority2, sectionops, severity2 -
#244856 (closed) retry
isn't taken in account for Merge Train pipeline jobs? Category:Merge Trains, backend, ~"bug", ~"ci::merge-request", devopsverify, ~"group::continuous integration", priority2, sectionops, severity3, workflowready for development -
#243801 Artifact paths should not be limited to relative paths Category:Continuous Integration, backend, ~"bug", ~"ci::artifacts", devopsverify, ~"group::continuous integration", priority3, sectionops, severity3 -
#260418 (closed) Merge request can be mergerd although one CI is failing ~"bug", devopsverify, ~"group::continuous integration"
Heatmap for ~missed-SLO bugs
severity1 | severity2 | severity3 | severity4 | No severity | |
---|---|---|---|---|---|
priority1 | 0 | 1 | 0 | 0 | 0 |
priority2 | 0 | 62 | 0 | 0 | 0 |
priority3 | 0 | 2 | 0 | 0 | 0 |
priority4 | 0 | 0 | 0 | 0 | 0 |
No priority | 0 | 0 | 0 | 0 | 0 |
This is a group level triage report that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:
If assignees or people mentioned in this individual triage report need to be amended, please edit group-definition.yml.