(replies inline) On Tue, 10 May 2016, Daniel Beck wrote:
> > > On 10.05.2016, at 12:23, Mladen Marev <[email protected]> wrote: > > > > my proxy and firewall allows download of Java content (e.g. Jenkins war > > file) only from HTTPS protected sites. I have tried manual download of v2.2 > > but it has been rejected because HTTP connection. > > I'm pretty sure we are currently unable to provide full HTTPS for Jenkins and > plugin downloads. Even for metadata it's difficult, see e.g. > https://issues.jenkins-ci.org/browse/INFRA-110?focusedCommentId=210433&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-210433 Moving to end-to-end TLS encryption for the Jenkins distribution site is something that is part of an infrastructure project I'm working towards right now. I don't have many details I can share right now, but my hope is that we have TLS distribution before the end of the calendar year. - R. Tyler Croy ------------------------------------------------------ Code: <https://github.com/rtyler> Chatter: <https://twitter.com/agentdero> % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F ------------------------------------------------------ -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160510150102.GK30995%40blackberry.coupleofllamas.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
