Technical spike - expose unexpected behavior when recreating a downstream pipeline
As part of &6947 (closed), we would like to provide the ability to recreate a downstream pipeline, during our implementation we discovered several unexpected behaviors mainly in the UI, the focus of this spike is to try to expose some of the unexpected behavior and understand the level of effort to implement the 2nd phase of this epic
Implementation plan
Iteration | Description | Link |
---|---|---|
1 | DESIGN/DISCUSSION | https://gitlab.com/gitlab-org/ci-cd/pipeline-authoring/-/issues/53 |
2 | Frontend: Add a retry button to a downstream pipeline on the pipeline graph | #354974 (closed) |
3 | Backend: Differentiate trigger jobs from regular jobs in the UI | #355751 (closed) |
4 | Design: Differentiate trigger jobs in the UI | #340194 (closed) |
5 | Frontend: Differentiate trigger jobs from regular jobs in the pipeline graph | #356330 (closed) |
6 | Frontend: Differentiate trigger jobs from regular jobs in the mini pipeline | #356331 |
7 | Technical spike - expose unexpected behavior when recreating a downstream pipeline |
|
8 | Backend issue to recreate downstream pipeline | |
9 | Implement retry on trigger job | #367547 (closed) |
Edited by James Heimbuck