Re: An Update on Jenkins

2017-04-27 Thread Davor Bonaci
As far as we know, Jenkins functionality is fully restored. Happy testing! On Wed, Apr 26, 2017 at 9:47 AM, Jason Kuster < jasonkus...@google.com.invalid> wrote: > Yup, not. Update as of this morning: Infra has contacted Github support > about the throttling issue; they're hoping that support wil

Re: An Update on Jenkins

2017-04-26 Thread Jason Kuster
Yup, not. Update as of this morning: Infra has contacted Github support about the throttling issue; they're hoping that support will be able to point to the issue. They are continuing to see rolling problems as the result of some certificate upgrades they performed over the weekend. In terms of th

Re: An Update on Jenkins

2017-04-26 Thread Dan Halperin
> If not, feel free to reply to this thread ... not. :) :( On Tue, Apr 25, 2017 at 9:58 PM, Jean-Baptiste Onofré wrote: > Thanks for the update ! > > Regards > JB > > On Apr 26, 2017, 05:51, at 05:51, Jason Kuster > > wrote: > >Hey folks, > > > >There have been a couple of different issues ov

Re: An Update on Jenkins

2017-04-25 Thread Jean-Baptiste Onofré
Thanks for the update ! Regards JB On Apr 26, 2017, 05:51, at 05:51, Jason Kuster wrote: >Hey folks, > >There have been a couple of different issues over the last couple of >days >related to some necessary updates Infra has been working on. We've >tracked >down the last couple of issues, and th

Re: An Update on Jenkins

2017-04-25 Thread Aviem Zur
Thanks for the update, Jason! On Wed, Apr 26, 2017 at 6:51 AM Jason Kuster wrote: > Hey folks, > > There have been a couple of different issues over the last couple of days > related to some necessary updates Infra has been working on. We've tracked > down the last couple of issues, and the late

An Update on Jenkins

2017-04-25 Thread Jason Kuster
Hey folks, There have been a couple of different issues over the last couple of days related to some necessary updates Infra has been working on. We've tracked down the last couple of issues, and the latest one seems to be that we're being hit by the rate limiter as a result of everything starting