Just a heads-up that the auto website publishing on the CI server was flakey last week - I spoke to a couple of you directly about it - but just to raise awareness I'll repeat here.
It started failing a couple of days before I did the last release and without intervention (as far as I know) is fixed now. I presume it was some spurious networking error but if anyone notices anything strange, please report your observations. I also added some adhoc steps into the release script in the groovy/groovy-release repo to allow the website to be published from outside the CI if needed (credentials to the CI box are still required). There is more work to be done around credentials at some point but that is the subject of another email. I have recorded just a few notes below in case it re-surfaces. Cheers, Paul. ------------------------------------------- The error message was: Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target ... groovy.json.JsonException: Unable to process url: https://issues.apache.org/jira/rest/api/2/project/GROOVY/versions ... :site:generateSite This is typically what happens when accessing a site with a self-signed certificate. But looking at the certificates manually and from several other boxes, I don't believe that was the issue here. It also worked fine from IcedTea JDK on the CI box but not using Oracle JDK7/8. I suspect some kind of spurious networking error whereby some hostname somewhere up the certification path isn't being found by dns - possibly the incorrect IP address in some DNS cache.
