Frontend: Redirect old trigger jobs to the latest trigger job
When the user retries a trigger job and the job is successful, they are redirected to the newly-created downstream pipeline.
An issue occurs when they click the back button, or if they view old trigger jobs. Since the pipeline query in the frontend only receives the latest jobs, it doesn't have information about old trigger jobs, so the page bugs out and doesn't show any information.
Note that this is not an issue when the user goes to the trigger job through the pipeline graph or mini pipeline graph, since the links there are already updated with the latest trigger job. This issue only occurs when the user has the link to an old trigger job.
| From Pipeline Graph | From Mini Pipeline Graph |
|---|---|
| from_pipeline_graph | from_mini_pipeline_graph |
Ideally, we should redirect old trigger jobs to the latest trigger job show page.
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 | |
| 1 | FRONTEND: Only show latest downstream pipeline and trigger job in the pipeline graphs** | #352124 (closed) |
| 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 | ? |