extended jenkins downtime monday, march 16th, plus some hints at the future

[shane knapp <sk...@berkeley.edu>]

i'll be taking jenkins down for some much-needed plugin updates, as well as
potentially upgrading jenkins itself.

this will start at 730am PDT, and i'm hoping to have everything up by noon.

the move to the anaconda python will take place in the next couple of weeks
as i'm in the process of rebuilding my staging environment (much needed) to
better reflect production, and allow me to better test the change.

and finally, some teasers for what's coming up in the next month or so:

* move to a fully puppetized environment (yay no more shell script
deployments!)
* virtualized workers (including multiple OSes -- OS X, ubuntu, ...,
profit?)

more details as they come.

happy friday!

shane

Re: extended jenkins downtime monday, march 16th, plus some hints at the future

[shane knapp <sk...@berkeley.edu>]

ok, we're back up and building.  upgrading the github plugin (and possibly
EnvInject) caused the stacktraces, so i've kept those at the old versions
that were working before.  jenkins and the rest of the plugins are updated
and we're g2g.

i'll be, of course, keeping an eye on things today and will squash anything
else that pops up.

On Mon, Mar 16, 2015 at 9:06 AM, shane knapp <sk...@berkeley.edu> wrote:

> looks like we're having some issues w/the pull request builder and cron
> stacktraces in the logs.  i'll be investigating further and will update
> when i figure out what's going on.
>
> On Mon, Mar 16, 2015 at 7:51 AM, shane knapp <sk...@berkeley.edu> wrote:
>
>> this is starting now.
>>
>> On Fri, Mar 13, 2015 at 10:12 AM, shane knapp <sk...@berkeley.edu>
>> wrote:
>>
>>> i'll be taking jenkins down for some much-needed plugin updates, as well
>>> as potentially upgrading jenkins itself.
>>>
>>> this will start at 730am PDT, and i'm hoping to have everything up by
>>> noon.
>>>
>>> the move to the anaconda python will take place in the next couple of
>>> weeks as i'm in the process of rebuilding my staging environment (much
>>> needed) to better reflect production, and allow me to better test the
>>> change.
>>>
>>> and finally, some teasers for what's coming up in the next month or so:
>>>
>>> * move to a fully puppetized environment (yay no more shell script
>>> deployments!)
>>> * virtualized workers (including multiple OSes -- OS X, ubuntu, ...,
>>> profit?)
>>>
>>> more details as they come.
>>>
>>> happy friday!
>>>
>>> shane
>>>
>>
>>
>

Re: extended jenkins downtime monday, march 16th, plus some hints at the future

[shane knapp <sk...@berkeley.edu>]

looks like we're having some issues w/the pull request builder and cron
stacktraces in the logs.  i'll be investigating further and will update
when i figure out what's going on.

On Mon, Mar 16, 2015 at 7:51 AM, shane knapp <sk...@berkeley.edu> wrote:

> this is starting now.
>
> On Fri, Mar 13, 2015 at 10:12 AM, shane knapp <sk...@berkeley.edu> wrote:
>
>> i'll be taking jenkins down for some much-needed plugin updates, as well
>> as potentially upgrading jenkins itself.
>>
>> this will start at 730am PDT, and i'm hoping to have everything up by
>> noon.
>>
>> the move to the anaconda python will take place in the next couple of
>> weeks as i'm in the process of rebuilding my staging environment (much
>> needed) to better reflect production, and allow me to better test the
>> change.
>>
>> and finally, some teasers for what's coming up in the next month or so:
>>
>> * move to a fully puppetized environment (yay no more shell script
>> deployments!)
>> * virtualized workers (including multiple OSes -- OS X, ubuntu, ...,
>> profit?)
>>
>> more details as they come.
>>
>> happy friday!
>>
>> shane
>>
>
>

Re: extended jenkins downtime monday, march 16th, plus some hints at the future

[shane knapp <sk...@berkeley.edu>]

this is starting now.

On Fri, Mar 13, 2015 at 10:12 AM, shane knapp <sk...@berkeley.edu> wrote:

> i'll be taking jenkins down for some much-needed plugin updates, as well
> as potentially upgrading jenkins itself.
>
> this will start at 730am PDT, and i'm hoping to have everything up by noon.
>
> the move to the anaconda python will take place in the next couple of
> weeks as i'm in the process of rebuilding my staging environment (much
> needed) to better reflect production, and allow me to better test the
> change.
>
> and finally, some teasers for what's coming up in the next month or so:
>
> * move to a fully puppetized environment (yay no more shell script
> deployments!)
> * virtualized workers (including multiple OSes -- OS X, ubuntu, ...,
> profit?)
>
> more details as they come.
>
> happy friday!
>
> shane
>