Scheduled maintenance notice: 2016-02-17 05:00 UTC

[R. Tyler Croy]

I will be rolling some reboots through the Jenkins infrastructure this evening
(PST) in order to address CVE-2015-7547 / USN-2900-1
(http://www.ubuntu.com/usn/usn-2900-1/). Our internal ticket tracking this can
be found here: https://issues.jenkins-ci.org/browse/INFRA-566

I expect the impact to be minimal, but services will be temporarily taken
offline while hosts are rebooting. An all-clear notice will be sent after
maintenance has been completed.


If you have any questions, feel free to ask.



Cheers
- R. Tyler Croy

------------------------------------------------------
Code: <https://github.com/rtyler>
Chatter: <https://twitter.com/agentdero>

% gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
------------------------------------------------------

[niristotle okram]

Does this include the update center site as well? 

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20160216233737.GV17392%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.

--
Sent from mobile device, excuse typos if any.

[R. Tyler Croy]

(replies inline)

On Tue, 16 Feb 2016, niristotle okram wrote:

> Does this include the update center site as well?

Yes, consider everything hosted under jenkins-ci.org to be subject to this
maintenance notice (not everything will be affected but might as well include
it)

> On Tuesday, February 16, 2016, R. Tyler Croy <ty...@monkeypox.org> wrote:
>
> >
> > I will be rolling some reboots through the Jenkins infrastructure this
> > evening
> > (PST) in order to address CVE-2015-7547 / USN-2900-1
> > (http://www.ubuntu.com/usn/usn-2900-1/). Our internal ticket tracking
> > this can
> > be found here: https://issues.jenkins-ci.org/browse/INFRA-566
> >
> > I expect the impact to be minimal, but services will be temporarily taken
> > offline while hosts are rebooting. An all-clear notice will be sent after
> > maintenance has been completed.
> >
> >
> > If you have any questions, feel free to ask.
> >
> >
> >
> > Cheers
> > - R. Tyler Croy
> >
> > ------------------------------------------------------
> > Code: <https://github.com/rtyler>
> > Chatter: <https://twitter.com/agentdero>
> >
> > % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
> > ------------------------------------------------------
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Jenkins Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an

> > email to jenkinsci-use...@googlegroups.com <javascript:;>.

> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/jenkinsci-users/20160216233737.GV17392%40blackberry.coupleofllamas.com
> > .
> > For more options, visit https://groups.google.com/d/optout.
> >
>
>
> --
> Sent from mobile device, excuse typos if any.
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPzcO4g0%2BveSZqm2ksmBXWVu4oka6gAvs0ECq5JsW09sxPFMKw%40mail.gmail.com.

> For more options, visit https://groups.google.com/d/optout.

[R. Tyler Croy]

(replies inline)

On Tue, 16 Feb 2016, R. Tyler Croy wrote:

>
> I will be rolling some reboots through the Jenkins infrastructure this evening
> (PST) in order to address CVE-2015-7547 / USN-2900-1
> (http://www.ubuntu.com/usn/usn-2900-1/). Our internal ticket tracking this can
> be found here: https://issues.jenkins-ci.org/browse/INFRA-566

This work has been completed and to the best of my knowledge (and our
monitoring) everything looks to be back online and working properly. The full
window of time used was about 60 minutes but that only manifested itself in
about 5-10 minutes of service downtime.