[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title Arnaud Héritier closed an issue as Fixed Fixed in 2.15 Jenkins / JENKINS-38738 Maven plugin does not use SNI with SSL maven repos Change By: Arnaud Héritier Status: Open Closed Assignee: Arnaud Héritier Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title Stefano Travelli commented on JENKINS-38738 Re: Maven plugin does not use SNI with SSL maven repos You are right. It was a pure maven issue. Upgrading Maven to 3.2.1 and forcing maven-relase-plugin to version 2.5.3 it works. Thank you. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title Arnaud Héritier commented on JENKINS-38738 Re: Maven plugin does not use SNI with SSL maven repos If for SNAPSHOTs you are using the post build step provided by Jenkins then it could explain the difference and thus if parsing POM + SNAPSHOTs deployment are working with you repo using SNI this issue but also JENKINS-40903 could be fixed JENKINS-26403 is different because I think that this is the artifactory plugin which is doing the deployment from jenkins. In your case you are asking to maven to do the deployment with the deploy goal and this is where we have the issue and it should be a pure maven issue Maybe you could try to run your release build with -e or -X (or just a deploy with maven, it should be the same). It may help you to see which wagon provider/version you are using and adapt your maven configuration to use the right one. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title stefanotravelli commented on JENKINS-38738 Re: Maven plugin does not use SNI with SSL maven repos Yes, it's the same server and I'm using the post build step provided by Jenkins. With regard to the scope of this ticket I think it's fixed. My issue seems more like JENKINS-26403 (even if I'm not using the Artifactory plugin). Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title Arnaud Héritier commented on JENKINS-38738 Re: Maven plugin does not use SNI with SSL maven repos ok thus here it's at jenkins level. Parsing POM step succeed to get artifacts (which was the error reported in this ticket) It is strange that you have this deployment issue only with releases and not with snapshots (they are uploaded to the same server ?). I'm not sure if Jenkins can be involve in the issue, did you try to reproduce the issue without jenkins ? When you are deploying your snapshots you are also using maven to do it or you are using the post build step provided by jenkins in maven jobs ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title stefanotravelli commented on JENKINS-38738 Re: Maven plugin does not use SNI with SSL maven repos Previous error was misleading because JDK did'n recognize a LetsEncrypt Certificate. With JDK 1.0.8_112 I get: [INFO] [INFO] [INFO] [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ eui-login --- [INFO] [INFO] Uploading: https://www.entaksi.eu/maven/maintenact-release-local/eu/entaksi/eui/eui-login/1.0.4/eui-login-1.0.4.amp [INFO] [INFO] Uploading: https://www.entaksi.eu/maven/maintenact-release-local/eu/entaksi/eui/eui-login/1.0.4/eui-login-1.0.4.pom [INFO] [INFO] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] [INFO] [INFO] Total time: 4.035 s [INFO] [INFO] Finished at: 2017-02-17T14:32:24+01:00 [INFO] [INFO] Final Memory: 31M/640M [INFO] [INFO] [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project eui-login: Failed to deploy artifacts: Could not transfer artifact eu.entaksi.eui:eui-login:amp:1.0.4 from/to maintenact-release (https://www.entaksi.eu/maven/maintenact-release-local): hostname in certificate didn't match: != OR -> [Help 1] [INFO] [ERROR] [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [INFO] [ERROR] [INFO] [ERROR] For more information about the errors and possible solutions, please read the following articles: [INFO] [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException This happens only during a maven release. Regular builds that include uploading snapshots to the repository works fine. As a workaround I set an entry in the hosts file in order to point to a dedicated HTTP server with a single certificate. Add Comment
[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title Arnaud Héritier commented on JENKINS-38738 Re: Maven plugin does not use SNI with SSL maven repos Do you have the full stacktrace please ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title
stefanotravelli edited a comment on JENKINS-38738
Re: Maven plugin does not use SNI with SSL maven repos
No luck here with newer version 2.15.1 and nginx TLS/SNI :(Not sure that the error is the same, though:{{ sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title
stefanotravelli commented on JENKINS-38738
Re: Maven plugin does not use SNI with SSL maven repos
No luck here with newer version 2.15.1 and nginx TLS/SNI Not sure that the error is the same, though: {{sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target }}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title Arnaud Héritier commented on JENKINS-38738 Re: Maven plugin does not use SNI with SSL maven repos FYI 2.15.1 is out Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title Arnaud Héritier commented on JENKINS-38738 Re: Maven plugin does not use SNI with SSL maven repos version 2.15 will upgrade wagon to the latest version. Let us know if it fixes this issue. Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38738) Maven plugin does not use SNI with SSL maven repos
Title: Message Title Ciprian Ciubotariu created an issue Jenkins / JENKINS-38738 Maven plugin does not use SNI with SSL maven repos Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2016/Oct/05 2:18 PM Environment: Jenkins 2.7.2 Maven Integration plugin 2.13 Labels: plugins plugin build Priority: Major Reporter: Ciprian Ciubotariu I have an Apache Archiva instance running behind HAProxy. HAProxy acts as a SSL wrapper for more HTTP services, each identified via its DNS name, and each with its own certificate. This setup requires clients to use SNI within the TLS handshake, so HAProxy can send back the proper SSL certificate. This works already for command-line maven builds on my machine. Also curl, firefox and even apache karaf are able to seamlessly communicate with my archiva repo via HTTPS. The jenkins maven plugin seems to not send SNI during handshake, and I infer this from the fact that HAProxy replies with the wrong SSL certificate (the one for the website www.example.com/example com, instead of archiva.example.org) , as presented in the log below. Parsing POMs Failed to transfer Could not transfer artifact org.example:example-parent:pom:4 from/to example-releases (https://archiva.example.org/repository/example-releases): hostname in certificate didn't match: != OR OR Failed to transfer Could not find artifact org.example:example-parent:pom:4 in
