jib icon indicating copy to clipboard operation
jib copied to clipboard

Published 20 hours ago • verified publisher icon GoogleContainerTools

Retry on HTTP 500?

Open rmannibucau opened this issue 2 years ago • 6 comments

Hi all,

It seems the retry mecanism jib has does not work with HTTP 500 (guess it is intended as of today). The issue is that some docker registry - gitea to not mention it ;) - have known issues where it can lead to HTTP 500 and need a few retries to pass. My current workaround is to wrap jib build in a retry loop but if JIB could handle the 500 directly and do a few retries it would be awesome and frictionless.

rmannibucau avatar Feb 22 '23 09:02 rmannibucau

@rmannibucau Are you suggesting some variation of the solution implemented here? https://github.com/GoogleContainerTools/jib/pull/3351

mpeddada1 avatar Feb 24 '23 21:02 mpeddada1

That is what I had in mind if it catches 500.

rmannibucau avatar Feb 24 '23 21:02 rmannibucau

up, is it something which could happen? While jib-core is used workarounds are quite easy but while using jib in a maven release it is really less trivial to workaround the process (and i have a case i can't deploy images after the jar release so I must do it all at once).

rmannibucau avatar Mar 10 '23 14:03 rmannibucau

@mpeddada1 if it helps I put a draft at https://github.com/GoogleContainerTools/jib/pull/3954

rmannibucau avatar Mar 10 '23 15:03 rmannibucau

up?

rmannibucau avatar Jul 10 '23 11:07 rmannibucau

I already opened an issue ticket to handle 502 errors too https://github.com/GoogleContainerTools/jib/issues/4266

fahedouch avatar Jul 16 '24 13:07 fahedouch