Jenkins winstone-3.2 (embedded Jetty 9) integration into master (ref: JENKINS-33412)

[elijah....@joyent.com]

I work for a public cloud provider (Joyent) and a number of our customers have stumbled into a Jenkins issue when running in a containerized environment or on a large server: https://issues.jenkins-ci.org/browse/JENKINS-33412

This issue could be easily fixed by using the latest version of the winstone component (https://github.com/jenkinsci/winstone/) with the next Jenkins release. How viable is that? Is there anything we at Joyent could do to help facilitate this?

In the meantime, I will recommend that our users set up their own reverse proxy for using HTTPS with Jenkins.

Thanks in advance,

Elijah Zupancic

[Daniel Beck]

Seems straightforward.

https://github.com/jenkinsci/jenkins/pull/2108

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4abf0cae-7b99-4ccb-ae2d-e7536c28c221%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.