In a Bitbucket Pipeline build, I have a maven step which downloads a dependency from an SSH Maven respository operated by me.
The dependency is downloaded via scp.
When Maven tries to download it (via wagon ssh), it remains stuck.
I have added a test script as a step which just download via scp the pom.xml in order to check for autenthication problems and alike, but it is working fine (it connects, and download the pom.xml w/o errors).
Any hint about debugging it?
By using:
- export MAVEN_OPTS="$MAVEN_OPTS -Djavax.net.debug=ssl"
I spotted an exception in some TLS code which suggested me that it had to be a wagon version issue.
And indeed upgrading the wagon extension to 3.3.4 solved the problem.
Hi Piercarlo,
Sadly I don't know to help you with your SSH problem but...
Why don't just configure your private maven repository using a custom settings.xml as desribed on Java with Bitbucket Pipelines page and let the maven downloads the depencency in the same way they download maven central dependencies and get rid of ssh at all?
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.