On 2025-01-20, Mark Thomas wrote: > All,
> The Gump builds have been unreliable since moving to new hardware and > I am trying to work out why. > A typical error is this one for commons-compress. > The build fails with: > ... > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 01:16 min > [INFO] Finished at: 2025-01-20T08:23:41Z > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-site-plugin:3.21.0:attach-descriptor > (attach-descriptor) on project commons-compress: Execution > attach-descriptor of goal > org.apache.maven.plugins:maven-site-plugin:3.21.0:attach-descriptor > failed: Plugin org.apache.maven.plugins:maven-site-plugin:3.21.0 or > one of its dependencies could not be resolved: Could not transfer > artifact org.apache.maven.wagon:wagon-ssh:jar:3.5.3 from/to > gump-central (http://localhost:8192/maven2): Transfer failed for > http://localhost:8192/maven2/org/apache/maven/wagon/wagon-ssh/3.5.3/wagon-ssh-3.5.3.jar: > ClientProtocolException: Status line contains invalid status code: > HTTP/1.1 :01 :01 -> [Help 1] > [ERROR] ... > If I ssh to vmgump while that run is still running and try downloading > http://localhost:8192/maven2/org/apache/maven/wagon/wagon-ssh/3.5.3/wagon-ssh-3.5.3.jar > with wget it works. > Any suggestions on how to either debug or fix the issue (keeping in > mind I know next to no python)? I don't think there is any Python involved at all. The "thing" listening to Port 8192 is https://svn.apache.org/viewvc/gump/mvnrepo/tags/0.7/ - Java and something between this MITM Proxy in front of Maven central and Maven seems to be going bad. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
