14.2 Pipeline Authoring retrospective
This is an asynchronous retrospective for the 14.2 release, following the process described in the handbook.
This issue is private (confidential) to the Pipeline Authoring group, plus anyone else who worked with the group during 14.2, to ensure everyone feels comfortable sharing freely. On 2021-08-26, in preparation for the R&D-wide 14.2 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
- Show the "tip" alert in the job dependencies view only once per user
- Pipeline header status doesn't update once pipeline has finished, even when jobs are retried
- Update PipelineNotificationWorker to utilize new Sidekiq readonly database replicas capabilities
- Add the ability to show pipelines within vscode
- Allow
needs:
(DAG) to refer to a job in the same stage - More issues - this list only includes deliverables!
Issues that slipped
No missed deliverables found; great job!
- Total deliverables closed: 5
- Total issues closed: 16
- Total MRs merged: 37