FTR

Jenkins is now at 2.3.2

It looks as though 2.3.1 and later now require Java 7:

https://jenkins.io/doc/upgrade-guide/2.32/#upgrading-to-jenkins-lts-2-32-1


On 22 February 2017 at 11:11, sebb <seb...@gmail.com> wrote:
> The point is that others may be watching builds@ but not see the JIRA issues.
> Hence the 'FTR' prefix.
>
> On 22 February 2017 at 10:54, Greg Stein <gst...@gmail.com> wrote:
>> What is your point? ... Gavin said, "or file an INFRA ticket" ... that is
>> what happened.
>>
>> On Wed, Feb 22, 2017 at 4:37 AM, sebb <seb...@gmail.com> wrote:
>>>
>>> FTR:
>>> At least one build using Java 1.6 stopped working; see INFRA-13556
>>>
>>> On 19 February 2017 at 03:04, Gavin McDonald <ga...@16degrees.com.au>
>>> wrote:
>>> > Hi Again,
>>> >
>>> > Jenkins has been upgraded to latest 2.32.2, all plugins have been
>>> > upgraded, Tomcat was also upgraded to latest 7.0.75 release.
>>> >
>>> > Downtime was a little over 2.5 hours due to the unplanned Tomcat upgrade
>>> > and having so many plugins that needed individual
>>> > upgrading.
>>> >
>>> > Some config tweaks were also made and so far, logs are looking much
>>> > cleaner.
>>> >
>>> > Any issues please report to builds@apache.org list, or file an INFRA
>>> > ticket.
>>> >
>>> > Thanks
>>> >
>>> > Gav…
>>> >
>>> >
>>> >> On 14 Feb 2017, at 7:30 pm, Gavin McDonald <ga...@16degrees.com.au>
>>> >> wrote:
>>> >>
>>> >> Hi All,
>>> >>
>>> >> Our main Jenkins instance at builds.apache.org will be going down for
>>> >> an upgrade this Saturday/Sunday.
>>> >>
>>> >> Downtime will start at 0000 UTC (Sunday) : 1100 AEDT (Sunday): 1900 EST
>>> >> (Saturday)
>>> >>
>>> >> Should be less than an hour, however there will be quite a few plugin
>>> >> updates so more restarts may be required.
>>> >>
>>> >> Will tweet @infrabot 1 hour before and again when complete.
>>> >>
>>> >> Thanks
>>> >>
>>> >> Gav...
>>> >>
>>> >
>>
>>

Reply via email to