You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The method isRetryableErrorCode can be removed from my point of view.
If an upload did not work, the plugin should not care why it did not work and make a retry. The restriction to HTTP Error 500 restricts the retry mechanism too much.
Info
docker-maven-plugin version : 0.38.1
Maven version (mvn -v) : 3.6.3
If it's a bug, how to reproduce : none
If it's a feature request, what is your use case :
-- during a release we send many artifacts to azure docker registry
-- the azure is sometimes not reachable because I/O error, DNS error and so on
-- then the release breaks and we have to repeat it
Sample project : [GitHub Clone URL]
none
The text was updated successfully, but these errors were encountered:
Feature Request Description
Currently the retry mechanism covers only a 500 error. See
docker-maven-plugin/src/main/java/io/fabric8/maven/docker/access/hc/DockerAccessWithHcClient.java
Line 764 in 3f55e01
The method isRetryableErrorCode can be removed from my point of view.
If an upload did not work, the plugin should not care why it did not work and make a retry. The restriction to HTTP Error 500 restricts the retry mechanism too much.
Info
docker-maven-plugin version : 0.38.1
Maven version (
mvn -v
) : 3.6.3If it's a bug, how to reproduce : none
If it's a feature request, what is your use case :
-- during a release we send many artifacts to azure docker registry
-- the azure is sometimes not reachable because I/O error, DNS error and so on
-- then the release breaks and we have to repeat it
Sample project : [GitHub Clone URL]
none
The text was updated successfully, but these errors were encountered: