Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
MIME-Version: 1.0
In-Reply-To: <012e01d2f05a$17c89570$4759c050$@apache.org>
References: <573832AC-086E-40DA-9CAB-C9D316968CE2@16degrees.com.au>
 <CAMopvkOZY-94AwVnjCv6nxaudJ4UK399GUaK1qEFek_eYtuqPQ@mail.gmail.com>
 <CABD8fLVSrennFCbcer=UJWtKtx56UNdp_3Tes5n9CRHAxh=Kew@mail.gmail.com> <012e01d2f05a$17c89570$4759c050$@apache.org>
From: Lukasz Lenart <lukaszlenart@apache.org>
Date: Thu, 29 Jun 2017 08:45:13 +0200
Message-ID: <CAMopvkM11G2wRw_zBoOqEL-273RJo30W3C-TsTaCEWbqMqG46Q@mail.gmail.com>
Subject: Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
To: "builds@apache.org" <builds@apache.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 29 Jun 2017 06:45:37 -0000

Thanks Uwe, this is very helpful!

2017-06-29 0:01 GMT+02:00 Uwe Schindler <uschindler@apache.org>:
> Hi,
>
> Instead of native Maven build jobs, the easy workaround is:
>
> - Use a standard Freestyle Job
> - Check the right JDK version
> - Use the "Tool Environment" plugin and select correct Maven version, e.g=
. MAVEN_3_5_0_HOME
> - Enter the Maven execution into the shell command line and use the "Tool=
 Environment" defined env var to locate the Maven executable (e.g., "${MAVE=
N_3_5_0_HOME}/bin/mvn").
>
> We use a similar approach for our smoker tests that run with multiple JVM=
 versions (7 and 8 for Lucene 5). The second JVM version is just exported b=
y the "Tools Environment" plugin.
>
> Uwe
>
> -----
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
>> -----Original Message-----
>> From: Greg Stein [mailto:gstein@gmail.com]
>> Sent: Wednesday, June 28, 2017 9:05 PM
>> To: builds@apache.org
>> Subject: Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
>> JDK7 deprecation)
>>
>> I think it depends upon your job type, as Gavin wrote: "in terms of Mave=
n
>> jobs for JDK 7"
>>
>> On Wed, Jun 28, 2017 at 10:01 AM, Lukasz Lenart
>> <lukaszlenart@apache.org>
>> wrote:
>>
>> > Hi,
>> >
>> > How to understand that? It won't be possible to run a job using JDK7
>> > anymore, right? Even if I selected such JDK in my build, Jenkins won't
>> > run it, is that true?
>> >
>> > We cannot run this build [1] anymore as JDK6 isn't support by the
>> > slaves [2] - will it be the same?
>> >
>> > [1] https://builds.apache.org/view/S-Z/view/Struts/job/
>> > Struts-JDK6-support-2.3/
>> > [2] https://builds.apache.org/view/S-Z/view/Struts/job/
>> > Struts-JDK6-support-2.3/1064/console
>> >
>> >
>> > Regards
>> > --
>> > =C5=81ukasz
>> > + 48 606 323 122 http://www.lenart.org.pl/
>> >
>> > 2017-06-27 9:03 GMT+02:00 Gavin McDonald <gavin@16degrees.com.au>:
>> > > ASF Jenkins Master Migration and Upgrade on :-
>> > >
>> > >
>> > > Location                                                Local Time
>> >                                         Time Zone       UTC Offset
>> > > Melbourne (Australia - Victoria)        Sunday, 16 July 2017 at 10:0=
0:00
>> > am     AEST            UTC+10 hours
>> > > New York (USA - New York)               Saturday, 15 July 2017 at
>> > 8:00:00 pm    EDT                     UTC-4 hours
>> > > Corresponding UTC (GMT)         Sunday, 16 July 2017 at 00:00:00
>> > >
>> > >
>> > > Hi All,
>> > >
>> > > A few things are going to happen in just over 2 weeks.
>> > >
>> > > 1. Migration of Jenkins to a new host. A Jenkins Master module and y=
aml
>> > have been puppetized and ready to go.
>> > >     What we need to do to migrate the Master away from its current h=
ost
>> > is turn off the old service. Perform a final
>> > >     rsync of data and perform the migration tasks.
>> > >
>> > >     As we intend to preserve history for jobs this will take some ti=
me.
>> > >     At the same time as doing this migration to a new host, all slav=
e
>> > connections will be updated (see below.)
>> > >     I have no current estimate of downtime, but it will run into sev=
eral
>> > hours. We do plan to run this migration on a
>> > >     Sunday at the lowest part of Jenkins usual usage.
>> > >
>> > > 2. Upgrade of Jenkins - Jenkins project released a new LTS release,
>> > version 2.60.1. This is a major release and breaks
>> > >     Jenkins in terms of Maven jobs for JDK 7 in the same way that it
>> > happened for Maven and JDK 6 a few months back.
>> > >
>> > >     The infra team (mainly myself) got quite some feedback on not
>> > supplying advance notice of this breakage. That upgrade
>> > >     however was necessary due to security fixes that required our
>> > upgrade.  This email serves as advance warning of the
>> > >     upcoming upgrade of Jenkins, the downtime due to the migration o=
f
>> > the service to a new host; and notice of the breakage
>> > >     to JDK 7 that the upgrade brings.
>> > >
>> > >     Please familiarise yourself with the Jenkins LTS upgrade notes a=
t
>> > [1].
>> > >     In particular please note:-
>> > >
>> > >     =E2=80=9C=E2=80=A62.60.1 is the first Jenkins LTS release that r=
equires Java 8 to
>> > run. If you're using the Maven Project type, please note that it needs=
 to
>> > use a JDK capable of running Jenkins, i.e. JDK 8 or up. If you configu=
re an
>> > older JDK in a Maven Project, Jenkins will attempt to find a newer JDK=
 and
>> > use that automatically. If your SSH Slaves fail to start and you have =
the
>> > plugin install the JRE to run them, make sure to update SSH Slaves Plu=
gin
>> > to at least version 1.17 (1.20 recommended).
>> > > Changes since 2.60:
>> > > Fix for NullPointerException while initiating some SSH connections
>> > (regression in 2.59). (issue 44120 <https://issues.jenkins-ci.
>> > org/browse/JENKINS-44120>)
>> > > Notable changes since 2.46.3:
>> > > Jenkins (master and agents) now requires Java 8 to run. (issue 27624=
 <
>> > https://issues.jenkins-ci.org/browse/JENKINS-27624> <>, issue 42709 <
>> > https://issues.jenkins-ci.org/browse/JENKINS-42709> <>, pull 2802 <
>> > https://github.com/jenkinsci/jenkins/pull/2802>, announcement blog pos=
t
>> <
>> > https://jenkins.io/blog/2017/04/10/jenkins-has-upgraded-to-java-8/>)
>> > >
>> > > =E2=80=A6=E2=80=9D
>> > >
>> > > There are over 30 other enhancements/fixes since 2.46.2 which we
>> > currently run so please do take a note of those.
>> > >
>> > > Recap: In just over 2 weeks, downtime for a migration AND upgrade is
>> > planned.
>> > >
>> > > Please do not rely on Jenkins at all for that weekend if you use it =
in
>> > your release workflow.
>> > >
>> > > Please do take this notice back to your dev lists.
>> > >
>> > > Any questions or concerns please email back to builds@apache.org
>> > <mailto:builds@apache.org> only.
>> > >
>> > > Thanks
>> > >
>> > > Gav=E2=80=A6
>> > >
>> > > [1] - https://jenkins.io/changelog-stable/
>> >
>