Re: Jenkins possibly compromised

2019-05-16 Thread Marco de Abreu
Hey again,

the webhook has successfully been re-activated and thus all PRs should be
processed again. As part of the process, we had to retrigger all jobs which
will re-evaluate all PRs and make a huge queue on our side. Autoscaling
will kick in and try to chew through all jobs, but it will take a few hours
none the less to process the queue. In a few hours, everything should have
normalized and we will check back to make sure we're running fine. Until
then, we are asking for you to be patient and would to excuse caused
inconveniences.

Best regards,
Marco

On Thu, May 16, 2019 at 3:15 PM Marco de Abreu 
wrote:

> Hello dev@,
>
> we noticed some fishy logs on our Jenkins and are afraid that a successful
> attack might have happened. Thus, we are taking security precautions and
> rotating all credentials and revoking active session.
>
> As part of this process, we have to rotate the GitHub webhook secret. This
> update requires communication with Apache Infra, which will render Jenkins
> unusable for PR verification until the secret has been updated on Apache
> Infras side.
>
> Please excuse any inconveniences this may have caused.
>
> Best regards,
> Marco
>


Jenkins possibly compromised

2019-05-16 Thread Marco de Abreu
Hello dev@,

we noticed some fishy logs on our Jenkins and are afraid that a successful
attack might have happened. Thus, we are taking security precautions and
rotating all credentials and revoking active session.

As part of this process, we have to rotate the GitHub webhook secret. This
update requires communication with Apache Infra, which will render Jenkins
unusable for PR verification until the secret has been updated on Apache
Infras side.

Please excuse any inconveniences this may have caused.

Best regards,
Marco