Hmmm, never mind. I literally just checked again after posting my question here, and now it works :-) Must have been a caching issue of some kind.
We could easily reproduce the issue over the last few days. Now it works, and consistently. Sebastian On Friday, June 17, 2016 at 4:31:42 PM UTC+2, Sebastian Gooren wrote: > > Hi all, > > We recently switched our build infrastructure to SSL, and are seeing > issues with our maven builds. > We run jenkins at https://jenkins.domain.com and Nexus at > https://nexus.domain.com > > To offload SSL, we run both apps behind a reverse proxy (apache 2.4.6 on > centos 7). > If we put the jenkins virtualhost before the nexus virtualhost, the maven > job complains that it cannot reach nexus, as the SSL certificate name > doesn't match. > > Jenkins is at version 2.9; > Java (on the jenkins server) is 1.8.0_92 > Java (as jenkins tool) is 1.8.0_92 > Maven (as jenkins tool) is 3.3.9 > > Testing this from the command line with maven 3.3.9, there is no problem. > It only breaks when we run our maven jobs in jenkins. > Our quick fix is to put the nexus vhost before the jenkins one, but that's > not really a proper solution. > > Any ideas as to the cause of this problem and how to debug it? I've > already tried running maven with "-X", but don't get any additional output > that is useful. > I can't figure out why this is not working - all versions (java, maven) > should support SNI out of the box. > > Thank you for reading and any help you provide :-) > > Kind regards, > > Sebastian > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6ee52fba-d83f-4e7d-8799-86c6ccff450b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
