Closed steven1046 closed 3 years ago
This could be related to https://github.com/travis-ci/travis-ci/issues/10053, where some Travis IP addresses may have been blocked by Maven.
We probably need to set a Maven repository username and password in the Maven wrapper properties: https://github.com/takari/maven-wrapper#using-basic-authentication-for-distribution-download
I have been seeing the same thing lately. Without doing too much digging, I suspect this started end of December (20th) when Travis added some new IPs. They probably need to be white listed by Maven / Sonatype.
2 possible solutions: -Do not use the wrapper for the travis builds -Do not download the same binary for every build
Also, make sure for ibm cloud sites we also do not download the binary for every build.
Closing this until we start using Travis again.
Ever since added a Maven wrapper to specify the version of Maven, the Travis builds will fail sometimes but not always. We haven't had this error in the IBM Cloud, just in Travis. This occurs in both the draft build and the QA build but not every time. Kicking off another build usually works.
Error: