Trigger downstream pipeline fails but cannot retry - wasting time waiting
What is the GitLab engineering productivity problem to solve?
When a parent pipeline triggers a downstream pipeline to start the parent pipeline will fail if the same branch does not exist in the downstream project. After creating the branch in the downstream project there is no way to retry the parent pipeline to simply run the last failed job which is to trigger the downstream project to start a new pipeline. The workaround is to start a whole new pipeline in the parent project which is a significant time waster! Would be nice if there was simply a retry button on the parent pipeline to negate the need for the workaround.
Image shows there is no Retry option.
Problem identification checklist
-
The root cause of the problem is identified. -
The surface of the problem is as small as possible.
What are the potential solutions?
Would be nice if there was simply a retry button on the parent pipeline to negate the need for the workaround of starting an entire new parent pipeline. The retry would simply just retry the last job that failed which was to trigger the downstream project to start a new pipeline.