Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
From: Gavin McDonald <gavin@16degrees.com.au>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_2D80A392-F95C-498E-8D02-C3753C4E4494"
Reply-To: builds@apache.org
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: [JENKINS]  [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
 deprecation)
Date: Tue, 27 Jun 2017 17:03:13 +1000
Message-Id: <573832AC-086E-40DA-9CAB-C9D316968CE2@16degrees.com.au>
Cc: ASF Operations <operations@apache.org>
To: builds@apache.org
archived-at: Tue, 27 Jun 2017 07:03:39 -0000

--Apple-Mail=_2D80A392-F95C-498E-8D02-C3753C4E4494
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

ASF Jenkins Master Migration and Upgrade on :-


Location	                                        Local Time	 =
                                       Time Zone	UTC Offset
Melbourne (Australia - Victoria)	Sunday, 16 July 2017 at 10:00: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	 =
	=20


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 yaml =
have been puppetized and ready to go.
    What we need to do to migrate the Master away from its current host =
is turn off the old service. Perform a final=20
    rsync of data and perform the migration tasks.=20

    As we intend to preserve history for jobs this will take some time.
    At the same time as doing this migration to a new host, all slave =
connections will be updated (see below.)
    I have no current estimate of downtime, but it will run into several =
hours. We do plan to run this migration on a=20
    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=20
    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=20
    however was necessary due to security fixes that required our =
upgrade.  This email serves as advance warning of the=20
    upcoming upgrade of Jenkins, the downtime due to the migration of =
the service to a new host; and notice of the breakage=20
    to JDK 7 that the upgrade brings.

    Please familiarise yourself with the Jenkins LTS upgrade notes at =
[1].
    In particular please note:-

    =E2=80=9C=E2=80=A62.60.1 is the first Jenkins LTS release that =
requires 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 configure 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 Plugin 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 post =
<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.=20

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.=20

Any questions or concerns please email back to builds@apache.org =
<mailto:builds@apache.org> only.=20

Thanks

Gav=E2=80=A6

[1] - https://jenkins.io/changelog-stable/=

--Apple-Mail=_2D80A392-F95C-498E-8D02-C3753C4E4494--