Skip to content

Retry docker building jobs

Steve Xuereb requested to merge add-retry-for-flaky-jobs into master

What does this MR do?

Retry docker building jobs

Why was this MR needed?

These jobs constantly fail for flaky reasons such as:

There is not much we can do to prevent failures like these since they are network-related or some data races inside of upstream dependencies. Retrying the job usually fixes the issue but this requires manual intervention and when using merge train it's not possible to retry a failed job because the SHA doesn't exist anymore.

Add retry to automatically retry the job on failure.

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Added tests for this feature/bug
  • In case of conflicts with master - branch was rebased

What are the relevant issue numbers?

closes #25648 (closed)

Merge request reports