Retry Docker build jobs
What does this MR do?
Allows Docker build jobs to retry once in case of flaky build.
Why was this MR needed?
Are there points in the code the reviewer needs to double check?
I decided to add the retry section to the base job definitions, since the flakiness could manifest in any of the jobs, not just development servercore1809 helper docker image or development docker images.
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)
Edited by Pedro Pombeiro