Retry triggered jobs
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
I am using pipelines generated by artifacts.
It is very painful when one of the artifact generated pipelines has a job fail due to something (like concurrent docker build failure due to name clash) because when you restart the job and it fails, the parent pipeline does not continue.
This particular parent pipeline takes about an hour spread over several child pipelines. It is very disruptive when it fails after 40 minutes of successful running if the failure is unrelated to the actual job check because the parent pipeline will not continue once the child pipelines complete.
The parent/child pipeline process needs some love.
Example of failure unrelated to job script failing:
*** WARNING: Service runner-Mh4fF_s3-project-77-concurrent-0-docker-0 probably didn't start properly.
Health check error:
ContainerCreate: Error response from daemon: Conflict. The container name "/runner-Mh4fF_s3-project-77-concurrent-0-docker-0-wait-for-service" is already in use by container "9dfd125c65c27f678f688f15da130c537c32a017b3c26e54b52170b3f2120102". You have to remove (or rename) that container to be able to reuse that name. (executor_docker.go:1225:0s)