Brian de Alwis
Brian de Alwis
@MSPigl you should be able to run something like: ``` (eval $(minikube docker-env); skaffold build ...) ```
Still [being seen](https://api.travis-ci.com/v3/job/473945864/log.txt), so setting the connection TTL isn't sufficient. ``` [builder] [ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:2.0.5.RELEASE:repackage (default) on project hello-spring-boot: Execution default of goal org.springframework.boot:spring-boot-maven-plugin:2.0.5.RELEASE:repackage failed: Plugin org.springframework.boot:spring-boot-maven-plugin:2.0.5.RELEASE...
[Maven Wagon HTTP defaults](https://github.com/apache/maven-wagon/blob/master/wagon-providers/wagon-http-shared/src/main/java/org/apache/maven/wagon/shared/http/AbstractHttpClientWagon.java): - `maven.wagon.http.retryHandler.class` = `standard` - `maven.wagon.http.retryHandler.requestSentEnabled` = `false` - `maven.wagon.http.retryHandler.count` = 3 The default retry handler (`DefaultHttpRequestRetryHandler`) defaults to [not retrying the following classes](https://hc.apache.org/httpcomponents-client-4.5.x/httpclient/apidocs/org/apache/http/impl/client/DefaultHttpRequestRetryHandler.html#DefaultHttpRequestRetryHandler(int,%20boolean)): `InterruptedIOException`, `UnknownHostException`,...
Placing the following into `/.mvn/jvm.config`, and ensuring you're using Maven ≥ 3.6.1 (which [has fixes for retry behaviour](https://issues.apache.org/jira/browse/WAGON-526)), seems to do the trick: ``` -Dmaven.wagon.httpconnectionManager.ttlSeconds=120 -Dmaven.wagon.http.retryHandler.requestSentEnabled=true ``` This changes the...
Still happening in the buildpacks tests ([log](https://api.travis-ci.com/v3/job/474501268/log.txt) from #5279)
This behaviour is intentional @spmason, but we're looking to make this behaviour configurable.
Sounds similar to #5855.
So I'm in this situation right now with the [container-debug-support images](https://github.com/GoogleContainerTools/container-debug-support/). I currently stage images to a staging repository (`us-central1-docker.pkg.dev/k8s-skaffold/skaffold-staging/skaffold-debug-support`) as `latest`. As we automate this, I want to instead...
Yes. Hit some stumbling blocks with testing.
#6951 and #6952 are still outstanding