Failure pattern in delivery phase, re-trigger such builds?

[navidshaikh]

Few builds could fail in delivery phase with the issue "failed to open pod log file".

jboss-keycloack-adapter-wildfly-latest project build failed with the mentioned error in delivery phase - Logs. Pod was not able to open custom-build_0.log file.

This seems to be a race condition, it happened earlier and fixed with a re-trigger.

The build has, linter and scanner result, build logs, test logs, all went fine but delivery.

I think service can identify such issues, with a re-trigger action for such builds. IMO, the user experience in which we notify the user that the build has failed due to an issue at service-end does not give a good impression.

How about enabling a mechanism to retry delivery build in case of failure?