You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by Gavin McDonald <ga...@16degrees.com.au> on 2017/06/27 07:03:13 UTC
[JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
deprecation)
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:-
“…2.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/>)
…”
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 <ma...@apache.org> only.
Thanks
Gav…
[1] - https://jenkins.io/changelog-stable/
Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Christopher <ct...@apache.org>.
Thanks for the heads-up. I think I've already migrated our builds.apache.org
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 <el...@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 <ga...@16degrees.com.au>
> Reply-To: builds@apache.org, builds@apache.org
> To: builds@apache.org
> CC: ASF Operations <op...@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:-
>
> “…2.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/>)
>
> …”
>
> 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
> <ma...@apache.org> only.
> Thanks
>
> Gav…
>
> [1] - https://jenkins.io/changelog-stable/
>
Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
deprecation)
Posted by Josh Elser <el...@apache.org>.
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 <ga...@16degrees.com.au>
Reply-To: builds@apache.org, builds@apache.org
To: builds@apache.org
CC: ASF Operations <op...@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:-
“…2.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/>)
…”
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
<ma...@apache.org> only.
Thanks
Gav…
[1] - https://jenkins.io/changelog-stable/
Re: Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)
Posted by Yasser Zamani <ya...@live.com>.
Yeah! following paragraph:
"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."
means we should drop support of both JDK6 & JDK7.
On 6/27/2017 1:36 PM, Lukasz Lenart wrote:
> This can affect our builds :\
>
> It's about a time to think on switching to JDK8
>
>
> ---------- Forwarded message ----------
> From: Gavin McDonald <ga...@16degrees.com.au>
> Date: 2017-06-27 9:03 GMT+02:00
> Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
> JDK7 deprecation)
> To: builds@apache.org
> DW: ASF Operations <op...@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:-
>
> “…2.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/>)
>
> …”
>
> 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
> <ma...@apache.org> only.
>
> Thanks
>
> Gav…
>
> [1] - https://jenkins.io/changelog-stable/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
deprecation)
Posted by Christoph Nenning <Ch...@lex-com.net>.
In theory it should be possible to create new build jobs with type
"freestyle" instead of type "maven". Then maven could be invoked via shell
and jdk 7 (or even 6). But all configuration (e.g. collection of test
results and aritfacts) must be done manually then.
wdyt?
Regards,
Christoph
> From: Lukasz Lenart <lu...@apache.org>
> To: Struts Developers List <de...@struts.apache.org>,
> Date: 27.06.2017 11:07
> Subject: Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade
> (And JDK7 deprecation)
>
> This can affect our builds :\
>
> It's about a time to think on switching to JDK8
>
>
> ---------- Forwarded message ----------
> From: Gavin McDonald <ga...@16degrees.com.au>
> Date: 2017-06-27 9:03 GMT+02:00
> Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
> JDK7 deprecation)
> To: builds@apache.org
> DW: ASF Operations <op...@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:-
>
> “…2.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/
>)
>
> …”
>
> 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
> <ma...@apache.org> only.
>
> Thanks
>
> Gav…
>
> [1] - https://jenkins.io/changelog-stable/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
This Email was scanned by Sophos Anti Virus
Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Lukasz Lenart <lu...@apache.org>.
This can affect our builds :\
It's about a time to think on switching to JDK8
---------- Forwarded message ----------
From: Gavin McDonald <ga...@16degrees.com.au>
Date: 2017-06-27 9:03 GMT+02:00
Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)
To: builds@apache.org
DW: ASF Operations <op...@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:-
“…2.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/>)
…”
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
<ma...@apache.org> only.
Thanks
Gav…
[1] - https://jenkins.io/changelog-stable/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
deprecation)
Posted by Josh Elser <el...@apache.org>.
I believe the answer is "maybe" at this point. The phrasing of the alert
seems to be saying "jdk7 might not work", but non-committal in that warning.
On 6/27/17 4:24 PM, Julian Hyde wrote:
> Does this mean that we will lose coverage for JDK 7?
>
> If so, it shouldn't be a huge problem. I run tests nightly on my home
> Linux box and it should detect if anything is amiss.
>
> On Tue, Jun 27, 2017 at 8:57 AM, Josh Elser <el...@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 <ga...@16degrees.com.au>
>> Reply-To: builds@apache.org, builds@apache.org
>> To: builds@apache.org
>> CC: ASF Operations <op...@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:-
>>
>> “…2.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/>)
>>
>> …”
>>
>> 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
>> <ma...@apache.org> only.
>> Thanks
>>
>> Gav…
>>
>> [1] - https://jenkins.io/changelog-stable/
Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Julian Hyde <jh...@apache.org>.
Does this mean that we will lose coverage for JDK 7?
If so, it shouldn't be a huge problem. I run tests nightly on my home
Linux box and it should detect if anything is amiss.
On Tue, Jun 27, 2017 at 8:57 AM, Josh Elser <el...@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 <ga...@16degrees.com.au>
> Reply-To: builds@apache.org, builds@apache.org
> To: builds@apache.org
> CC: ASF Operations <op...@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:-
>
> “…2.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/>)
>
> …”
>
> 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
> <ma...@apache.org> only.
> Thanks
>
> Gav…
>
> [1] - https://jenkins.io/changelog-stable/
Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
deprecation)
Posted by Josh Elser <el...@apache.org>.
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 <ga...@16degrees.com.au>
Reply-To: builds@apache.org, builds@apache.org
To: builds@apache.org
CC: ASF Operations <op...@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:-
“…2.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/>)
…”
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
<ma...@apache.org> only.
Thanks
Gav…
[1] - https://jenkins.io/changelog-stable/
Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
deprecation)
Posted by Josh Elser <el...@apache.org>.
Sorry for the churn! I didn't update my inbox soon enough it seems and
missed Mike's thread when sending mine :)
On 6/27/17 12:16 PM, Sean Busbey wrote:
> Let's keep these on one thread:
>
> https://lists.apache.org/thread.html/cb08670178f5c645ad2387f14ad485face0594e89d976bf31865596f@%3Cdev.hbase.apache.org%3E
>
> On Tue, Jun 27, 2017 at 10:57 AM, Josh Elser <el...@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 <ga...@16degrees.com.au>
>> Reply-To: builds@apache.org, builds@apache.org
>> To: builds@apache.org
>> CC: ASF Operations <op...@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:-
>>
>> “…2.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/>)
>>
>> …”
>>
>> 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…
>>
>> [1] - https://jenkins.io/changelog-stable/
>>
>
Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Sean Busbey <bu...@apache.org>.
Let's keep these on one thread:
https://lists.apache.org/thread.html/cb08670178f5c645ad2387f14ad485face0594e89d976bf31865596f@%3Cdev.hbase.apache.org%3E
On Tue, Jun 27, 2017 at 10:57 AM, Josh Elser <el...@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 <ga...@16degrees.com.au>
> Reply-To: builds@apache.org, builds@apache.org
> To: builds@apache.org
> CC: ASF Operations <op...@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:-
>
> “…2.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/>)
>
> …”
>
> 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…
>
> [1] - https://jenkins.io/changelog-stable/
>
Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
deprecation)
Posted by Josh Elser <el...@apache.org>.
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 <ga...@16degrees.com.au>
Reply-To: builds@apache.org, builds@apache.org
To: builds@apache.org
CC: ASF Operations <op...@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:-
“…2.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/>)
…”
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
<ma...@apache.org> only.
Thanks
Gav…
[1] - https://jenkins.io/changelog-stable/
Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Gary Gregory <ga...@gmail.com>.
Oleg and All, FYI.
Gary
---------- Forwarded message ----------
From: "sebb" <se...@gmail.com>
Date: Jun 27, 2017 07:10
Subject: Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)
To: "CommonsDev" <de...@commons.apache.org>
Cc:
AFAIK most of the Commons jobs use JDK 1.7 latest and the java-1.n
profiles to choose the appropriate compile/test environment.
These should continue to build OK, assuming that Jenkins is able to
find a suitable version of Java if necessary.
Builds which rely on JDK 7 and which don't use a Java profile will
find that the compile/test now use Java 8.
We need predictable builds so we need to ensure that all Maven builds
use the appropriate java profiles for the target JVM.
Once all the builds use the appropriate Java profiles we should be OK
when Jenkins next change the minimum Java version.
---------- Forwarded message ----------
From: Gavin McDonald <ga...@16degrees.com.au>
Date: 27 June 2017 at 08:03
Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)
To: builds@apache.org
Cc: ASF Operations <op...@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:-
“…2.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/>)
…”
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
<ma...@apache.org> only.
Thanks
Gav…
[1] - https://jenkins.io/changelog-stable/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by sebb <se...@gmail.com>.
AFAIK most of the Commons jobs use JDK 1.7 latest and the java-1.n
profiles to choose the appropriate compile/test environment.
These should continue to build OK, assuming that Jenkins is able to
find a suitable version of Java if necessary.
Builds which rely on JDK 7 and which don't use a Java profile will
find that the compile/test now use Java 8.
We need predictable builds so we need to ensure that all Maven builds
use the appropriate java profiles for the target JVM.
Once all the builds use the appropriate Java profiles we should be OK
when Jenkins next change the minimum Java version.
---------- Forwarded message ----------
From: Gavin McDonald <ga...@16degrees.com.au>
Date: 27 June 2017 at 08:03
Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)
To: builds@apache.org
Cc: ASF Operations <op...@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:-
“…2.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/>)
…”
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
<ma...@apache.org> only.
Thanks
Gav…
[1] - https://jenkins.io/changelog-stable/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
deprecation)
Posted by Josh Elser <el...@apache.org>.
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 <ga...@16degrees.com.au>
Reply-To: builds@apache.org, builds@apache.org
To: builds@apache.org
CC: ASF Operations <op...@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:-
“…2.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/>)
…”
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
<ma...@apache.org> only.
Thanks
Gav…
[1] - https://jenkins.io/changelog-stable/
Re: [Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade
(And JDK7 deprecation)]
Posted by Robert Munteanu <ro...@apache.org>.
On Tue, 2017-06-27 at 15:48 +0000, Stefan Seifert wrote:
> i'm ok with 1)
> we still have the compile and signature check in the poms.
>
> i cannot remember any problems in in the last 1-2 years that where
> related to differences between the JDK versions.
Done via https://issues.apache.org/jira/browse/SLING-7005 .
Robert
>
> stefan
>
> > -----Original Message-----
> > From: Robert Munteanu [mailto:rombert@apache.org]
> > Sent: Tuesday, June 27, 2017 11:39 AM
> > To: dev@sling.apache.org
> > Subject: [Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and
> > Upgrade (And
> > JDK7 deprecation)]
> >
> > Hi,
> >
> > In two weeks the ASF Jenkins instance will stop supporting JDK 7
> > for
> > Maven jobs (details attached).
> >
> > There will be an impact for us as we have a large number of jobs
> > fitting this description.
> >
> > There are two ways out:
> >
> > 1) Remove the Java 7 jobs, as we're moving towards Java 8 anyway
> > 2) Switch to the freestyle job type
> >
> > The downside of 1) is that we will no longer test with Java 7.
> > The downside of 2) is that we will no longer have automatic job
> > dependencies calculated and we will have to either
> >
> > a) manually maintain the dependencies between jobs
> > b) live with stale jobs and/or manually trigger them
> >
> > I would incline towards 1), but I would like to hear what others
> > think
> > as well.
> >
> > Thanks,
> >
> > Robert
RE: [Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)]
Posted by Stefan Seifert <ss...@pro-vision.de>.
i'm ok with 1)
we still have the compile and signature check in the poms.
i cannot remember any problems in in the last 1-2 years that where related to differences between the JDK versions.
stefan
>-----Original Message-----
>From: Robert Munteanu [mailto:rombert@apache.org]
>Sent: Tuesday, June 27, 2017 11:39 AM
>To: dev@sling.apache.org
>Subject: [Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
>JDK7 deprecation)]
>
>Hi,
>
>In two weeks the ASF Jenkins instance will stop supporting JDK 7 for
>Maven jobs (details attached).
>
>There will be an impact for us as we have a large number of jobs
>fitting this description.
>
>There are two ways out:
>
>1) Remove the Java 7 jobs, as we're moving towards Java 8 anyway
>2) Switch to the freestyle job type
>
>The downside of 1) is that we will no longer test with Java 7.
>The downside of 2) is that we will no longer have automatic job
>dependencies calculated and we will have to either
>
>a) manually maintain the dependencies between jobs
>b) live with stale jobs and/or manually trigger them
>
>I would incline towards 1), but I would like to hear what others think
>as well.
>
>Thanks,
>
>Robert
[Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)]
Posted by Robert Munteanu <ro...@apache.org>.
Hi,
In two weeks the ASF Jenkins instance will stop supporting JDK 7 for
Maven jobs (details attached).
There will be an impact for us as we have a large number of jobs
fitting this description.
There are two ways out:
1) Remove the Java 7 jobs, as we're moving towards Java 8 anyway
2) Switch to the freestyle job type
The downside of 1) is that we will no longer test with Java 7.
The downside of 2) is that we will no longer have automatic job
dependencies calculated and we will have to either
a) manually maintain the dependencies between jobs
b) live with stale jobs and/or manually trigger them
I would incline towards 1), but I would like to hear what others think
as well.
Thanks,
Robert
Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
deprecation)
Posted by Andy Seaborne <an...@apache.org>.
from builds@apache.org
Recap: In just over 2 weeks, downtime for a migration AND upgrade is planned.
Sunday, 16 July 2017 at 00:00:00
-------- Forwarded Message --------
Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)
Date: Tue, 27 Jun 2017 17:03:13 +1000
From: Gavin McDonald <ga...@16degrees.com.au>
Reply-To: builds@apache.org, builds@apache.org
To: builds@apache.org
CC: ASF Operations <op...@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:-
“…2.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/>)
…”
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 <ma...@apache.org> only.
Thanks
Gav…
[1] - https://jenkins.io/changelog-stable/
Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Sean Busbey <bu...@apache.org>.
We already ignore ASF infra's jdk and rely on openjdk7 via docker for
precommit on branch-1 and earlier.
Sounds like we'll need to update our nightly runs to similarly rely on
docker, which is a pretty good reason to switch to yetus' nightly check
mode.
This is what, like 2 weeks notice?
On Tue, Jun 27, 2017 at 9:49 AM, Mike Drob <md...@apache.org> wrote:
> Gavin of the infra team just sent this missive over.
>
> It looks like JDK 7 will no longer be available. Do we need to do anything
> this affect our branch-1, or are we sufficiently confident that JDK8 with
> compatibility mode targeting 1.7 will be enough for our needs?
>
> Mike
>
> ---------- Forwarded message ----------
> From: Gavin McDonald <ga...@16degrees.com.au>
> Date: Tue, Jun 27, 2017 at 2:03 AM
> Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
> deprecation)
> To: builds@apache.org
> Cc: ASF Operations <op...@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:-
>
> “…2.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/>)
>
> …”
>
> 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…
>
> [1] - https://jenkins.io/changelog-stable/
>
Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Mike Drob <md...@apache.org>.
Gavin of the infra team just sent this missive over.
It looks like JDK 7 will no longer be available. Do we need to do anything
this affect our branch-1, or are we sufficiently confident that JDK8 with
compatibility mode targeting 1.7 will be enough for our needs?
Mike
---------- Forwarded message ----------
From: Gavin McDonald <ga...@16degrees.com.au>
Date: Tue, Jun 27, 2017 at 2:03 AM
Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
deprecation)
To: builds@apache.org
Cc: ASF Operations <op...@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:-
“…2.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/>)
…”
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…
[1] - https://jenkins.io/changelog-stable/
Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Anders Hammar <an...@hammar.net>.
See info below.
It looks as we're on the Maven project build type for some builds so that
this will affect us wrt JDK7 deprecation.
/Anders
---------- Forwarded message ----------
From: Gavin McDonald <ga...@16degrees.com.au>
Date: Tue, Jun 27, 2017 at 9:03 AM
Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7
deprecation)
To: builds@apache.org
Cc: ASF Operations <op...@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:-
“…2.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/>)
…”
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…
[1] - https://jenkins.io/changelog-stable/
Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Lukasz Lenart <lu...@apache.org>.
Thanks sebb!
For now, the approach with a Free Style Job fits our needs :)
2017-06-29 12:03 GMT+02:00 sebb <se...@gmail.com>:
> Or you can run Maven using Java x but compile/test using Java y.
>
> This can either be done via toolchains
>
> http://maven.apache.org/guides/mini/guide-using-toolchains.html
>
> Or using properties to redefine the executables used by the
> compile/build steps (as is done by the Commons parent pom), see:
>
> http://commons.apache.org/commons-parent-pom.html
>
>
> On 29 June 2017 at 07:45, Lukasz Lenart <lu...@apache.org> wrote:
>> Thanks Uwe, this is very helpful!
>>
>> 2017-06-29 0:01 GMT+02:00 Uwe Schindler <us...@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., "${MAVEN_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 by 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 Maven
>>>> jobs for JDK 7"
>>>>
>>>> On Wed, Jun 28, 2017 at 10:01 AM, Lukasz Lenart
>>>> <lu...@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
>>>> > --
>>>> > Łukasz
>>>> > + 48 606 323 122 http://www.lenart.org.pl/
>>>> >
>>>> > 2017-06-27 9:03 GMT+02:00 Gavin McDonald <ga...@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: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:-
>>>> > >
>>>> > > “…2.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/>)
>>>> > >
>>>> > > …”
>>>> > >
>>>> > > 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
>>>> > <ma...@apache.org> only.
>>>> > >
>>>> > > Thanks
>>>> > >
>>>> > > Gav…
>>>> > >
>>>> > > [1] - https://jenkins.io/changelog-stable/
>>>> >
>>>
Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by sebb <se...@gmail.com>.
Or you can run Maven using Java x but compile/test using Java y.
This can either be done via toolchains
http://maven.apache.org/guides/mini/guide-using-toolchains.html
Or using properties to redefine the executables used by the
compile/build steps (as is done by the Commons parent pom), see:
http://commons.apache.org/commons-parent-pom.html
On 29 June 2017 at 07:45, Lukasz Lenart <lu...@apache.org> wrote:
> Thanks Uwe, this is very helpful!
>
> 2017-06-29 0:01 GMT+02:00 Uwe Schindler <us...@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., "${MAVEN_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 by 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 Maven
>>> jobs for JDK 7"
>>>
>>> On Wed, Jun 28, 2017 at 10:01 AM, Lukasz Lenart
>>> <lu...@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
>>> > --
>>> > Łukasz
>>> > + 48 606 323 122 http://www.lenart.org.pl/
>>> >
>>> > 2017-06-27 9:03 GMT+02:00 Gavin McDonald <ga...@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: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:-
>>> > >
>>> > > “…2.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/>)
>>> > >
>>> > > …”
>>> > >
>>> > > 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
>>> > <ma...@apache.org> only.
>>> > >
>>> > > Thanks
>>> > >
>>> > > Gav…
>>> > >
>>> > > [1] - https://jenkins.io/changelog-stable/
>>> >
>>
Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Lukasz Lenart <lu...@apache.org>.
Thanks Uwe, this is very helpful!
2017-06-29 0:01 GMT+02:00 Uwe Schindler <us...@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., "${MAVEN_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 by 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 Maven
>> jobs for JDK 7"
>>
>> On Wed, Jun 28, 2017 at 10:01 AM, Lukasz Lenart
>> <lu...@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
>> > --
>> > Łukasz
>> > + 48 606 323 122 http://www.lenart.org.pl/
>> >
>> > 2017-06-27 9:03 GMT+02:00 Gavin McDonald <ga...@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: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:-
>> > >
>> > > “…2.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/>)
>> > >
>> > > …”
>> > >
>> > > 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
>> > <ma...@apache.org> only.
>> > >
>> > > Thanks
>> > >
>> > > Gav…
>> > >
>> > > [1] - https://jenkins.io/changelog-stable/
>> >
>
RE: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Uwe Schindler <us...@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., "${MAVEN_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 by 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 Maven
> jobs for JDK 7"
>
> On Wed, Jun 28, 2017 at 10:01 AM, Lukasz Lenart
> <lu...@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
> > --
> > Łukasz
> > + 48 606 323 122 http://www.lenart.org.pl/
> >
> > 2017-06-27 9:03 GMT+02:00 Gavin McDonald <ga...@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: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:-
> > >
> > > “…2.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/>)
> > >
> > > …”
> > >
> > > 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
> > <ma...@apache.org> only.
> > >
> > > Thanks
> > >
> > > Gav…
> > >
> > > [1] - https://jenkins.io/changelog-stable/
> >
Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Greg Stein <gs...@gmail.com>.
I think it depends upon your job type, as Gavin wrote: "in terms of Maven
jobs for JDK 7"
On Wed, Jun 28, 2017 at 10:01 AM, Lukasz Lenart <lu...@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
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2017-06-27 9:03 GMT+02:00 Gavin McDonald <ga...@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: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:-
> >
> > “…2.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/>)
> >
> > …”
> >
> > 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
> <ma...@apache.org> only.
> >
> > Thanks
> >
> > Gav…
> >
> > [1] - https://jenkins.io/changelog-stable/
>
Re: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)
Posted by Lukasz Lenart <lu...@apache.org>.
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
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2017-06-27 9:03 GMT+02:00 Gavin McDonald <ga...@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: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:-
>
> “…2.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/>)
>
> …”
>
> 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 <ma...@apache.org> only.
>
> Thanks
>
> Gav…
>
> [1] - https://jenkins.io/changelog-stable/
Fwd: REMINDER: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade
(And JDK7 deprecation)
Posted by Geoff Macartney <ge...@cloudsoft.io>.
Just for general awareness, I'm forwarding an Infra reminder relating to
downtime on the Apache Jenkins instances this weekend.
G
---------- Forwarded message ---------
From: Gavin McDonald <ga...@16degrees.com.au>
Date: Fri, 14 Jul 2017 at 11:56
Subject: REMINDER: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade
(And JDK7 deprecation)
To: <bu...@apache.org>
Cc: ASF Operations <op...@apache.org>
HI Folks,
time is almost upon us.
This Saturday/Sunday (depending on your TZ) is when the migration and
upgrade happens.
Is everyone prepared for :-
A) The amount of downtime - it will be several hours , including stopping
new jobs from running to allow for
in progress jobs to complete.
B) the Maven JDK 1.7 issue. Workarounds have been mentioned on this list
and I will document them on
the Infra Confluence Wiki shortly.
C) Plugin Upgrades - These will be upgraded both before, for those that are
compatible with the current
running version, and after the upgrade, to being them inline with the new
Jenkins version.
I will be on HipChat #asfinfra (https://infra.chat <https://infra.chat/>)
all weekend should anyone have any questions before/during/after.
Thanks
Gav…
> On 27 Jun 2017, at 5:03 pm, Gavin McDonald <ga...@16degrees.com.au> wrote:
>
> 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:-
>
> “…2.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/>)
>
> …”
>
> 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…
>
> [1] - https://jenkins.io/changelog-stable/
REMINDER: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)
Posted by Gavin McDonald <ga...@16degrees.com.au>.
HI Folks,
time is almost upon us.
This Saturday/Sunday (depending on your TZ) is when the migration and upgrade happens.
Is everyone prepared for :-
A) The amount of downtime - it will be several hours , including stopping new jobs from running to allow for
in progress jobs to complete.
B) the Maven JDK 1.7 issue. Workarounds have been mentioned on this list and I will document them on
the Infra Confluence Wiki shortly.
C) Plugin Upgrades - These will be upgraded both before, for those that are compatible with the current
running version, and after the upgrade, to being them inline with the new Jenkins version.
I will be on HipChat #asfinfra (https://infra.chat <https://infra.chat/>) all weekend should anyone have any questions before/during/after.
Thanks
Gav…
> On 27 Jun 2017, at 5:03 pm, Gavin McDonald <ga...@16degrees.com.au> wrote:
>
> 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:-
>
> “…2.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/>)
>
> …”
>
> 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 <ma...@apache.org> only.
>
> Thanks
>
> Gav…
>
> [1] - https://jenkins.io/changelog-stable/
Re: Time to give up on Java 7 compatibility? [Fwd: [JENKINS]
[IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)]
Posted by sebb <se...@gmail.com>.
On 28 June 2017 at 09:32, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Wed, 2017-06-28 at 00:49 +0100, sebb wrote:
>> It's only Maven projects that have to be run with Java 8 on Jenkins.
>> And this only affects the Maven framework.
>>
>> Compilation and testing can still be done with earlier Java versions.
>>
>> Commons has lots of components that target Java 6 or even 5, and they
>> work fine with current Jenkins (which needs Java 7).
>>
>
> It does not look that way to me. I understand one can still spawn any
> arbitrary process with Jenkins as a job but this is not the same as
> having full Maven project support.
Commons uses profiles (defined in the parent pom) to specify the JDK
used for compile and test.
For example, Commons Net builds fine but requires 1.6
It runs as a Maven project, not freestyle.
The job uses JDK 8, but compile/test use 1.6
I probably don't have time to look at this today, but I may have time tomorrow.
> ---
> [httpcomponents-client-4.5.x] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx2g -Xms256m -cp /home/jenkins/jenkins-slave/maven33-agent.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/conf/logging jenkins.maven3.agent.Maven33Main /home/jenkins/tools/maven/apache-maven-3.3.9 /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven33-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 39826
> Native maven support requires Java 1.7 or later, but this Maven is using /usr/local/asfpackages/java/jdk1.6.0_45-64/jre
> Please use the freestyle project.
For the next release of Jenkins, AFAICT it will try to find a JDK8 to
run Maven projects.
So the job will run, but not using the expected JDK.
> ERROR: Failed to launch Maven. Exit code = 1
> Sending e-mails to: commits@hc.apache.org
> Warning: this build has no associated authentication, so build permissions may be lacking, and downstream projects which cannot even be seen by an anonymous user will be silently skipped
> Finished: FAILURE
> ---
>
> Oleg
>
>
>> The Jenkins JVM requirement is not directly relevant to HC (or any
>> other project), and should not be used to drive a change.
>>
>> On 27 June 2017 at 16:35, Gary Gregory <ga...@gmail.com>
>> wrote:
>> > Giving up Java 7 works for me. It is not clear to me that the
>> > Jenkins
>> > update does not support Java 7 at all though:
>> >
>> > "If your Maven projects need to be built with JDK 7, consider
>> > converting
>> > them to freestyle projects, or look into Maven toolchains."
>> >
>> > We use Maven toolchains over at Log4j (for building some bits with
>> > Java 9)
>> > and that works fine.
>> >
>> > The business SSH slaves does not sound pretty though.
>> >
>> > Travis-CI still supports Java 7 of course so we can go with that.
>> >
>> > We just need to decide what matters for 5.0 and 4.6. Java 8 is OK
>> > here.
>> >
>> > Gary
>> >
>> > On Jun 27, 2017 04:22, "Oleg Kalnichevski" <ol...@apache.org>
>> > wrote:
>> >
>> > Folks
>> >
>> > ASF Jenkins will no longer support Java7 Maven projects soon. That
>> > means there will be no way to reliably test Java 7 compatibility
>> > anymore.
>> >
>> > Maybe it is time we gave up on Java 7 compatibility altogether. By
>> > the
>> > time 5.0.x projects go GA Java 7 may no longer matter.
>> >
>> > What do you think?
>> >
>> > Oleg
>> >
>> >
>> > -------- Forwarded Message --------
>> > From: Gavin McDonald <ga...@16degrees.com.au>
>> > Reply-to: builds@apache.org
>> > To: builds@apache.org
>> > Cc: ASF Operations <op...@apache.org>
>> > Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade
>> > (And
>> > JDK7 deprecation)
>> > Date: Tue, 27 Jun 2017 17:03:13 +1000
>> >
>> > ...
>> >
>> >
>> > 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:-
>> >
>> > “…2.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).
>> > ...
>> >
>> > -----------------------------------------------------------------
>> > ----
>> > To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
>> > For additional commands, e-mail: dev-help@hc.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
>> For additional commands, e-mail: dev-help@hc.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Time to give up on Java 7 compatibility? [Fwd: [JENKINS]
[IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)]
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Wed, 2017-06-28 at 00:49 +0100, sebb wrote:
> It's only Maven projects that have to be run with Java 8 on Jenkins.
> And this only affects the Maven framework.
>
> Compilation and testing can still be done with earlier Java versions.
>
> Commons has lots of components that target Java 6 or even 5, and they
> work fine with current Jenkins (which needs Java 7).
>
It does not look that way to me. I understand one can still spawn any
arbitrary process with Jenkins as a job but this is not the same as
having full Maven project support.
---
[httpcomponents-client-4.5.x] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx2g -Xms256m -cp /home/jenkins/jenkins-slave/maven33-agent.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/apache-maven-3.3.9/conf/logging jenkins.maven3.agent.Maven33Main /home/jenkins/tools/maven/apache-maven-3.3.9 /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven33-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 39826
Native maven support requires Java 1.7 or later, but this Maven is using /usr/local/asfpackages/java/jdk1.6.0_45-64/jre
Please use the freestyle project.
ERROR: Failed to launch Maven. Exit code = 1
Sending e-mails to: commits@hc.apache.org
Warning: this build has no associated authentication, so build permissions may be lacking, and downstream projects which cannot even be seen by an anonymous user will be silently skipped
Finished: FAILURE
---
Oleg
> The Jenkins JVM requirement is not directly relevant to HC (or any
> other project), and should not be used to drive a change.
>
> On 27 June 2017 at 16:35, Gary Gregory <ga...@gmail.com>
> wrote:
> > Giving up Java 7 works for me. It is not clear to me that the
> > Jenkins
> > update does not support Java 7 at all though:
> >
> > "If your Maven projects need to be built with JDK 7, consider
> > converting
> > them to freestyle projects, or look into Maven toolchains."
> >
> > We use Maven toolchains over at Log4j (for building some bits with
> > Java 9)
> > and that works fine.
> >
> > The business SSH slaves does not sound pretty though.
> >
> > Travis-CI still supports Java 7 of course so we can go with that.
> >
> > We just need to decide what matters for 5.0 and 4.6. Java 8 is OK
> > here.
> >
> > Gary
> >
> > On Jun 27, 2017 04:22, "Oleg Kalnichevski" <ol...@apache.org>
> > wrote:
> >
> > Folks
> >
> > ASF Jenkins will no longer support Java7 Maven projects soon. That
> > means there will be no way to reliably test Java 7 compatibility
> > anymore.
> >
> > Maybe it is time we gave up on Java 7 compatibility altogether. By
> > the
> > time 5.0.x projects go GA Java 7 may no longer matter.
> >
> > What do you think?
> >
> > Oleg
> >
> >
> > -------- Forwarded Message --------
> > From: Gavin McDonald <ga...@16degrees.com.au>
> > Reply-to: builds@apache.org
> > To: builds@apache.org
> > Cc: ASF Operations <op...@apache.org>
> > Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade
> > (And
> > JDK7 deprecation)
> > Date: Tue, 27 Jun 2017 17:03:13 +1000
> >
> > ...
> >
> >
> > 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:-
> >
> > “…2.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).
> > ...
> >
> > -----------------------------------------------------------------
> > ----
> > To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> > For additional commands, e-mail: dev-help@hc.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Time to give up on Java 7 compatibility? [Fwd: [JENKINS]
[IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)]
Posted by sebb <se...@gmail.com>.
It's only Maven projects that have to be run with Java 8 on Jenkins.
And this only affects the Maven framework.
Compilation and testing can still be done with earlier Java versions.
Commons has lots of components that target Java 6 or even 5, and they
work fine with current Jenkins (which needs Java 7).
The Jenkins JVM requirement is not directly relevant to HC (or any
other project), and should not be used to drive a change.
On 27 June 2017 at 16:35, Gary Gregory <ga...@gmail.com> wrote:
> Giving up Java 7 works for me. It is not clear to me that the Jenkins
> update does not support Java 7 at all though:
>
> "If your Maven projects need to be built with JDK 7, consider converting
> them to freestyle projects, or look into Maven toolchains."
>
> We use Maven toolchains over at Log4j (for building some bits with Java 9)
> and that works fine.
>
> The business SSH slaves does not sound pretty though.
>
> Travis-CI still supports Java 7 of course so we can go with that.
>
> We just need to decide what matters for 5.0 and 4.6. Java 8 is OK here.
>
> Gary
>
> On Jun 27, 2017 04:22, "Oleg Kalnichevski" <ol...@apache.org> wrote:
>
> Folks
>
> ASF Jenkins will no longer support Java7 Maven projects soon. That
> means there will be no way to reliably test Java 7 compatibility
> anymore.
>
> Maybe it is time we gave up on Java 7 compatibility altogether. By the
> time 5.0.x projects go GA Java 7 may no longer matter.
>
> What do you think?
>
> Oleg
>
>
> -------- Forwarded Message --------
> From: Gavin McDonald <ga...@16degrees.com.au>
> Reply-to: builds@apache.org
> To: builds@apache.org
> Cc: ASF Operations <op...@apache.org>
> Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
> JDK7 deprecation)
> Date: Tue, 27 Jun 2017 17:03:13 +1000
>
> ...
>
>
> 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:-
>
> “…2.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).
> ...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Time to give up on Java 7 compatibility? [Fwd: [JENKINS]
[IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)]
Posted by Gary Gregory <ga...@gmail.com>.
Giving up Java 7 works for me. It is not clear to me that the Jenkins
update does not support Java 7 at all though:
"If your Maven projects need to be built with JDK 7, consider converting
them to freestyle projects, or look into Maven toolchains."
We use Maven toolchains over at Log4j (for building some bits with Java 9)
and that works fine.
The business SSH slaves does not sound pretty though.
Travis-CI still supports Java 7 of course so we can go with that.
We just need to decide what matters for 5.0 and 4.6. Java 8 is OK here.
Gary
On Jun 27, 2017 04:22, "Oleg Kalnichevski" <ol...@apache.org> wrote:
Folks
ASF Jenkins will no longer support Java7 Maven projects soon. That
means there will be no way to reliably test Java 7 compatibility
anymore.
Maybe it is time we gave up on Java 7 compatibility altogether. By the
time 5.0.x projects go GA Java 7 may no longer matter.
What do you think?
Oleg
-------- Forwarded Message --------
From: Gavin McDonald <ga...@16degrees.com.au>
Reply-to: builds@apache.org
To: builds@apache.org
Cc: ASF Operations <op...@apache.org>
Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)
Date: Tue, 27 Jun 2017 17:03:13 +1000
...
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:-
“…2.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).
...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Time to give up on Java 7 compatibility? [Fwd: [JENKINS]
[IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)]
Posted by Oleg Kalnichevski <ol...@apache.org>.
Folks
ASF Jenkins will no longer support Java7 Maven projects soon. That
means there will be no way to reliably test Java 7 compatibility
anymore.
Maybe it is time we gave up on Java 7 compatibility altogether. By the
time 5.0.x projects go GA Java 7 may no longer matter.
What do you think?
Oleg
-------- Forwarded Message --------
From: Gavin McDonald <ga...@16degrees.com.au>
Reply-to: builds@apache.org
To: builds@apache.org
Cc: ASF Operations <op...@apache.org>
Subject: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And
JDK7 deprecation)
Date: Tue, 27 Jun 2017 17:03:13 +1000
...
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:-
“…2.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).
...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org