-
Bug
-
Resolution: Unresolved
-
Minor
-
Jenkins 1.596.2, Artifactory 4.0.2, JDK 1.6, Artifactory plugin 4.0.2
We are currently running Jenkins 1.596.2 on Linux and have recently upgraded Artifactory to 4.0.2 on our Windows test environment. We make use of the Artifactory plugin (2.3.0) to deploy artifacts and the build info to Artifactory.
As part of our testing we have found that if we have a build running 1.6 JDK it fails during the downloading and deploying of Artifacts to Artifactory with the following error.
pool-2-thread-1, WRITE: TLSv1 Handshake, length = 75
pool-2-thread-1, WRITE: SSLv2 client hello message, length = 101
pool-2-thread-1, READ: Unknown-3.3 Alert, length = 2
pool-2-thread-1, RECV TLSv1 ALERT: fatal, handshake_failure
pool-2-thread-1, called closeSocket()
pool-2-thread-1, handling exception: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
pool-2-thread-1, IOException in getSession(): javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
It seems this issue could be caused by the new version of Artifactory (possibly Tomcat 4,0?) not accepting connections via SSLv2? There doesn't seem to be much information about it though?
I've got round one part of the issue to an extent by specifying '-Dhttps.protocols=TLSv1' and this now means maven is able to pull down requests but it still fails on the 'build info' step with 'peer not authenticated errors'.
[ERROR] Internal error: java.lang.RuntimeException: org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded() listener has failed: Error occurred while publishing artifact to Artifactory: /data/jenkins/jobs/application-develop/workspace/target/application-develop-SNAPSHOT-javadoc.jar.
[ERROR] Skipping deployment of remaining artifacts (if any) and build info. peer not authenticated
[ERROR] -> [Help 1]
I've checked the cacerts file and all looks to be correct and the whole process was working before the upgrade. I've upgraded the Artifactory plugin to the latest version but still get errors.
I don't want to upgrade Jenkins on our test environment without knowing that doing so might fix this issue.
Many Thanks.