OK, ended up being more like an hour, but I think things are up and running. It's churning through a queue (Mike uploaded a big patch bomb).
*Please note*: the IP address changed after the upgrade, since I recreated the VM it's running on and couldn't figure out how to keep its IP. However, this time around I assigned a static IP and also got a DNS name assigned from ASF Infra: http://jenkins.kudu.apache.org/ So, if you're looking for test results from a prior submitted patch, use the above hostname instead of the old IP, and your results should still be there (it's the same disk as before, just a new address) -Todd On Thu, Jun 15, 2017 at 10:28 AM, Todd Lipcon <[email protected]> wrote: > It seems our Jenkins is vulnerable to some remote exploits. I'm going to > be upgrading it to a newer version in a few minutes, which will cause some > downtime. If you have unexpected precommit failures, please be patient. > I'll send an all-clear when it's back up and working so you can retrigger. > > -Todd > > -- > Todd Lipcon > Software Engineer, Cloudera > -- Todd Lipcon Software Engineer, Cloudera
