Return-Path: <dev-return-18920-archive-asf-public=cust-asf.ponee.io@accumulo.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 565AF200CB5
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Wed, 28 Jun 2017 00:26:05 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 54D31160BE9; Tue, 27 Jun 2017 22:26:05 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 98AFE160BDC
	for <archive-asf-public@cust-asf.ponee.io>; Wed, 28 Jun 2017 00:26:04 +0200 (CEST)
Received: (qmail 82509 invoked by uid 500); 27 Jun 2017 22:26:03 -0000
Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@accumulo.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@accumulo.apache.org>
List-Post: <mailto:dev@accumulo.apache.org>
List-Id: <dev.accumulo.apache.org>
Reply-To: dev@accumulo.apache.org
Delivered-To: mailing list dev@accumulo.apache.org
Received: (qmail 82498 invoked by uid 99); 27 Jun 2017 22:26:03 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2017 22:26:03 +0000
Received: from mail-ua0-f178.google.com (mail-ua0-f178.google.com [209.85.217.178])
	by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 27B621A00A2
	for <dev@accumulo.apache.org>; Tue, 27 Jun 2017 22:26:01 +0000 (UTC)
Received: by mail-ua0-f178.google.com with SMTP id w19so6553110uac.0
        for <dev@accumulo.apache.org>; Tue, 27 Jun 2017 15:26:01 -0700 (PDT)
X-Gm-Message-State: AKS2vOyFvspU7Jl+WD6WsOQ85KBeqedulDuE8DaITSv8i61q3U2zQjo4
	qFrIeF8r1RztJe9VDfk7s1xiW31p8A==
X-Received: by 10.176.80.19 with SMTP id b19mr4442733uaa.139.1498602361009;
 Tue, 27 Jun 2017 15:26:01 -0700 (PDT)
MIME-Version: 1.0
References: <573832AC-086E-40DA-9CAB-C9D316968CE2@16degrees.com.au> <49d3be80-3a15-2181-18be-b0883d7d9117@apache.org>
In-Reply-To: <49d3be80-3a15-2181-18be-b0883d7d9117@apache.org>
From: Christopher <ctubbsii@apache.org>
Date: Tue, 27 Jun 2017 22:25:50 +0000
X-Gmail-Original-Message-ID: <CAL5zq9b1ZX7dwEhEexGxeeFZw2yPh6=dN0RBFesi0evyQ=kTJg@mail.gmail.com>
Message-ID: <CAL5zq9b1ZX7dwEhEexGxeeFZw2yPh6=dN0RBFesi0evyQ=kTJg@mail.gmail.com>
Subject: Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
To: dev@accumulo.apache.org
Content-Type: multipart/alternative; boundary="94eb2c18f87863413c0552f88d29"
archived-at: Tue, 27 Jun 2017 22:26:05 -0000

--94eb2c18f87863413c0552f88d29
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks for the heads-up. I think I've already migrated our builds.apache.or=
g
jobs to use JDK8, because of some annoying permgen space exhaustion with
the asciidoc-maven-plugin which I couldn't resolve. We currently rely on
the maven-enforcer-plugin animal-sniffer rule to ensure we avoid Java 8
APIs when compiling with JDK8, so I think we're safe. Although... we may
wish to still do releases on the 1.7 and 1.8 branches using an actual JDK7
if we want to be extra safe for a release.

On Tue, Jun 27, 2017 at 11:57 AM Josh Elser <elserj@apache.org> wrote:

> tl;dr Infra is upgrading Jenkins in 2 weeks and Java7 Maven jobs
> may/may-not work after this. See explanation below from [1]:
>
> <snip>
> Users with jobs configured with the "Maven project" type may not be able
> to use Java 7 for their Maven jobs. The correct behavior is not
> guaranteed so proceed at your own risk. The Maven Project uses Jenkins
> Remoting to establish "interceptors" within the Maven executable.
> Because of this, Maven uses Remoting and other Jenkins core classes, and
> this behavior may break an update.
> </snip>
>
> [1] https://jenkins.io/blog/2017/04/10/jenkins-has-upgraded-to-java-8/
>
>
> -------- Forwarded Message --------
> Subject: [JENKINS]  [IMPORTANT] - Jenkins Migration and Upgrade (And
> JDK7 deprecation)
> Date: Tue, 27 Jun 2017 17:03:13 +1000
> From: Gavin McDonald <gavin@16degrees.com.au>
> Reply-To: builds@apache.org, builds@apache.org
> To: builds@apache.org
> CC: ASF Operations <operations@apache.org>
>
> 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
>
> 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     rsync of data and
> perform the migration tasks.
>      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     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 of 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 at [1=
].
>      In particular please note:-
>
>      =E2=80=9C=E2=80=A62.60.1 is the first Jenkins LTS release that requi=
res 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.
> 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/
>

--94eb2c18f87863413c0552f88d29--