Frontend: Only show latest downstream pipeline and trigger job in the pipeline graphs
From #350243 (comment 831541437)
If you try to retry a trigger job several times, you may end up with something like this:
Since retrying a trigger job creates new downstream pipelines, they all get added to our pipeline graphs.
This issue is a follow up for #350243 (closed) to only show the latest downstream pipelines and bridge jobs in the pipeline graph and pipeline mini graph.
Implementation
The full breakdown of this epic is as follows:
| Iteration | Description | Link |
|---|---|---|
| - | DESIGN/DISCUSSION | #343256 (closed) |
| 1 | BACKEND: Add route for show page | #347060 (closed) |
| 1 | FRONTEND: Create show page | #345046 |
| 1 | BACKEND: Add functionality for retry button no 1 (retry bridge job; re-create new downstream pipeline) | #345050 (closed) |
| 1 | FRONTEND: Add button no 1 and tie it to the functionality (retry bridge job; re-create new downstream pipeline) | #350243 (closed) |
| 1 | FRONTEND: Redirect old trigger jobs to the latest trigger job | #352472 (closed) |
| 1 | FRONTEND: Only show latest downstream pipeline and trigger job in the pipeline graphs |
|
| 2 | BACKEND: Add functionality for retry button no 2 (retry failed/canceled jobs) | #348904 (closed) |
| 2 | FRONTEND: Add split button and tie it to the functionality (retry failed/canceled jobs) | #32559 (closed) |
| 3 | BACKEND: Add functionality for retrying from the graph (or what we say is iteration 3) | #323470 (closed) |
| 3 | FRONTEND: Add button/icon for retrying from graph | ? |
Edited by Mark Nuzzo