Re: jenkins.impala.io switching to SSL
Hi All, I completed the Jenkins reconfiguration that I announced last night. Jenkins can now be reached at https://jenkins.impala.io and all previous URLs redirect there permanently. From now on it will post https:// links in code reviews. Links posted in old code reviews should still work. I found two jobs that were aborted by the restart and I kicked off new build for those. If one of your jobs got killed, please make sure to restart them, too. Unless we discover any issues with the new configuration there should be no more interruptions. Thank you for your patience. Cheers, Lars On Tue, Jul 18, 2017 at 1:43 PM, Lars Volkerwrote: > Hi All, > > Jenkins has been running with SSL for the past few days and I haven't > received any complaints. If no-one objects, tomorrow morning (Wednesday, > PST) I will configure http://jenkins.impala.io:8080/ to redirect to > https://jenkins.impala.io. From that point on, Jenkins will also post > links to its https endpoint in code reviews. > > Let me know if you have any questions or concerns. > > Cheers, Lars > > On Fri, Jul 14, 2017 at 10:55 PM, Lars Volker wrote: > >> Hi All, >> >> our Jenkins instance now has a proper SSL certificate and can be reached >> at https://jenkins.impala.io. The old redirect from http://j.i.o now >> points to the SSL endpoint instead of port 8080. >> >> If you run into any issues with the SSL setup, please let me know. As a >> workaround you can still access Jenkins directly at >> http://jenkins.impala.io:8080/. If no-one reports any issues in the next >> few days, I will eventually make that URL redirect to SSL, too, so all >> connections will be secured. >> >> Cheers, Lars >> > >
Re: jenkins.impala.io switching to SSL
Thanks for taking care of this Lars! On Tue, Jul 18, 2017 at 1:43 PM, Lars Volkerwrote: > Hi All, > > Jenkins has been running with SSL for the past few days and I haven't > received any complaints. If no-one objects, tomorrow morning (Wednesday, > PST) I will configure http://jenkins.impala.io:8080/ to redirect to > https://jenkins.impala.io. From that point on, Jenkins will also post > links > to its https endpoint in code reviews. > > Let me know if you have any questions or concerns. > > Cheers, Lars > > On Fri, Jul 14, 2017 at 10:55 PM, Lars Volker wrote: > > > Hi All, > > > > our Jenkins instance now has a proper SSL certificate and can be reached > > at https://jenkins.impala.io. The old redirect from http://j.i.o now > > points to the SSL endpoint instead of port 8080. > > > > If you run into any issues with the SSL setup, please let me know. As a > > workaround you can still access Jenkins directly at > > http://jenkins.impala.io:8080/. If no-one reports any issues in the next > > few days, I will eventually make that URL redirect to SSL, too, so all > > connections will be secured. > > > > Cheers, Lars > > >
Re: jenkins.impala.io switching to SSL
Hi All, Jenkins has been running with SSL for the past few days and I haven't received any complaints. If no-one objects, tomorrow morning (Wednesday, PST) I will configure http://jenkins.impala.io:8080/ to redirect to https://jenkins.impala.io. From that point on, Jenkins will also post links to its https endpoint in code reviews. Let me know if you have any questions or concerns. Cheers, Lars On Fri, Jul 14, 2017 at 10:55 PM, Lars Volkerwrote: > Hi All, > > our Jenkins instance now has a proper SSL certificate and can be reached > at https://jenkins.impala.io. The old redirect from http://j.i.o now > points to the SSL endpoint instead of port 8080. > > If you run into any issues with the SSL setup, please let me know. As a > workaround you can still access Jenkins directly at > http://jenkins.impala.io:8080/. If no-one reports any issues in the next > few days, I will eventually make that URL redirect to SSL, too, so all > connections will be secured. > > Cheers, Lars >
jenkins.impala.io switching to SSL
Hi All, our Jenkins instance now has a proper SSL certificate and can be reached at https://jenkins.impala.io. The old redirect from http://j.i.o now points to the SSL endpoint instead of port 8080. If you run into any issues with the SSL setup, please let me know. As a workaround you can still access Jenkins directly at http://jenkins.impala.io:8080/. If no-one reports any issues in the next few days, I will eventually make that URL redirect to SSL, too, so all connections will be secured. Cheers, Lars