On 27.10.2015, at 15:46, Per Arnold Blaasmo <[email protected]> wrote:
> That worked, but do I really want to do that? As a temporary workaround, possibly. Alternatively you could just wait until it's fixed. > It never was a problem before, why now? Apparently the fix for JENKINS-31089 resulted in the old cert being automatically revoked. > Shouldn't jenkins-ci.org fix it's certificate? Nope, we're perfectly happy with this solution as is. Seriously though, that's why I'm calling this a 'known issue', and disabling OCSP a workaround, and not a solution. The timing with JavaOne right now[1] just isn't great for getting this fixed really quickly. 1: https://www.oracle.com/javaone/index.html -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/D9A03A8B-41C4-4713-A2A1-50631370A4CE%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
