13.3 Continuous Integration retrospective
This is an asynchronous retrospective for the 13.3 release, following the process described in the handbook.
This issue is private (confidential) to the Continuous Integration team, plus anyone else who worked with the team during 13.3, to ensure everyone feels comfortable sharing freely. On 2020-08-26, in preparation for the engineering-wide 13.3 Retrospective, the issue will be opened up to the public, as long as everyone is comfortable with this. You're free to redact any comments that contain information that you'd like to stay private before that date.
Please look at back at your experiences working on this release, ask yourself
For each point you want to raise, please create a new discussion with the relevant emoji, so that others can weigh in with their perspectives, and so that we can easily discuss any follow-up action items in-line.
If there is anything you are not comfortable sharing here, please message your manager directly. Note, however, that 'Emotions are not only allowed in retrospectives, they should be encouraged', so we'd love to hear from you here if possible.
Issues we shipped
- Take DAG visualization out of beta
- Merge widget gives ambiguous UI instructions when merge trains are enabled
- Group storage quota not displayed - Console shows errors
- Efficient counters
Ci::JobArtifact#update_project_statistics
fails because of statement timeout- CI: allow "never" in job:artifacts:expire_in
- Make it possible to define a cartesian product/matrix for build jobs
- More issues - this list only includes deliverables!
Issues that slipped
- Cannot find element #js-pipeline-graph-vue console error
- E2E pipeline web runner
- follow-up from "implement #bridge API endpoint"
- Inconsistent behavior when using needs with skipped jobs
- Ability to render a processed (merged) gitlab-ci.yml file
- Allow MR to merge even when pipeline is blocked
- Total deliverables closed: 7
- Total issues closed: 38
- Total MRs merged: 97