You are viewing a plain text version of this content. The canonical link for it is here.
Posted to builds@apache.org by Gav <gm...@apache.org> on 2016/07/29 11:03:59 UTC
Jenkins JDK Matrix - and consolidating of versions.
Hi All,
So 99% of our Jenkins build machines are now puppetised with our configs in
our Git repos.
Going forward this should make things easier to maintain the software (and
versions of) on the nodes.
I went through all the JDK drop down options available in the Jenkins UI
when
creating a build.The Confluence wiki page at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
lists all them all. When choosing a version to use I hope that this
information will
prove useful - any changes made we will keep this page upto date.
However, some are not currently installed on the new puppetised
slaves (on purpose) and others we intend to consolidate down to fewer
versions.
In contrast, we will be able to make newer release versions available
quicker.
Once we are done with the JDKs, we'll move on to Maven, and then the rest.
Ok to specifics,
First major change to get out of the way is the removal of the 'auto
install' JDK
versions. They overlap with installed versions and going forward we would
rather
manage installation via Puppet and roll them out to all slaves in one hit.
Looking at the table in the linked wiki page above, this means we'll be
removing
eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
To avoid confusion we'll also be removing the auto install 'latest1.6'
'latest1.7' and 'latest1.8' options.
The best options for 'latest' versions is the ones at the top of the table
'JDK 1.x (Latest)'
which are all installed on all nodes and managed via puppet.
I'll point out also that we have installed 'unlimited security' versions of
1.6,1.7,1.8 jdks.
Very recent addition is also that of the JDK 9 b128 Early Access Build. We
hope you enjoy
this addition and please do give feedback on this version to the builds@
mailing list so we can pass it on - but certainly do not plan to base your
releases on these 'ea' builds. I'll try my best to add new ea builds as
they come through.
Last ones to mention are the IBM and Harmony versions. I'm not sure how
much in use
these are so I'm holding off on installing these for now. Please do ask for
a specific version
if needed. I'll drop the from the UI in time.
I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
along with the auto install latest links. Please plan
on migrating your builds away from these versions before then.
Any follow questions, please do concentrate your email responses to the
builds@ mailing list.
Thanks!
Gav... (On behalf of the Infrastructure Team)
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Gav <ip...@gmail.com>.
On Tue, Aug 2, 2016 at 10:19 PM, Ismael Juma <is...@juma.me.uk> wrote:
> Hi,
>
> We had a couple of failed Kafka builds using JDK 1.8 (latest) where the JDK
> was not found:
>
> https://builds.apache.org/job/kafka-trunk-jdk8/793/
> https://builds.apache.org/job/kafka-trunk-jdk8/794/
>
> The JDK was found OK in the previous build:
>
> https://builds.apache.org/job/kafka-trunk-jdk8/792/
>
> Maybe a misconfiguration in "jenkins-test-24f"?
>
Yep the jenkins-test cloud image is awaiting a rebuild
Gav...
> Ismael
>
> On Mon, Aug 1, 2016 at 12:39 PM, Ismael Juma <is...@juma.me.uk> wrote:
>
> > Hi,
> >
> > On Mon, Aug 1, 2016 at 4:14 AM, Gav <gm...@apache.org> wrote:
> >
> >> JDK 1.4 (latest), JDK 1.5 (latest), JDK 1.6 (latest), JDK 1.7 (latest),
> >> JDK
> >> 1.8 (latest)
> >>
> >> All point to the very latest (and in some cases last) publically
> available
> >> release as of today.
> >
> >
> > Thanks for doing this, I have updated Kafka Jenkins builds to use JDK 1.7
> > (latest) and JDK 1.8 (latest).
> >
> > Ismael
> >
>
--
Gav...
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Ismael Juma <is...@juma.me.uk>.
Hi,
We had a couple of failed Kafka builds using JDK 1.8 (latest) where the JDK
was not found:
https://builds.apache.org/job/kafka-trunk-jdk8/793/
https://builds.apache.org/job/kafka-trunk-jdk8/794/
The JDK was found OK in the previous build:
https://builds.apache.org/job/kafka-trunk-jdk8/792/
Maybe a misconfiguration in "jenkins-test-24f"?
Ismael
On Mon, Aug 1, 2016 at 12:39 PM, Ismael Juma <is...@juma.me.uk> wrote:
> Hi,
>
> On Mon, Aug 1, 2016 at 4:14 AM, Gav <gm...@apache.org> wrote:
>
>> JDK 1.4 (latest), JDK 1.5 (latest), JDK 1.6 (latest), JDK 1.7 (latest),
>> JDK
>> 1.8 (latest)
>>
>> All point to the very latest (and in some cases last) publically available
>> release as of today.
>
>
> Thanks for doing this, I have updated Kafka Jenkins builds to use JDK 1.7
> (latest) and JDK 1.8 (latest).
>
> Ismael
>
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Ismael Juma <is...@juma.me.uk>.
Hi,
On Mon, Aug 1, 2016 at 4:14 AM, Gav <gm...@apache.org> wrote:
> JDK 1.4 (latest), JDK 1.5 (latest), JDK 1.6 (latest), JDK 1.7 (latest), JDK
> 1.8 (latest)
>
> All point to the very latest (and in some cases last) publically available
> release as of today.
Thanks for doing this, I have updated Kafka Jenkins builds to use JDK 1.7
(latest) and JDK 1.8 (latest).
Ismael
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Gav <gm...@apache.org>.
Hi again,
Just an update for you,
All symlinks labelled
JDK 1.4 (latest), JDK 1.5 (latest), JDK 1.6 (latest), JDK 1.7 (latest), JDK
1.8 (latest)
All point to the very latest (and in some cases last) publically available
release as of today.
See :
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
for accurate up to date information.
Enjoy.
Gav...
On Fri, Jul 29, 2016 at 9:03 PM, Gav <gm...@apache.org> wrote:
> Hi All,
>
> So 99% of our Jenkins build machines are now puppetised with our configs
> in our Git repos.
> Going forward this should make things easier to maintain the software (and
> versions of) on the nodes.
>
> I went through all the JDK drop down options available in the Jenkins UI
> when
> creating a build.The Confluence wiki page at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
>
> lists all them all. When choosing a version to use I hope that this
> information will
> prove useful - any changes made we will keep this page upto date.
> However, some are not currently installed on the new puppetised
> slaves (on purpose) and others we intend to consolidate down to fewer
> versions.
>
> In contrast, we will be able to make newer release versions available
> quicker.
>
> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>
> Ok to specifics,
>
> First major change to get out of the way is the removal of the 'auto
> install' JDK
> versions. They overlap with installed versions and going forward we would
> rather
> manage installation via Puppet and roll them out to all slaves in one hit.
>
> Looking at the table in the linked wiki page above, this means we'll be
> removing
> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> To avoid confusion we'll also be removing the auto install 'latest1.6'
> 'latest1.7' and 'latest1.8' options.
>
> The best options for 'latest' versions is the ones at the top of the table
> 'JDK 1.x (Latest)'
> which are all installed on all nodes and managed via puppet.
>
> I'll point out also that we have installed 'unlimited security' versions
> of 1.6,1.7,1.8 jdks.
>
> Very recent addition is also that of the JDK 9 b128 Early Access Build. We
> hope you enjoy
> this addition and please do give feedback on this version to the builds@
> mailing list so we can pass it on - but certainly do not plan to base your
> releases on these 'ea' builds. I'll try my best to add new ea builds as
> they come through.
>
> Last ones to mention are the IBM and Harmony versions. I'm not sure how
> much in use
> these are so I'm holding off on installing these for now. Please do ask
> for a specific version
> if needed. I'll drop the from the UI in time.
>
> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
> 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
> along with the auto install latest links. Please plan
> on migrating your builds away from these versions before then.
>
> Any follow questions, please do concentrate your email responses to the
> builds@ mailing list.
>
> Thanks!
>
> Gav... (On behalf of the Infrastructure Team)
>
>
Fwd: Jenkins JDK Matrix - and consolidating of versions.
Posted by Adina Crainiceanu <ad...@usna.edu>.
FYI: Since the Java labels on the Apache Jenkins were changed, I changed
our build incubator-rya-develop to use "JDK 1.8 (latest)" instead of
"latest 1.8". Last build completed without problems.
Adina
---------- Forwarded message ----------
From: Gav <gm...@apache.org>
Date: Thu, Aug 4, 2016 at 9:03 PM
Subject: Re: Jenkins JDK Matrix - and consolidating of versions.
To: builds <bu...@apache.org>, "infrastructure@apache.org Infrastructure" <
infrastructure@apache.org>
Hi all,
Please note that today is the day 7 days have past since the 7 days notice
that I said I was removing some
jenkins JDK drop down options.
Unfortunately a fair few projects have failed to move their builds to
another option.
Therefore I have extended by another 3 days only.
I have informed all PMCs just in case the rare scenario where a PMC has no
subscribers here.
Below you will find a list of all Jenkins Jobs still using the deprecated
drop down options.
Carefully check to see if your jobs are on the list and if so please take
action to change it.
Any jobs still on the old options after this time I WILL MIGRATE THEM
MYSELF !!!
HTH
Gav...
Project Jobs still using :-
'latest1.8'
=======
Accumulo-master-IT
ACE-trunk
ActiveMQ-Artemis-Deploy
ActiveMQ-Artemis-Master
ActiveMQ-Artemis-Nightly-Regression-Test
ActiveMQ-Artemis-PR-Build
Airavata
Ant_BuildFromPOMs
Ant_Nightly
Aries-rsa
Aries-rsa
Aries-Tx-Control-Deploy
Aries-Tx-Control-Trunk-JDK8
Calcite-Avatica-Master-JDK-1.8
Calcite-Master-JDK-1.8
Camel.trunk.fulltest.java8
Camel.trunk.itest.karaf
Camel.trunk.itest.osgi
Camel.trunk.notest
cayenne-31
Chemistry
cloudstack-marvin
cloudstack-pr-analysis
ctakes-trunk-compiletest
ctakes-trunk-package
CXF-trunk-deploy
CXF-Trunk-JDK18
CXF-Trunk-PR
DeltaSpike-PR-Builder
DeltaSpike_Wildfly_10.1
DeltaSpike_Wildfly_10
Derby-10.11-suites.All
Derby-10.12-suites.All
Derby-JaCoCo
Derby-trunk
Derby-trunk-JaCoCo
Derby-trunk-suites.All
Geode-nightly
Geode-nightly-copy
Geode-release
Geode-spark-connector
Groovy
hadoop-qbt-osx-java8
Hadoop-trunk-Commit
hadoop-trunk-osx-java8
hadoop-trunk-win-java8
HBase-1.1-JDK8
HBase-1.2
HBase-1.2-IT
HBase-1.3
HBase-1.3-IT
HBase-1.4
HBase-Trunk-IT
HBase-Trunk_matrix
incubator-eagle-develop
incubator-eagle-test
incubator-rya-develop
Jena_Development_Deploy
Jena_Development_Test
Jena_Development_Test_Windows
johnzon-multi
joshua_master
karaf-pr
Lucene-Artifacts-6.x
Lucene-Artifacts-master
Lucene-Solr-Clover-6.x
Lucene-Solr-Clover-master
Lucene-Solr-Maven-6.x
Lucene-Solr-Maven-master
Lucene-Solr-NightlyTests-6.x
Lucene-Solr-NightlyTests-master
Lucene-Solr-SmokeRelease-6.0
Lucene-Solr-SmokeRelease-6.1
Lucene-Solr-SmokeRelease-6.x
Lucene-Solr-SmokeRelease-master
Lucene-Solr-Tests-5.5-Java8
Lucene-Solr-Tests-6.x
Lucene-Solr-Tests-master
Lucene-Tests-MMAP-master
maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8_windows
MINA-trunk-jdk1.8-ubuntu
MINA-trunk-jdk1.8-windows
olingo-odata4-all-profiles
olingo-odata4-cobertura
olingo-odata4
Precommit-HADOOP-OSX
PreCommit-TAJO-Build
River-dev-jdk8
river-JoinManagerTests
river-JRMPactivationTests
river-LeaseTests
river-LookupServiceTests
river-PolicySecurityLoaderUrlTests
river-ReliabilityThreadTests
river-ServiceDiscoveryManagerTests
river-StartConfigIoIdExport
river-TransactionTests
ServiceMix-6.x
ServiceMix-master
ServiceMix-pr
Solr-Artifacts-6.x
Solr-Artifacts-master
Struts-JDK8-master
Struts-JDK9-master
Tajo-master-nightly
tinkerpop-master
Tobago
UIMAJ-SDK_java8
ZooKeeper_branch35_jdk8
'latest1.7'
=======
Ambari-branch-1.7.0
Ambari-branch-2.0.0
Ambari-branch-2.1
Ambari-branch-2.2
Ambari-trunk-Commit
Ambari-trunk-Commit-debug
Ambari-trunk-test-patch
Ambari-view
brooklyn-master-windows
Camel.2.15.x.fulltest
Curator-3.0
CXF-3.1.x
DeltaSpike
Empire-db
Empire-db
Felix-Connect
Felix-FileInstall
flex-falcon-w2012-test
Geode-trunk-test-patch
Geronimo
Giraph-trunk-Commit
Groovy
Groovy
HADOOP2_Release_Artifacts_Builder
HBase-0.98-matrix
HBase-1.2
HBase-1.2-IT
HBase-1.3
HBase-1.3-IT
HBase-1.4
HBase-Trunk-IT
HBase-Trunk_matrix
incubator-eagle-main
JMeter-trunk
JMeter-Windows
johnzon-multi
Lucene-Solr-Tests-5.5-Java7
maven-plugins
maven-plugins-ITs-m3.0.4
olingo-odata2
PreCommit-SQOOP-Build
PreCommit-ZOOKEEPER-Build
Qpid-Java-Cpp-Test
Qpid-JMS-Deploy
Qpid-proton-c
Reef-pull-request-ubuntu
samza-freestyle-build
Sqoop2-cobertura
Sqoop2
Sqoop-hadoop100
Sqoop-hadoop200
Sqoop-hadoop20
Sqoop-hadoop23
Struts-archetypes-JDK7-master
Struts-JDK7-master
Tamaya-Javadoc-Master
Tamaya-Master-branch
Tamaya-Site-Master
UIMA-AS
UIMA-SDK
UIMA-uimaFIT
ZooKeeper_branch34_jdk7
ZooKeeper_branch35_jdk7
ZooKeeper-trunk
ZooKeeper-trunk-solaris
'latest1.6'
=======
Groovy**
HBase-0.98-matrix
johnzon-multi
PreCommit-PIG-Build
'1.8.0_05'
=======
ActiveMQ-Java8
archiva-master-jdk-1.8
PreCommit-Lens-Build
PreCommit-Lens-Build
'1.8.0_11'
=======
Apache**
Geronimo-Specs-trunk
'1.8.0_66'
=======
AuroraBot
Aurora
Axis2
beam_PostCommit_MavenVerify
beam_PostCommit_PythonVerify
beam_PostCommit_RunnableOnService_FlinkLocal
beam_PostCommit_RunnableOnService_GearpumpLocal
beam_PostCommit_RunnableOnService_GoogleCloudDataflow
beam_PostCommit_RunnableOnService_SparkLocal
beam_PreCommit_MavenVerify
beam_Release_NightlySnapshot
bookkeeper-master
build-incubator-atlas*
CarbonData-master
Cassandra-artifacts
Cassandra-test-all
Cassandra-test-burn
Cassandra-test-cdc
Cassandra-test-compression
Cassandra-test
Chukwa-master
Commons-CRYPTO-JDK1.7
Commons-CRYPTO-JDK1.8
Commons-CRYPTO-JDK1.8
distributedlog-nightly-build
flink-github-ci
flink-snapshot-deployment
Fluo**
incubator-eagle-pr-reviewer
karaf-4.0.x
karaf-master
Nutch-nutchgora
Nutch-nutchgora
PreCommit-Lens-Build
samza-build-post-commit
sis-dev
Struts-examples-JDK8-master
tika-2.x-windows
Tobago**
wss4j-trunk
--end list
On Fri, Jul 29, 2016 at 9:03 PM, Gav <gm...@apache.org> wrote:
> Hi All,
>
> So 99% of our Jenkins build machines are now puppetised with our configs
> in our Git repos.
> Going forward this should make things easier to maintain the software (and
> versions of) on the nodes.
>
> I went through all the JDK drop down options available in the Jenkins UI
> when
> creating a build.The Confluence wiki page at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
>
> lists all them all. When choosing a version to use I hope that this
> information will
> prove useful - any changes made we will keep this page upto date.
> However, some are not currently installed on the new puppetised
> slaves (on purpose) and others we intend to consolidate down to fewer
> versions.
>
> In contrast, we will be able to make newer release versions available
> quicker.
>
> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>
> Ok to specifics,
>
> First major change to get out of the way is the removal of the 'auto
> install' JDK
> versions. They overlap with installed versions and going forward we would
> rather
> manage installation via Puppet and roll them out to all slaves in one hit.
>
> Looking at the table in the linked wiki page above, this means we'll be
> removing
> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> To avoid confusion we'll also be removing the auto install 'latest1.6'
> 'latest1.7' and 'latest1.8' options.
>
> The best options for 'latest' versions is the ones at the top of the table
> 'JDK 1.x (Latest)'
> which are all installed on all nodes and managed via puppet.
>
> I'll point out also that we have installed 'unlimited security' versions
> of 1.6,1.7,1.8 jdks.
>
> Very recent addition is also that of the JDK 9 b128 Early Access Build. We
> hope you enjoy
> this addition and please do give feedback on this version to the builds@
> mailing list so we can pass it on - but certainly do not plan to base your
> releases on these 'ea' builds. I'll try my best to add new ea builds as
> they come through.
>
> Last ones to mention are the IBM and Harmony versions. I'm not sure how
> much in use
> these are so I'm holding off on installing these for now. Please do ask
> for a specific version
> if needed. I'll drop the from the UI in time.
>
> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
> 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
> along with the auto install latest links. Please plan
> on migrating your builds away from these versions before then.
>
> Any follow questions, please do concentrate your email responses to the
> builds@ mailing list.
>
> Thanks!
>
> Gav... (On behalf of the Infrastructure Team)
>
>
--
Dr. Adina Crainiceanu
Associate Professor, Computer Science Department
United States Naval Academy
410-293-6822
adina@usna.edu
http://www.usna.edu/Users/cs/adina/
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Sean Busbey <bu...@apache.org>.
Hi Gav!
I updated all of the HBase related builds to use the 'JDK 1.x (latest)' labels for JDK selection, but now we have several multiple-configuration builds that fail.
One of our community members tracked it down to the addition of spaces (and perhaps parens?) used in the JDK names, since these end up in the path of the working directory during multi-configuration builds where JDK version is one of the test axes.
Any chance we could consolidate on JDK labels that don't have characters that are problematic, like spaces and parens?
-busbey
On 2016-08-04 20:03 (-0500), Gav <gm...@apache.org> wrote:
> Hi all,
>
> Please note that today is the day 7 days have past since the 7 days notice
> that I said I was removing some
> jenkins JDK drop down options.
>
> Unfortunately a fair few projects have failed to move their builds to
> another option.
>
> Therefore I have extended by another 3 days only.
>
> I have informed all PMCs just in case the rare scenario where a PMC has no
> subscribers here.
>
> Below you will find a list of all Jenkins Jobs still using the deprecated
> drop down options.
>
> Carefully check to see if your jobs are on the list and if so please take
> action to change it.
>
> Any jobs still on the old options after this time I WILL MIGRATE THEM
> MYSELF !!!
>
> HTH
>
> Gav...
>
> Project Jobs still using :-
>
> 'latest1.8'
> =======
>
> Accumulo-master-IT
> ACE-trunk
> ActiveMQ-Artemis-Deploy
> ActiveMQ-Artemis-Master
> ActiveMQ-Artemis-Nightly-Regression-Test
> ActiveMQ-Artemis-PR-Build
> Airavata
> Ant_BuildFromPOMs
> Ant_Nightly
> Aries-rsa
> Aries-rsa
> Aries-Tx-Control-Deploy
> Aries-Tx-Control-Trunk-JDK8
> Calcite-Avatica-Master-JDK-1.8
> Calcite-Master-JDK-1.8
> Camel.trunk.fulltest.java8
> Camel.trunk.itest.karaf
> Camel.trunk.itest.osgi
> Camel.trunk.notest
> cayenne-31
> Chemistry
> cloudstack-marvin
> cloudstack-pr-analysis
> ctakes-trunk-compiletest
> ctakes-trunk-package
> CXF-trunk-deploy
> CXF-Trunk-JDK18
> CXF-Trunk-PR
> DeltaSpike-PR-Builder
> DeltaSpike_Wildfly_10.1
> DeltaSpike_Wildfly_10
> Derby-10.11-suites.All
> Derby-10.12-suites.All
> Derby-JaCoCo
> Derby-trunk
> Derby-trunk-JaCoCo
> Derby-trunk-suites.All
> Geode-nightly
> Geode-nightly-copy
> Geode-release
> Geode-spark-connector
> Groovy
> hadoop-qbt-osx-java8
> Hadoop-trunk-Commit
> hadoop-trunk-osx-java8
> hadoop-trunk-win-java8
> HBase-1.1-JDK8
> HBase-1.2
> HBase-1.2-IT
> HBase-1.3
> HBase-1.3-IT
> HBase-1.4
> HBase-Trunk-IT
> HBase-Trunk_matrix
> incubator-eagle-develop
> incubator-eagle-test
> incubator-rya-develop
> Jena_Development_Deploy
> Jena_Development_Test
> Jena_Development_Test_Windows
> johnzon-multi
> joshua_master
> karaf-pr
> Lucene-Artifacts-6.x
> Lucene-Artifacts-master
> Lucene-Solr-Clover-6.x
> Lucene-Solr-Clover-master
> Lucene-Solr-Maven-6.x
> Lucene-Solr-Maven-master
> Lucene-Solr-NightlyTests-6.x
> Lucene-Solr-NightlyTests-master
> Lucene-Solr-SmokeRelease-6.0
> Lucene-Solr-SmokeRelease-6.1
> Lucene-Solr-SmokeRelease-6.x
> Lucene-Solr-SmokeRelease-master
> Lucene-Solr-Tests-5.5-Java8
> Lucene-Solr-Tests-6.x
> Lucene-Solr-Tests-master
> Lucene-Tests-MMAP-master
> maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8_windows
> MINA-trunk-jdk1.8-ubuntu
> MINA-trunk-jdk1.8-windows
> olingo-odata4-all-profiles
> olingo-odata4-cobertura
> olingo-odata4
> Precommit-HADOOP-OSX
> PreCommit-TAJO-Build
> River-dev-jdk8
> river-JoinManagerTests
> river-JRMPactivationTests
> river-LeaseTests
> river-LookupServiceTests
> river-PolicySecurityLoaderUrlTests
> river-ReliabilityThreadTests
> river-ServiceDiscoveryManagerTests
> river-StartConfigIoIdExport
> river-TransactionTests
> ServiceMix-6.x
> ServiceMix-master
> ServiceMix-pr
> Solr-Artifacts-6.x
> Solr-Artifacts-master
> Struts-JDK8-master
> Struts-JDK9-master
> Tajo-master-nightly
> tinkerpop-master
> Tobago
> UIMAJ-SDK_java8
> ZooKeeper_branch35_jdk8
>
> 'latest1.7'
> =======
>
> Ambari-branch-1.7.0
> Ambari-branch-2.0.0
> Ambari-branch-2.1
> Ambari-branch-2.2
> Ambari-trunk-Commit
> Ambari-trunk-Commit-debug
> Ambari-trunk-test-patch
> Ambari-view
> brooklyn-master-windows
> Camel.2.15.x.fulltest
> Curator-3.0
> CXF-3.1.x
> DeltaSpike
> Empire-db
> Empire-db
> Felix-Connect
> Felix-FileInstall
> flex-falcon-w2012-test
> Geode-trunk-test-patch
> Geronimo
> Giraph-trunk-Commit
> Groovy
> Groovy
> HADOOP2_Release_Artifacts_Builder
> HBase-0.98-matrix
> HBase-1.2
> HBase-1.2-IT
> HBase-1.3
> HBase-1.3-IT
> HBase-1.4
> HBase-Trunk-IT
> HBase-Trunk_matrix
> incubator-eagle-main
> JMeter-trunk
> JMeter-Windows
> johnzon-multi
> Lucene-Solr-Tests-5.5-Java7
> maven-plugins
> maven-plugins-ITs-m3.0.4
> olingo-odata2
> PreCommit-SQOOP-Build
> PreCommit-ZOOKEEPER-Build
> Qpid-Java-Cpp-Test
> Qpid-JMS-Deploy
> Qpid-proton-c
> Reef-pull-request-ubuntu
> samza-freestyle-build
> Sqoop2-cobertura
> Sqoop2
> Sqoop-hadoop100
> Sqoop-hadoop200
> Sqoop-hadoop20
> Sqoop-hadoop23
> Struts-archetypes-JDK7-master
> Struts-JDK7-master
> Tamaya-Javadoc-Master
> Tamaya-Master-branch
> Tamaya-Site-Master
> UIMA-AS
> UIMA-SDK
> UIMA-uimaFIT
> ZooKeeper_branch34_jdk7
> ZooKeeper_branch35_jdk7
> ZooKeeper-trunk
> ZooKeeper-trunk-solaris
>
> 'latest1.6'
> =======
>
> Groovy**
> HBase-0.98-matrix
> johnzon-multi
> PreCommit-PIG-Build
>
> '1.8.0_05'
> =======
>
> ActiveMQ-Java8
> archiva-master-jdk-1.8
> PreCommit-Lens-Build
> PreCommit-Lens-Build
>
> '1.8.0_11'
> =======
>
> Apache**
> Geronimo-Specs-trunk
>
> '1.8.0_66'
> =======
>
> AuroraBot
> Aurora
> Axis2
> beam_PostCommit_MavenVerify
> beam_PostCommit_PythonVerify
> beam_PostCommit_RunnableOnService_FlinkLocal
> beam_PostCommit_RunnableOnService_GearpumpLocal
> beam_PostCommit_RunnableOnService_GoogleCloudDataflow
> beam_PostCommit_RunnableOnService_SparkLocal
> beam_PreCommit_MavenVerify
> beam_Release_NightlySnapshot
> bookkeeper-master
> build-incubator-atlas*
> CarbonData-master
> Cassandra-artifacts
> Cassandra-test-all
> Cassandra-test-burn
> Cassandra-test-cdc
> Cassandra-test-compression
> Cassandra-test
> Chukwa-master
> Commons-CRYPTO-JDK1.7
> Commons-CRYPTO-JDK1.8
> Commons-CRYPTO-JDK1.8
> distributedlog-nightly-build
> flink-github-ci
> flink-snapshot-deployment
> Fluo**
> incubator-eagle-pr-reviewer
> karaf-4.0.x
> karaf-master
> Nutch-nutchgora
> Nutch-nutchgora
> PreCommit-Lens-Build
> samza-build-post-commit
> sis-dev
> Struts-examples-JDK8-master
> tika-2.x-windows
> Tobago**
> wss4j-trunk
>
> --end list
>
>
>
>
> On Fri, Jul 29, 2016 at 9:03 PM, Gav <gm...@apache.org> wrote:
>
> > Hi All,
> >
> > So 99% of our Jenkins build machines are now puppetised with our configs
> > in our Git repos.
> > Going forward this should make things easier to maintain the software (and
> > versions of) on the nodes.
> >
> > I went through all the JDK drop down options available in the Jenkins UI
> > when
> > creating a build.The Confluence wiki page at :-
> >
> > https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
> >
> > lists all them all. When choosing a version to use I hope that this
> > information will
> > prove useful - any changes made we will keep this page upto date.
> > However, some are not currently installed on the new puppetised
> > slaves (on purpose) and others we intend to consolidate down to fewer
> > versions.
> >
> > In contrast, we will be able to make newer release versions available
> > quicker.
> >
> > Once we are done with the JDKs, we'll move on to Maven, and then the rest.
> >
> > Ok to specifics,
> >
> > First major change to get out of the way is the removal of the 'auto
> > install' JDK
> > versions. They overlap with installed versions and going forward we would
> > rather
> > manage installation via Puppet and roll them out to all slaves in one hit.
> >
> > Looking at the table in the linked wiki page above, this means we'll be
> > removing
> > eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> > To avoid confusion we'll also be removing the auto install 'latest1.6'
> > 'latest1.7' and 'latest1.8' options.
> >
> > The best options for 'latest' versions is the ones at the top of the table
> > 'JDK 1.x (Latest)'
> > which are all installed on all nodes and managed via puppet.
> >
> > I'll point out also that we have installed 'unlimited security' versions
> > of 1.6,1.7,1.8 jdks.
> >
> > Very recent addition is also that of the JDK 9 b128 Early Access Build. We
> > hope you enjoy
> > this addition and please do give feedback on this version to the builds@
> > mailing list so we can pass it on - but certainly do not plan to base your
> > releases on these 'ea' builds. I'll try my best to add new ea builds as
> > they come through.
> >
> > Last ones to mention are the IBM and Harmony versions. I'm not sure how
> > much in use
> > these are so I'm holding off on installing these for now. Please do ask
> > for a specific version
> > if needed. I'll drop the from the UI in time.
> >
> > I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
> > 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
> > along with the auto install latest links. Please plan
> > on migrating your builds away from these versions before then.
> >
> > Any follow questions, please do concentrate your email responses to the
> > builds@ mailing list.
> >
> > Thanks!
> >
> > Gav... (On behalf of the Infrastructure Team)
> >
> >
>
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Gav <gm...@apache.org>.
Hi all,
Please note that today is the day 7 days have past since the 7 days notice
that I said I was removing some
jenkins JDK drop down options.
Unfortunately a fair few projects have failed to move their builds to
another option.
Therefore I have extended by another 3 days only.
I have informed all PMCs just in case the rare scenario where a PMC has no
subscribers here.
Below you will find a list of all Jenkins Jobs still using the deprecated
drop down options.
Carefully check to see if your jobs are on the list and if so please take
action to change it.
Any jobs still on the old options after this time I WILL MIGRATE THEM
MYSELF !!!
HTH
Gav...
Project Jobs still using :-
'latest1.8'
=======
Accumulo-master-IT
ACE-trunk
ActiveMQ-Artemis-Deploy
ActiveMQ-Artemis-Master
ActiveMQ-Artemis-Nightly-Regression-Test
ActiveMQ-Artemis-PR-Build
Airavata
Ant_BuildFromPOMs
Ant_Nightly
Aries-rsa
Aries-rsa
Aries-Tx-Control-Deploy
Aries-Tx-Control-Trunk-JDK8
Calcite-Avatica-Master-JDK-1.8
Calcite-Master-JDK-1.8
Camel.trunk.fulltest.java8
Camel.trunk.itest.karaf
Camel.trunk.itest.osgi
Camel.trunk.notest
cayenne-31
Chemistry
cloudstack-marvin
cloudstack-pr-analysis
ctakes-trunk-compiletest
ctakes-trunk-package
CXF-trunk-deploy
CXF-Trunk-JDK18
CXF-Trunk-PR
DeltaSpike-PR-Builder
DeltaSpike_Wildfly_10.1
DeltaSpike_Wildfly_10
Derby-10.11-suites.All
Derby-10.12-suites.All
Derby-JaCoCo
Derby-trunk
Derby-trunk-JaCoCo
Derby-trunk-suites.All
Geode-nightly
Geode-nightly-copy
Geode-release
Geode-spark-connector
Groovy
hadoop-qbt-osx-java8
Hadoop-trunk-Commit
hadoop-trunk-osx-java8
hadoop-trunk-win-java8
HBase-1.1-JDK8
HBase-1.2
HBase-1.2-IT
HBase-1.3
HBase-1.3-IT
HBase-1.4
HBase-Trunk-IT
HBase-Trunk_matrix
incubator-eagle-develop
incubator-eagle-test
incubator-rya-develop
Jena_Development_Deploy
Jena_Development_Test
Jena_Development_Test_Windows
johnzon-multi
joshua_master
karaf-pr
Lucene-Artifacts-6.x
Lucene-Artifacts-master
Lucene-Solr-Clover-6.x
Lucene-Solr-Clover-master
Lucene-Solr-Maven-6.x
Lucene-Solr-Maven-master
Lucene-Solr-NightlyTests-6.x
Lucene-Solr-NightlyTests-master
Lucene-Solr-SmokeRelease-6.0
Lucene-Solr-SmokeRelease-6.1
Lucene-Solr-SmokeRelease-6.x
Lucene-Solr-SmokeRelease-master
Lucene-Solr-Tests-5.5-Java8
Lucene-Solr-Tests-6.x
Lucene-Solr-Tests-master
Lucene-Tests-MMAP-master
maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8_windows
MINA-trunk-jdk1.8-ubuntu
MINA-trunk-jdk1.8-windows
olingo-odata4-all-profiles
olingo-odata4-cobertura
olingo-odata4
Precommit-HADOOP-OSX
PreCommit-TAJO-Build
River-dev-jdk8
river-JoinManagerTests
river-JRMPactivationTests
river-LeaseTests
river-LookupServiceTests
river-PolicySecurityLoaderUrlTests
river-ReliabilityThreadTests
river-ServiceDiscoveryManagerTests
river-StartConfigIoIdExport
river-TransactionTests
ServiceMix-6.x
ServiceMix-master
ServiceMix-pr
Solr-Artifacts-6.x
Solr-Artifacts-master
Struts-JDK8-master
Struts-JDK9-master
Tajo-master-nightly
tinkerpop-master
Tobago
UIMAJ-SDK_java8
ZooKeeper_branch35_jdk8
'latest1.7'
=======
Ambari-branch-1.7.0
Ambari-branch-2.0.0
Ambari-branch-2.1
Ambari-branch-2.2
Ambari-trunk-Commit
Ambari-trunk-Commit-debug
Ambari-trunk-test-patch
Ambari-view
brooklyn-master-windows
Camel.2.15.x.fulltest
Curator-3.0
CXF-3.1.x
DeltaSpike
Empire-db
Empire-db
Felix-Connect
Felix-FileInstall
flex-falcon-w2012-test
Geode-trunk-test-patch
Geronimo
Giraph-trunk-Commit
Groovy
Groovy
HADOOP2_Release_Artifacts_Builder
HBase-0.98-matrix
HBase-1.2
HBase-1.2-IT
HBase-1.3
HBase-1.3-IT
HBase-1.4
HBase-Trunk-IT
HBase-Trunk_matrix
incubator-eagle-main
JMeter-trunk
JMeter-Windows
johnzon-multi
Lucene-Solr-Tests-5.5-Java7
maven-plugins
maven-plugins-ITs-m3.0.4
olingo-odata2
PreCommit-SQOOP-Build
PreCommit-ZOOKEEPER-Build
Qpid-Java-Cpp-Test
Qpid-JMS-Deploy
Qpid-proton-c
Reef-pull-request-ubuntu
samza-freestyle-build
Sqoop2-cobertura
Sqoop2
Sqoop-hadoop100
Sqoop-hadoop200
Sqoop-hadoop20
Sqoop-hadoop23
Struts-archetypes-JDK7-master
Struts-JDK7-master
Tamaya-Javadoc-Master
Tamaya-Master-branch
Tamaya-Site-Master
UIMA-AS
UIMA-SDK
UIMA-uimaFIT
ZooKeeper_branch34_jdk7
ZooKeeper_branch35_jdk7
ZooKeeper-trunk
ZooKeeper-trunk-solaris
'latest1.6'
=======
Groovy**
HBase-0.98-matrix
johnzon-multi
PreCommit-PIG-Build
'1.8.0_05'
=======
ActiveMQ-Java8
archiva-master-jdk-1.8
PreCommit-Lens-Build
PreCommit-Lens-Build
'1.8.0_11'
=======
Apache**
Geronimo-Specs-trunk
'1.8.0_66'
=======
AuroraBot
Aurora
Axis2
beam_PostCommit_MavenVerify
beam_PostCommit_PythonVerify
beam_PostCommit_RunnableOnService_FlinkLocal
beam_PostCommit_RunnableOnService_GearpumpLocal
beam_PostCommit_RunnableOnService_GoogleCloudDataflow
beam_PostCommit_RunnableOnService_SparkLocal
beam_PreCommit_MavenVerify
beam_Release_NightlySnapshot
bookkeeper-master
build-incubator-atlas*
CarbonData-master
Cassandra-artifacts
Cassandra-test-all
Cassandra-test-burn
Cassandra-test-cdc
Cassandra-test-compression
Cassandra-test
Chukwa-master
Commons-CRYPTO-JDK1.7
Commons-CRYPTO-JDK1.8
Commons-CRYPTO-JDK1.8
distributedlog-nightly-build
flink-github-ci
flink-snapshot-deployment
Fluo**
incubator-eagle-pr-reviewer
karaf-4.0.x
karaf-master
Nutch-nutchgora
Nutch-nutchgora
PreCommit-Lens-Build
samza-build-post-commit
sis-dev
Struts-examples-JDK8-master
tika-2.x-windows
Tobago**
wss4j-trunk
--end list
On Fri, Jul 29, 2016 at 9:03 PM, Gav <gm...@apache.org> wrote:
> Hi All,
>
> So 99% of our Jenkins build machines are now puppetised with our configs
> in our Git repos.
> Going forward this should make things easier to maintain the software (and
> versions of) on the nodes.
>
> I went through all the JDK drop down options available in the Jenkins UI
> when
> creating a build.The Confluence wiki page at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
>
> lists all them all. When choosing a version to use I hope that this
> information will
> prove useful - any changes made we will keep this page upto date.
> However, some are not currently installed on the new puppetised
> slaves (on purpose) and others we intend to consolidate down to fewer
> versions.
>
> In contrast, we will be able to make newer release versions available
> quicker.
>
> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>
> Ok to specifics,
>
> First major change to get out of the way is the removal of the 'auto
> install' JDK
> versions. They overlap with installed versions and going forward we would
> rather
> manage installation via Puppet and roll them out to all slaves in one hit.
>
> Looking at the table in the linked wiki page above, this means we'll be
> removing
> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> To avoid confusion we'll also be removing the auto install 'latest1.6'
> 'latest1.7' and 'latest1.8' options.
>
> The best options for 'latest' versions is the ones at the top of the table
> 'JDK 1.x (Latest)'
> which are all installed on all nodes and managed via puppet.
>
> I'll point out also that we have installed 'unlimited security' versions
> of 1.6,1.7,1.8 jdks.
>
> Very recent addition is also that of the JDK 9 b128 Early Access Build. We
> hope you enjoy
> this addition and please do give feedback on this version to the builds@
> mailing list so we can pass it on - but certainly do not plan to base your
> releases on these 'ea' builds. I'll try my best to add new ea builds as
> they come through.
>
> Last ones to mention are the IBM and Harmony versions. I'm not sure how
> much in use
> these are so I'm holding off on installing these for now. Please do ask
> for a specific version
> if needed. I'll drop the from the UI in time.
>
> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
> 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
> along with the auto install latest links. Please plan
> on migrating your builds away from these versions before then.
>
> Any follow questions, please do concentrate your email responses to the
> builds@ mailing list.
>
> Thanks!
>
> Gav... (On behalf of the Infrastructure Team)
>
>
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Gav <gm...@apache.org>.
Hi,
On Sat, Jul 30, 2016 at 4:41 AM, Uwe Schindler <us...@apache.org>
wrote:
> Hi,
>
>
>
> in addition, the „JDK 7 (latest)“ according to the installation matrix is
> too old and buggy. Lucene is known to be broken with those old JDK versions
> (we require from our users to user later versions, the minimum is JDK 7u65
> for the Lucene 5 branch).
>
>
>
> JDK 8 (latest) is fine as its rather new.
>
>
>
> Could you use the recent JDK 7u90 builds like the “deprecated” latest1.7
> builds. Or did I misunderstood the term “latest”? J
>
You understood correct, I do need to go over them all still.
I have installed the jdk1.7.0_80 which is the last release.
HTH
Gav...
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> uschindler@apache.org
>
> ASF Member, Apache Lucene PMC / Committer
>
> Bremen, Germany
>
> http://lucene.apache.org/
>
>
>
> *From:* Uwe Schindler [mailto:uschindler@apache.org]
> *Sent:* Friday, July 29, 2016 8:31 PM
> *To:* dev@lucene.apache.org
> *Cc:* gmcdonald@apache.org; infrastructure@apache.org
> *Subject:* RE: Jenkins JDK Matrix - and consolidating of versions.
>
>
>
> Hi,
>
>
>
> after changing the setup of the Lucene Jobs, we get all jobs failing with
> „JAVA_HOME“ not correctly defined:
>
>
>
> https://builds.apache.org/job/Lucene-Solr-Tests-master/1290/console
>
>
>
> This affects the “lucene” Jenkins node. Maybe the puppet was not correctly
> activated there. We need” JDK 1.7 (latest)” and “JDK 1.8 (latest)” on this
> machine.
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> uschindler@apache.org
>
> ASF Member, Apache Lucene PMC / Committer
>
> Bremen, Germany
>
> http://lucene.apache.org/
>
>
>
> *From:* Steve Rowe [mailto:sarowe@gmail.com <sa...@gmail.com>]
> *Sent:* Friday, July 29, 2016 2:38 PM
> *To:* Lucene Dev <de...@lucene.apache.org>
> *Subject:* Fwd: Jenkins JDK Matrix - and consolidating of versions.
>
>
>
> FYI, I switched all Lucene/Solr ASF Jenkins jobs’ configuration from
> “latest1.8” to “JDK 1.8 (latest)” (except for the 5.5 branch Java7 build,
> which I switched from "latest1.7” to “JDK 1.7 (latest)”) - more info below.
>
>
>
> --
>
> Steve
>
> www.lucidworks.com
>
>
>
> Begin forwarded message:
>
>
>
> *From: *Gav <gm...@apache.org>
>
> *Subject: Jenkins JDK Matrix - and consolidating of versions.*
>
> *Date: *July 29, 2016 at 7:03:59 AM EDT
>
> *To: *builds@apache.org, "infrastructure@apache.org Infrastructure" <
> infrastructure@apache.org>
>
> *Reply-To: *gmcdonald@apache.org
>
>
>
> Hi All,
>
> So 99% of our Jenkins build machines are now puppetised with our configs
> in our Git repos.
> Going forward this should make things easier to maintain the software (and
> versions of) on the nodes.
>
>
>
> I went through all the JDK drop down options available in the Jenkins UI
> when
>
> creating a build.The Confluence wiki page at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
>
> lists all them all. When choosing a version to use I hope that this
> information will
> prove useful - any changes made we will keep this page upto date.
> However, some are not currently installed on the new puppetised
>
> slaves (on purpose) and others we intend to consolidate down to fewer
> versions.
>
> In contrast, we will be able to make newer release versions available
> quicker.
>
> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>
> Ok to specifics,
>
> First major change to get out of the way is the removal of the 'auto
> install' JDK
>
> versions. They overlap with installed versions and going forward we would
> rather
>
> manage installation via Puppet and roll them out to all slaves in one hit.
>
> Looking at the table in the linked wiki page above, this means we'll be
> removing
>
> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> To avoid confusion we'll also be removing the auto install 'latest1.6'
> 'latest1.7' and 'latest1.8' options.
>
> The best options for 'latest' versions is the ones at the top of the table
> 'JDK 1.x (Latest)'
> which are all installed on all nodes and managed via puppet.
>
> I'll point out also that we have installed 'unlimited security' versions
> of 1.6,1.7,1.8 jdks.
>
> Very recent addition is also that of the JDK 9 b128 Early Access Build. We
> hope you enjoy
>
> this addition and please do give feedback on this version to the builds@
> mailing list so we can pass it on - but certainly do not plan to base your
> releases on these 'ea' builds. I'll try my best to add new ea builds as
> they come through.
>
> Last ones to mention are the IBM and Harmony versions. I'm not sure how
> much in use
>
> these are so I'm holding off on installing these for now. Please do ask
> for a specific version
>
> if needed. I'll drop the from the UI in time.
>
> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
> 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
> along with the auto install latest links. Please plan
>
> on migrating your builds away from these versions before then.
>
> Any follow questions, please do concentrate your email responses to the
> builds@ mailing list.
>
> Thanks!
>
> Gav... (On behalf of the Infrastructure Team)
>
>
>
RE: Jenkins JDK Matrix - and consolidating of versions.
Posted by Uwe Schindler <us...@apache.org>.
Hi,
in addition, the „JDK 7 (latest)“ according to the installation matrix is too old and buggy. Lucene is known to be broken with those old JDK versions (we require from our users to user later versions, the minimum is JDK 7u65 for the Lucene 5 branch).
JDK 8 (latest) is fine as its rather new.
Could you use the recent JDK 7u90 builds like the “deprecated” latest1.7 builds. Or did I misunderstood the term “latest”? :)
Uwe
-----
Uwe Schindler
uschindler@apache.org
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
http://lucene.apache.org/
From: Uwe Schindler [mailto:uschindler@apache.org]
Sent: Friday, July 29, 2016 8:31 PM
To: dev@lucene.apache.org
Cc: gmcdonald@apache.org; infrastructure@apache.org
Subject: RE: Jenkins JDK Matrix - and consolidating of versions.
Hi,
after changing the setup of the Lucene Jobs, we get all jobs failing with „JAVA_HOME“ not correctly defined:
https://builds.apache.org/job/Lucene-Solr-Tests-master/1290/console
This affects the “lucene” Jenkins node. Maybe the puppet was not correctly activated there. We need” JDK 1.7 (latest)” and “JDK 1.8 (latest)” on this machine.
Uwe
-----
Uwe Schindler
uschindler@apache.org <ma...@apache.org>
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
<http://lucene.apache.org/> http://lucene.apache.org/
From: Steve Rowe [ <ma...@gmail.com> mailto:sarowe@gmail.com]
Sent: Friday, July 29, 2016 2:38 PM
To: Lucene Dev < <ma...@lucene.apache.org> dev@lucene.apache.org>
Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
FYI, I switched all Lucene/Solr ASF Jenkins jobs’ configuration from “latest1.8” to “JDK 1.8 (latest)” (except for the 5.5 branch Java7 build, which I switched from "latest1.7” to “JDK 1.7 (latest)”) - more info below.
--
Steve
www.lucidworks.com <http://www.lucidworks.com>
Begin forwarded message:
From: Gav <gmcdonald@apache.org <ma...@apache.org> >
Subject: Jenkins JDK Matrix - and consolidating of versions.
Date: July 29, 2016 at 7:03:59 AM EDT
To: builds@apache.org <ma...@apache.org> , "infrastructure@apache.org <ma...@apache.org> Infrastructure" <infrastructure@apache.org <ma...@apache.org> >
Reply-To: gmcdonald@apache.org <ma...@apache.org>
Hi All,
So 99% of our Jenkins build machines are now puppetised with our configs in our Git repos.
Going forward this should make things easier to maintain the software (and versions of) on the nodes.
I went through all the JDK drop down options available in the Jenkins UI when
creating a build.The Confluence wiki page at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
lists all them all. When choosing a version to use I hope that this information will
prove useful - any changes made we will keep this page upto date.
However, some are not currently installed on the new puppetised
slaves (on purpose) and others we intend to consolidate down to fewer versions.
In contrast, we will be able to make newer release versions available quicker.
Once we are done with the JDKs, we'll move on to Maven, and then the rest.
Ok to specifics,
First major change to get out of the way is the removal of the 'auto install' JDK
versions. They overlap with installed versions and going forward we would rather
manage installation via Puppet and roll them out to all slaves in one hit.
Looking at the table in the linked wiki page above, this means we'll be removing
eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
To avoid confusion we'll also be removing the auto install 'latest1.6' 'latest1.7' and 'latest1.8' options.
The best options for 'latest' versions is the ones at the top of the table 'JDK 1.x (Latest)'
which are all installed on all nodes and managed via puppet.
I'll point out also that we have installed 'unlimited security' versions of 1.6,1.7,1.8 jdks.
Very recent addition is also that of the JDK 9 b128 Early Access Build. We hope you enjoy
this addition and please do give feedback on this version to the builds@ mailing list so we can pass it on - but certainly do not plan to base your releases on these 'ea' builds. I'll try my best to add new ea builds as they come through.
Last ones to mention are the IBM and Harmony versions. I'm not sure how much in use
these are so I'm holding off on installing these for now. Please do ask for a specific version
if needed. I'll drop the from the UI in time.
I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45, 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now, along with the auto install latest links. Please plan
on migrating your builds away from these versions before then.
Any follow questions, please do concentrate your email responses to the builds@ mailing list.
Thanks!
Gav... (On behalf of the Infrastructure Team)
RE: Jenkins JDK Matrix - and consolidating of versions.
Posted by Uwe Schindler <us...@apache.org>.
Hi Gav,
sorry for responding late – I am currently on vacation!
About your questions: In the past we required some extra modules (like older Subversion to be compatible with the older Jenkins Checkouts). As we are on Git now and the build scripts use JGit to fetch revision numbers and check for clean checkouts, this is obsolete. So if you want to install the “Jenkins puppet module”, we are fine.
There is one special case for Lucene:
We have a hardware-specific “lucene.build.properties” file in Jenkin’s root and also some additional “test files” (large wikiepdia checkouts) that are used for nightly tests. If the puppet module does not delete those files in current ~/jenkins, it is ok. We would still need access to the machine and sudo to jenkins.
If this is all fine, go ahead!
Uwe
-----
Uwe Schindler
uschindler@apache.org
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
http://lucene.apache.org/
From: Gav [mailto:gmcdonald@apache.org]
Sent: Tuesday, August 2, 2016 1:06 AM
To: Uwe Schindler <us...@apache.org>
Cc: dev@lucene.apache.org; infrastructure@apache.org Infrastructure <in...@apache.org>
Subject: Re: Jenkins JDK Matrix - and consolidating of versions.
Hello Uwe,
Still waiting a response on what you would like doing with the Lucene VM (lucene1-us-west) VM.
Ideally we ditch the lucene_pvm_asf module and just make it use the build_slaves module the same
as the rest. With a note on the slave description that its still a node for the Lucene project.
Thoughts?
Gav...
On Sat, Jul 30, 2016 at 8:33 AM, Gav <gmcdonald@apache.org <ma...@apache.org> > wrote:
Hi Uwe,
On Sat, Jul 30, 2016 at 4:30 AM, Uwe Schindler <uschindler@apache.org <ma...@apache.org> > wrote:
Hi,
after changing the setup of the Lucene Jobs, we get all jobs failing with „JAVA_HOME“ not correctly defined:
https://builds.apache.org/job/Lucene-Solr-Tests-master/1290/console
This affects the “lucene” Jenkins node. Maybe the puppet was not correctly activated there.
Right, I hadnt added the jenkins module to 'lucene1-us-west' - being a PMC owned VM I was going to ask about that.
If you are happy for me to continue I'll get on with it today.
Gav...
We need” JDK 1.7 (latest)” and “JDK 1.8 (latest)” on this machine.
Uwe
-----
Uwe Schindler
uschindler@apache.org <ma...@apache.org>
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
http://lucene.apache.org/
From: Steve Rowe [mailto:sarowe@gmail.com <ma...@gmail.com> ]
Sent: Friday, July 29, 2016 2:38 PM
To: Lucene Dev <dev@lucene.apache.org <ma...@lucene.apache.org> >
Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
FYI, I switched all Lucene/Solr ASF Jenkins jobs’ configuration from “latest1.8” to “JDK 1.8 (latest)” (except for the 5.5 branch Java7 build, which I switched from "latest1.7” to “JDK 1.7 (latest)”) - more info below.
--
Steve
www.lucidworks.com <http://www.lucidworks.com>
Begin forwarded message:
From: Gav <gmcdonald@apache.org <ma...@apache.org> >
Subject: Jenkins JDK Matrix - and consolidating of versions.
Date: July 29, 2016 at 7:03:59 AM EDT
To: builds@apache.org <ma...@apache.org> , "infrastructure@apache.org <ma...@apache.org> Infrastructure" <infrastructure@apache.org <ma...@apache.org> >
Reply-To: gmcdonald@apache.org <ma...@apache.org>
Hi All,
So 99% of our Jenkins build machines are now puppetised with our configs in our Git repos.
Going forward this should make things easier to maintain the software (and versions of) on the nodes.
I went through all the JDK drop down options available in the Jenkins UI when
creating a build.The Confluence wiki page at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
lists all them all. When choosing a version to use I hope that this information will
prove useful - any changes made we will keep this page upto date.
However, some are not currently installed on the new puppetised
slaves (on purpose) and others we intend to consolidate down to fewer versions.
In contrast, we will be able to make newer release versions available quicker.
Once we are done with the JDKs, we'll move on to Maven, and then the rest.
Ok to specifics,
First major change to get out of the way is the removal of the 'auto install' JDK
versions. They overlap with installed versions and going forward we would rather
manage installation via Puppet and roll them out to all slaves in one hit.
Looking at the table in the linked wiki page above, this means we'll be removing
eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
To avoid confusion we'll also be removing the auto install 'latest1.6' 'latest1.7' and 'latest1.8' options.
The best options for 'latest' versions is the ones at the top of the table 'JDK 1.x (Latest)'
which are all installed on all nodes and managed via puppet.
I'll point out also that we have installed 'unlimited security' versions of 1.6,1.7,1.8 jdks.
Very recent addition is also that of the JDK 9 b128 Early Access Build. We hope you enjoy
this addition and please do give feedback on this version to the builds@ mailing list so we can pass it on - but certainly do not plan to base your releases on these 'ea' builds. I'll try my best to add new ea builds as they come through.
Last ones to mention are the IBM and Harmony versions. I'm not sure how much in use
these are so I'm holding off on installing these for now. Please do ask for a specific version
if needed. I'll drop the from the UI in time.
I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45, 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now, along with the auto install latest links. Please plan
on migrating your builds away from these versions before then.
Any follow questions, please do concentrate your email responses to the builds@ mailing list.
Thanks!
Gav... (On behalf of the Infrastructure Team)
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Gav <gm...@apache.org>.
Hello Uwe,
Still waiting a response on what you would like doing with the Lucene VM
(lucene1-us-west) VM.
Ideally we ditch the lucene_pvm_asf module and just make it use the
build_slaves module the same
as the rest. With a note on the slave description that its still a node for
the Lucene project.
Thoughts?
Gav...
On Sat, Jul 30, 2016 at 8:33 AM, Gav <gm...@apache.org> wrote:
> Hi Uwe,
>
> On Sat, Jul 30, 2016 at 4:30 AM, Uwe Schindler <us...@apache.org>
> wrote:
>
>> Hi,
>>
>>
>>
>> after changing the setup of the Lucene Jobs, we get all jobs failing with
>> „JAVA_HOME“ not correctly defined:
>>
>>
>>
>> https://builds.apache.org/job/Lucene-Solr-Tests-master/1290/console
>>
>>
>>
>> This affects the “lucene” Jenkins node. Maybe the puppet was not
>> correctly activated there.
>>
>
> Right, I hadnt added the jenkins module to 'lucene1-us-west' - being a PMC
> owned VM I was going to ask about that.
> If you are happy for me to continue I'll get on with it today.
>
> Gav...
>
>
>
>> We need” JDK 1.7 (latest)” and “JDK 1.8 (latest)” on this machine.
>>
>
>
>
>>
>>
>> Uwe
>>
>>
>>
>> -----
>>
>> Uwe Schindler
>>
>> uschindler@apache.org
>>
>> ASF Member, Apache Lucene PMC / Committer
>>
>> Bremen, Germany
>>
>> http://lucene.apache.org/
>>
>>
>>
>> *From:* Steve Rowe [mailto:sarowe@gmail.com]
>> *Sent:* Friday, July 29, 2016 2:38 PM
>> *To:* Lucene Dev <de...@lucene.apache.org>
>> *Subject:* Fwd: Jenkins JDK Matrix - and consolidating of versions.
>>
>>
>>
>> FYI, I switched all Lucene/Solr ASF Jenkins jobs’ configuration from
>> “latest1.8” to “JDK 1.8 (latest)” (except for the 5.5 branch Java7 build,
>> which I switched from "latest1.7” to “JDK 1.7 (latest)”) - more info below.
>>
>>
>>
>> --
>>
>> Steve
>>
>> www.lucidworks.com
>>
>>
>>
>> Begin forwarded message:
>>
>>
>>
>> *From: *Gav <gm...@apache.org>
>>
>> *Subject: Jenkins JDK Matrix - and consolidating of versions.*
>>
>> *Date: *July 29, 2016 at 7:03:59 AM EDT
>>
>> *To: *builds@apache.org, "infrastructure@apache.org Infrastructure" <
>> infrastructure@apache.org>
>>
>> *Reply-To: *gmcdonald@apache.org
>>
>>
>>
>> Hi All,
>>
>> So 99% of our Jenkins build machines are now puppetised with our configs
>> in our Git repos.
>> Going forward this should make things easier to maintain the software
>> (and versions of) on the nodes.
>>
>>
>>
>> I went through all the JDK drop down options available in the Jenkins UI
>> when
>>
>> creating a build.The Confluence wiki page at :-
>>
>> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
>>
>> lists all them all. When choosing a version to use I hope that this
>> information will
>> prove useful - any changes made we will keep this page upto date.
>> However, some are not currently installed on the new puppetised
>>
>> slaves (on purpose) and others we intend to consolidate down to fewer
>> versions.
>>
>> In contrast, we will be able to make newer release versions available
>> quicker.
>>
>> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>>
>> Ok to specifics,
>>
>> First major change to get out of the way is the removal of the 'auto
>> install' JDK
>>
>> versions. They overlap with installed versions and going forward we would
>> rather
>>
>> manage installation via Puppet and roll them out to all slaves in one hit.
>>
>> Looking at the table in the linked wiki page above, this means we'll be
>> removing
>>
>> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
>> To avoid confusion we'll also be removing the auto install 'latest1.6'
>> 'latest1.7' and 'latest1.8' options.
>>
>> The best options for 'latest' versions is the ones at the top of the
>> table 'JDK 1.x (Latest)'
>> which are all installed on all nodes and managed via puppet.
>>
>> I'll point out also that we have installed 'unlimited security' versions
>> of 1.6,1.7,1.8 jdks.
>>
>> Very recent addition is also that of the JDK 9 b128 Early Access Build.
>> We hope you enjoy
>>
>> this addition and please do give feedback on this version to the builds@
>> mailing list so we can pass it on - but certainly do not plan to base your
>> releases on these 'ea' builds. I'll try my best to add new ea builds as
>> they come through.
>>
>> Last ones to mention are the IBM and Harmony versions. I'm not sure how
>> much in use
>>
>> these are so I'm holding off on installing these for now. Please do ask
>> for a specific version
>>
>> if needed. I'll drop the from the UI in time.
>>
>> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
>> 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
>> along with the auto install latest links. Please plan
>>
>> on migrating your builds away from these versions before then.
>>
>> Any follow questions, please do concentrate your email responses to the
>> builds@ mailing list.
>>
>> Thanks!
>>
>> Gav... (On behalf of the Infrastructure Team)
>>
>>
>>
>
>
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Gav <gm...@apache.org>.
Hi Uwe,
On Sat, Jul 30, 2016 at 4:30 AM, Uwe Schindler <us...@apache.org>
wrote:
> Hi,
>
>
>
> after changing the setup of the Lucene Jobs, we get all jobs failing with
> „JAVA_HOME“ not correctly defined:
>
>
>
> https://builds.apache.org/job/Lucene-Solr-Tests-master/1290/console
>
>
>
> This affects the “lucene” Jenkins node. Maybe the puppet was not correctly
> activated there.
>
Right, I hadnt added the jenkins module to 'lucene1-us-west' - being a PMC
owned VM I was going to ask about that.
If you are happy for me to continue I'll get on with it today.
Gav...
> We need” JDK 1.7 (latest)” and “JDK 1.8 (latest)” on this machine.
>
>
>
> Uwe
>
>
>
> -----
>
> Uwe Schindler
>
> uschindler@apache.org
>
> ASF Member, Apache Lucene PMC / Committer
>
> Bremen, Germany
>
> http://lucene.apache.org/
>
>
>
> *From:* Steve Rowe [mailto:sarowe@gmail.com]
> *Sent:* Friday, July 29, 2016 2:38 PM
> *To:* Lucene Dev <de...@lucene.apache.org>
> *Subject:* Fwd: Jenkins JDK Matrix - and consolidating of versions.
>
>
>
> FYI, I switched all Lucene/Solr ASF Jenkins jobs’ configuration from
> “latest1.8” to “JDK 1.8 (latest)” (except for the 5.5 branch Java7 build,
> which I switched from "latest1.7” to “JDK 1.7 (latest)”) - more info below.
>
>
>
> --
>
> Steve
>
> www.lucidworks.com
>
>
>
> Begin forwarded message:
>
>
>
> *From: *Gav <gm...@apache.org>
>
> *Subject: Jenkins JDK Matrix - and consolidating of versions.*
>
> *Date: *July 29, 2016 at 7:03:59 AM EDT
>
> *To: *builds@apache.org, "infrastructure@apache.org Infrastructure" <
> infrastructure@apache.org>
>
> *Reply-To: *gmcdonald@apache.org
>
>
>
> Hi All,
>
> So 99% of our Jenkins build machines are now puppetised with our configs
> in our Git repos.
> Going forward this should make things easier to maintain the software (and
> versions of) on the nodes.
>
>
>
> I went through all the JDK drop down options available in the Jenkins UI
> when
>
> creating a build.The Confluence wiki page at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
>
> lists all them all. When choosing a version to use I hope that this
> information will
> prove useful - any changes made we will keep this page upto date.
> However, some are not currently installed on the new puppetised
>
> slaves (on purpose) and others we intend to consolidate down to fewer
> versions.
>
> In contrast, we will be able to make newer release versions available
> quicker.
>
> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>
> Ok to specifics,
>
> First major change to get out of the way is the removal of the 'auto
> install' JDK
>
> versions. They overlap with installed versions and going forward we would
> rather
>
> manage installation via Puppet and roll them out to all slaves in one hit.
>
> Looking at the table in the linked wiki page above, this means we'll be
> removing
>
> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> To avoid confusion we'll also be removing the auto install 'latest1.6'
> 'latest1.7' and 'latest1.8' options.
>
> The best options for 'latest' versions is the ones at the top of the table
> 'JDK 1.x (Latest)'
> which are all installed on all nodes and managed via puppet.
>
> I'll point out also that we have installed 'unlimited security' versions
> of 1.6,1.7,1.8 jdks.
>
> Very recent addition is also that of the JDK 9 b128 Early Access Build. We
> hope you enjoy
>
> this addition and please do give feedback on this version to the builds@
> mailing list so we can pass it on - but certainly do not plan to base your
> releases on these 'ea' builds. I'll try my best to add new ea builds as
> they come through.
>
> Last ones to mention are the IBM and Harmony versions. I'm not sure how
> much in use
>
> these are so I'm holding off on installing these for now. Please do ask
> for a specific version
>
> if needed. I'll drop the from the UI in time.
>
> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
> 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
> along with the auto install latest links. Please plan
>
> on migrating your builds away from these versions before then.
>
> Any follow questions, please do concentrate your email responses to the
> builds@ mailing list.
>
> Thanks!
>
> Gav... (On behalf of the Infrastructure Team)
>
>
>
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Steve Rowe <sa...@gmail.com>.
Sorry, that was a dumb question - I didn’t look at those two paths close enough to see that one was a prefix of the other...
--
Steve
www.lucidworks.com
> On Jul 29, 2016, at 2:36 PM, Steve Rowe <sa...@gmail.com> wrote:
>
> Uwe, (FYI removed ASF infra and Gav from recipient list)
>
> I see the following in the logs:
>
> ——
> Error: JAVA_HOME is not defined correctly.
> We cannot execute /home/jenkins/tools/java/latest1.8/bin/java
> ——
>
> But <https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix> says the symlink for “JDK 1.8 (latest)” is: /home/jenkins/tools/java/latest1.8
>
> Is there something special happing on the lucene slave that would make the new config stuff inoperable?
>
> --
> Steve
> www.lucidworks.com
>
>> On Jul 29, 2016, at 2:30 PM, Uwe Schindler <us...@apache.org> wrote:
>>
>> Hi,
>>
>> after changing the setup of the Lucene Jobs, we get all jobs failing with „JAVA_HOME“ not correctly defined:
>>
>> https://builds.apache.org/job/Lucene-Solr-Tests-master/1290/console
>>
>> This affects the “lucene” Jenkins node. Maybe the puppet was not correctly activated there. We need” JDK 1.7 (latest)” and “JDK 1.8 (latest)” on this machine.
>>
>> Uwe
>>
>> -----
>> Uwe Schindler
>> uschindler@apache.org
>> ASF Member, Apache Lucene PMC / Committer
>> Bremen, Germany
>> http://lucene.apache.org/
>>
>> From: Steve Rowe [mailto:sarowe@gmail.com]
>> Sent: Friday, July 29, 2016 2:38 PM
>> To: Lucene Dev <de...@lucene.apache.org>
>> Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
>>
>> FYI, I switched all Lucene/Solr ASF Jenkins jobs’ configuration from “latest1.8” to “JDK 1.8 (latest)” (except for the 5.5 branch Java7 build, which I switched from "latest1.7” to “JDK 1.7 (latest)”) - more info below.
>>
>> --
>> Steve
>> www.lucidworks.com
>>
>>
>>> Begin forwarded message:
>>>
>>> From: Gav <gm...@apache.org>
>>> Subject: Jenkins JDK Matrix - and consolidating of versions.
>>> Date: July 29, 2016 at 7:03:59 AM EDT
>>> To: builds@apache.org, "infrastructure@apache.org Infrastructure" <in...@apache.org>
>>> Reply-To: gmcdonald@apache.org
>>>
>>> Hi All,
>>>
>>> So 99% of our Jenkins build machines are now puppetised with our configs in our Git repos.
>>> Going forward this should make things easier to maintain the software (and versions of) on the nodes.
>>>
>>> I went through all the JDK drop down options available in the Jenkins UI when
>>> creating a build.The Confluence wiki page at :-
>>>
>>> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
>>>
>>> lists all them all. When choosing a version to use I hope that this information will
>>> prove useful - any changes made we will keep this page upto date.
>>> However, some are not currently installed on the new puppetised
>>> slaves (on purpose) and others we intend to consolidate down to fewer versions.
>>>
>>> In contrast, we will be able to make newer release versions available quicker.
>>>
>>> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>>>
>>> Ok to specifics,
>>>
>>> First major change to get out of the way is the removal of the 'auto install' JDK
>>> versions. They overlap with installed versions and going forward we would rather
>>> manage installation via Puppet and roll them out to all slaves in one hit.
>>>
>>> Looking at the table in the linked wiki page above, this means we'll be removing
>>> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
>>> To avoid confusion we'll also be removing the auto install 'latest1.6' 'latest1.7' and 'latest1.8' options.
>>>
>>> The best options for 'latest' versions is the ones at the top of the table 'JDK 1.x (Latest)'
>>> which are all installed on all nodes and managed via puppet.
>>>
>>> I'll point out also that we have installed 'unlimited security' versions of 1.6,1.7,1.8 jdks.
>>>
>>> Very recent addition is also that of the JDK 9 b128 Early Access Build. We hope you enjoy
>>> this addition and please do give feedback on this version to the builds@ mailing list so we can pass it on - but certainly do not plan to base your releases on these 'ea' builds. I'll try my best to add new ea builds as they come through.
>>>
>>> Last ones to mention are the IBM and Harmony versions. I'm not sure how much in use
>>> these are so I'm holding off on installing these for now. Please do ask for a specific version
>>> if needed. I'll drop the from the UI in time.
>>>
>>> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45, 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now, along with the auto install latest links. Please plan
>>> on migrating your builds away from these versions before then.
>>>
>>> Any follow questions, please do concentrate your email responses to the builds@ mailing list.
>>>
>>> Thanks!
>>>
>>> Gav... (On behalf of the Infrastructure Team)
>>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Steve Rowe <sa...@gmail.com>.
Uwe, (FYI removed ASF infra and Gav from recipient list)
I see the following in the logs:
——
Error: JAVA_HOME is not defined correctly.
We cannot execute /home/jenkins/tools/java/latest1.8/bin/java
——
But <https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix> says the symlink for “JDK 1.8 (latest)” is: /home/jenkins/tools/java/latest1.8
Is there something special happing on the lucene slave that would make the new config stuff inoperable?
--
Steve
www.lucidworks.com
> On Jul 29, 2016, at 2:30 PM, Uwe Schindler <us...@apache.org> wrote:
>
> Hi,
>
> after changing the setup of the Lucene Jobs, we get all jobs failing with „JAVA_HOME“ not correctly defined:
>
> https://builds.apache.org/job/Lucene-Solr-Tests-master/1290/console
>
> This affects the “lucene” Jenkins node. Maybe the puppet was not correctly activated there. We need” JDK 1.7 (latest)” and “JDK 1.8 (latest)” on this machine.
>
> Uwe
>
> -----
> Uwe Schindler
> uschindler@apache.org
> ASF Member, Apache Lucene PMC / Committer
> Bremen, Germany
> http://lucene.apache.org/
>
> From: Steve Rowe [mailto:sarowe@gmail.com]
> Sent: Friday, July 29, 2016 2:38 PM
> To: Lucene Dev <de...@lucene.apache.org>
> Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
>
> FYI, I switched all Lucene/Solr ASF Jenkins jobs’ configuration from “latest1.8” to “JDK 1.8 (latest)” (except for the 5.5 branch Java7 build, which I switched from "latest1.7” to “JDK 1.7 (latest)”) - more info below.
>
> --
> Steve
> www.lucidworks.com
>
>
>> Begin forwarded message:
>>
>> From: Gav <gm...@apache.org>
>> Subject: Jenkins JDK Matrix - and consolidating of versions.
>> Date: July 29, 2016 at 7:03:59 AM EDT
>> To: builds@apache.org, "infrastructure@apache.org Infrastructure" <in...@apache.org>
>> Reply-To: gmcdonald@apache.org
>>
>> Hi All,
>>
>> So 99% of our Jenkins build machines are now puppetised with our configs in our Git repos.
>> Going forward this should make things easier to maintain the software (and versions of) on the nodes.
>>
>> I went through all the JDK drop down options available in the Jenkins UI when
>> creating a build.The Confluence wiki page at :-
>>
>> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
>>
>> lists all them all. When choosing a version to use I hope that this information will
>> prove useful - any changes made we will keep this page upto date.
>> However, some are not currently installed on the new puppetised
>> slaves (on purpose) and others we intend to consolidate down to fewer versions.
>>
>> In contrast, we will be able to make newer release versions available quicker.
>>
>> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>>
>> Ok to specifics,
>>
>> First major change to get out of the way is the removal of the 'auto install' JDK
>> versions. They overlap with installed versions and going forward we would rather
>> manage installation via Puppet and roll them out to all slaves in one hit.
>>
>> Looking at the table in the linked wiki page above, this means we'll be removing
>> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
>> To avoid confusion we'll also be removing the auto install 'latest1.6' 'latest1.7' and 'latest1.8' options.
>>
>> The best options for 'latest' versions is the ones at the top of the table 'JDK 1.x (Latest)'
>> which are all installed on all nodes and managed via puppet.
>>
>> I'll point out also that we have installed 'unlimited security' versions of 1.6,1.7,1.8 jdks.
>>
>> Very recent addition is also that of the JDK 9 b128 Early Access Build. We hope you enjoy
>> this addition and please do give feedback on this version to the builds@ mailing list so we can pass it on - but certainly do not plan to base your releases on these 'ea' builds. I'll try my best to add new ea builds as they come through.
>>
>> Last ones to mention are the IBM and Harmony versions. I'm not sure how much in use
>> these are so I'm holding off on installing these for now. Please do ask for a specific version
>> if needed. I'll drop the from the UI in time.
>>
>> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45, 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now, along with the auto install latest links. Please plan
>> on migrating your builds away from these versions before then.
>>
>> Any follow questions, please do concentrate your email responses to the builds@ mailing list.
>>
>> Thanks!
>>
>> Gav... (On behalf of the Infrastructure Team)
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
RE: Jenkins JDK Matrix - and consolidating of versions.
Posted by Uwe Schindler <us...@apache.org>.
Hi,
after changing the setup of the Lucene Jobs, we get all jobs failing with „JAVA_HOME“ not correctly defined:
https://builds.apache.org/job/Lucene-Solr-Tests-master/1290/console
This affects the “lucene” Jenkins node. Maybe the puppet was not correctly activated there. We need” JDK 1.7 (latest)” and “JDK 1.8 (latest)” on this machine.
Uwe
-----
Uwe Schindler
uschindler@apache.org
ASF Member, Apache Lucene PMC / Committer
Bremen, Germany
http://lucene.apache.org/
From: Steve Rowe [mailto:sarowe@gmail.com]
Sent: Friday, July 29, 2016 2:38 PM
To: Lucene Dev <de...@lucene.apache.org>
Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
FYI, I switched all Lucene/Solr ASF Jenkins jobs’ configuration from “latest1.8” to “JDK 1.8 (latest)” (except for the 5.5 branch Java7 build, which I switched from "latest1.7” to “JDK 1.7 (latest)”) - more info below.
--
Steve
www.lucidworks.com <http://www.lucidworks.com>
Begin forwarded message:
From: Gav <gmcdonald@apache.org <ma...@apache.org> >
Subject: Jenkins JDK Matrix - and consolidating of versions.
Date: July 29, 2016 at 7:03:59 AM EDT
To: builds@apache.org <ma...@apache.org> , "infrastructure@apache.org <ma...@apache.org> Infrastructure" <infrastructure@apache.org <ma...@apache.org> >
Reply-To: gmcdonald@apache.org <ma...@apache.org>
Hi All,
So 99% of our Jenkins build machines are now puppetised with our configs in our Git repos.
Going forward this should make things easier to maintain the software (and versions of) on the nodes.
I went through all the JDK drop down options available in the Jenkins UI when
creating a build.The Confluence wiki page at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
lists all them all. When choosing a version to use I hope that this information will
prove useful - any changes made we will keep this page upto date.
However, some are not currently installed on the new puppetised
slaves (on purpose) and others we intend to consolidate down to fewer versions.
In contrast, we will be able to make newer release versions available quicker.
Once we are done with the JDKs, we'll move on to Maven, and then the rest.
Ok to specifics,
First major change to get out of the way is the removal of the 'auto install' JDK
versions. They overlap with installed versions and going forward we would rather
manage installation via Puppet and roll them out to all slaves in one hit.
Looking at the table in the linked wiki page above, this means we'll be removing
eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
To avoid confusion we'll also be removing the auto install 'latest1.6' 'latest1.7' and 'latest1.8' options.
The best options for 'latest' versions is the ones at the top of the table 'JDK 1.x (Latest)'
which are all installed on all nodes and managed via puppet.
I'll point out also that we have installed 'unlimited security' versions of 1.6,1.7,1.8 jdks.
Very recent addition is also that of the JDK 9 b128 Early Access Build. We hope you enjoy
this addition and please do give feedback on this version to the builds@ mailing list so we can pass it on - but certainly do not plan to base your releases on these 'ea' builds. I'll try my best to add new ea builds as they come through.
Last ones to mention are the IBM and Harmony versions. I'm not sure how much in use
these are so I'm holding off on installing these for now. Please do ask for a specific version
if needed. I'll drop the from the UI in time.
I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45, 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now, along with the auto install latest links. Please plan
on migrating your builds away from these versions before then.
Any follow questions, please do concentrate your email responses to the builds@ mailing list.
Thanks!
Gav... (On behalf of the Infrastructure Team)
Fwd: Jenkins JDK Matrix - and consolidating of versions.
Posted by Steve Rowe <sa...@gmail.com>.
FYI, I switched all Lucene/Solr ASF Jenkins jobs’ configuration from “latest1.8” to “JDK 1.8 (latest)” (except for the 5.5 branch Java7 build, which I switched from "latest1.7” to “JDK 1.7 (latest)”) - more info below.
--
Steve
www.lucidworks.com <http://www.lucidworks.com/>
> Begin forwarded message:
>
> From: Gav <gm...@apache.org>
> Subject: Jenkins JDK Matrix - and consolidating of versions.
> Date: July 29, 2016 at 7:03:59 AM EDT
> To: builds@apache.org, "infrastructure@apache.org Infrastructure" <in...@apache.org>
> Reply-To: gmcdonald@apache.org
>
> Hi All,
>
> So 99% of our Jenkins build machines are now puppetised with our configs in our Git repos.
> Going forward this should make things easier to maintain the software (and versions of) on the nodes.
>
> I went through all the JDK drop down options available in the Jenkins UI when
> creating a build.The Confluence wiki page at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix <https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix>
>
> lists all them all. When choosing a version to use I hope that this information will
> prove useful - any changes made we will keep this page upto date.
> However, some are not currently installed on the new puppetised
> slaves (on purpose) and others we intend to consolidate down to fewer versions.
>
> In contrast, we will be able to make newer release versions available quicker.
>
> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>
> Ok to specifics,
>
> First major change to get out of the way is the removal of the 'auto install' JDK
> versions. They overlap with installed versions and going forward we would rather
> manage installation via Puppet and roll them out to all slaves in one hit.
>
> Looking at the table in the linked wiki page above, this means we'll be removing
> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> To avoid confusion we'll also be removing the auto install 'latest1.6' 'latest1.7' and 'latest1.8' options.
>
> The best options for 'latest' versions is the ones at the top of the table 'JDK 1.x (Latest)'
> which are all installed on all nodes and managed via puppet.
>
> I'll point out also that we have installed 'unlimited security' versions of 1.6,1.7,1.8 jdks.
>
> Very recent addition is also that of the JDK 9 b128 Early Access Build. We hope you enjoy
> this addition and please do give feedback on this version to the builds@ mailing list so we can pass it on - but certainly do not plan to base your releases on these 'ea' builds. I'll try my best to add new ea builds as they come through.
>
> Last ones to mention are the IBM and Harmony versions. I'm not sure how much in use
> these are so I'm holding off on installing these for now. Please do ask for a specific version
> if needed. I'll drop the from the UI in time.
>
> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45, 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now, along with the auto install latest links. Please plan
> on migrating your builds away from these versions before then.
>
> Any follow questions, please do concentrate your email responses to the builds@ mailing list.
>
> Thanks!
>
> Gav... (On behalf of the Infrastructure Team)
>
Fwd: Jenkins JDK Matrix - and consolidating of versions.
Posted by "John D. Ament" <jo...@apache.org>.
All,
Please see below email from Gav RE Jenkins.
If no one sees any issues, I'd like to go through all of our jobs and:
- Anything pointing to a Java 6 build switch to JDK 1.6 (latest)
- Similarly for Java 7/Java 8
John
---------- Forwarded message ---------
From: Gav <gm...@apache.org>
Date: Fri, Jul 29, 2016 at 7:04 AM
Subject: Jenkins JDK Matrix - and consolidating of versions.
To: <bu...@apache.org>, infrastructure@apache.org Infrastructure <
infrastructure@apache.org>
Hi All,
So 99% of our Jenkins build machines are now puppetised with our configs in
our Git repos.
Going forward this should make things easier to maintain the software (and
versions of) on the nodes.
I went through all the JDK drop down options available in the Jenkins UI
when
creating a build.The Confluence wiki page at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
lists all them all. When choosing a version to use I hope that this
information will
prove useful - any changes made we will keep this page upto date.
However, some are not currently installed on the new puppetised
slaves (on purpose) and others we intend to consolidate down to fewer
versions.
In contrast, we will be able to make newer release versions available
quicker.
Once we are done with the JDKs, we'll move on to Maven, and then the rest.
Ok to specifics,
First major change to get out of the way is the removal of the 'auto
install' JDK
versions. They overlap with installed versions and going forward we would
rather
manage installation via Puppet and roll them out to all slaves in one hit.
Looking at the table in the linked wiki page above, this means we'll be
removing
eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
To avoid confusion we'll also be removing the auto install 'latest1.6'
'latest1.7' and 'latest1.8' options.
The best options for 'latest' versions is the ones at the top of the table
'JDK 1.x (Latest)'
which are all installed on all nodes and managed via puppet.
I'll point out also that we have installed 'unlimited security' versions of
1.6,1.7,1.8 jdks.
Very recent addition is also that of the JDK 9 b128 Early Access Build. We
hope you enjoy
this addition and please do give feedback on this version to the builds@
mailing list so we can pass it on - but certainly do not plan to base your
releases on these 'ea' builds. I'll try my best to add new ea builds as
they come through.
Last ones to mention are the IBM and Harmony versions. I'm not sure how
much in use
these are so I'm holding off on installing these for now. Please do ask for
a specific version
if needed. I'll drop the from the UI in time.
I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
along with the auto install latest links. Please plan
on migrating your builds away from these versions before then.
Any follow questions, please do concentrate your email responses to the
builds@ mailing list.
Thanks!
Gav... (On behalf of the Infrastructure Team)
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Stefan Bodewig <bo...@apache.org>.
On 2016-07-29, Gav wrote:
> I went through all the JDK drop down options available in the Jenkins UI
> when
> creating a build.The Confluence wiki page at :-
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
> lists all them all. When choosing a version to use I hope that this
> information will
> prove useful - any changes made we will keep this page upto date.
> However, some are not currently installed on the new puppetised
> slaves (on purpose) and others we intend to consolidate down to fewer
> versions.
Thanks a lot!
I tried to configure
https://builds.apache.org/job/Ant-Build-Matrix-1.9.x according to this
matrix. For some reason the "JDK 1.X (unlimited security) 64-bit Windows
only" with X=7,8 don't seem to work. Do I need to narrow down the
selection of nodes beyond "label=Windows"?
Also I've frequently run into OutOfMemory errors in the Ubuntu nodes,
most notable the HXY nodes. For now I use !yahoo-not-h2 to restrict the
selection of Ubuntu nodes, I am not sure this is the best option,
though.
> The best options for 'latest' versions is the ones at the top of the table
> 'JDK 1.x (Latest)'
> which are all installed on all nodes and managed via puppet.
Does platform "Ubuntu" mean these options are not available to Windows
nodes?
> Very recent addition is also that of the JDK 9 b128 Early Access
> Build.
This is awesome. Unfortunately it didn't work in our case either.
https://builds.apache.org/job/Ant-Build-Matrix-1.9.x/32/jdk=JDK%209%20b128%20(early%20access%20build),label=Ubuntu/console
,----
| Error: JAVA_HOME is not defined correctly.
| We cannot execute /home/jenkins/tools/java/jdk-9-ea-b128/bin/java
`----
Cheers
Stefan
Fwd: Jenkins JDK Matrix - and consolidating of versions.
Posted by Andreas Lehmkuehler <an...@lehmi.de>.
fyi
-------- Weitergeleitete Nachricht --------
Betreff: Jenkins JDK Matrix - and consolidating of versions.
Datum: Fri, 29 Jul 2016 21:03:59 +1000
Von: Gav <gm...@apache.org>
Antwort an: builds@apache.org, gmcdonald@apache.org
An: builds@apache.org, infrastructure@apache.org Infrastructure
<in...@apache.org>
Hi All,
So 99% of our Jenkins build machines are now puppetised with our configs in
our Git repos.
Going forward this should make things easier to maintain the software (and
versions of) on the nodes.
I went through all the JDK drop down options available in the Jenkins UI
when
creating a build.The Confluence wiki page at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
lists all them all. When choosing a version to use I hope that this
information will
prove useful - any changes made we will keep this page upto date.
However, some are not currently installed on the new puppetised
slaves (on purpose) and others we intend to consolidate down to fewer
versions.
In contrast, we will be able to make newer release versions available
quicker.
Once we are done with the JDKs, we'll move on to Maven, and then the rest.
Ok to specifics,
First major change to get out of the way is the removal of the 'auto
install' JDK
versions. They overlap with installed versions and going forward we would
rather
manage installation via Puppet and roll them out to all slaves in one hit.
Looking at the table in the linked wiki page above, this means we'll be
removing
eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
To avoid confusion we'll also be removing the auto install 'latest1.6'
'latest1.7' and 'latest1.8' options.
The best options for 'latest' versions is the ones at the top of the table
'JDK 1.x (Latest)'
which are all installed on all nodes and managed via puppet.
I'll point out also that we have installed 'unlimited security' versions of
1.6,1.7,1.8 jdks.
Very recent addition is also that of the JDK 9 b128 Early Access Build. We
hope you enjoy
this addition and please do give feedback on this version to the builds@
mailing list so we can pass it on - but certainly do not plan to base your
releases on these 'ea' builds. I'll try my best to add new ea builds as
they come through.
Last ones to mention are the IBM and Harmony versions. I'm not sure how
much in use
these are so I'm holding off on installing these for now. Please do ask for
a specific version
if needed. I'll drop the from the UI in time.
I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
along with the auto install latest links. Please plan
on migrating your builds away from these versions before then.
Any follow questions, please do concentrate your email responses to the
builds@ mailing list.
Thanks!
Gav... (On behalf of the Infrastructure Team)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pdfbox.apache.org
For additional commands, e-mail: dev-help@pdfbox.apache.org
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Gav <gm...@apache.org>.
Hi,
On Fri, Aug 5, 2016 at 5:02 PM, Richard Eckart de Castilho <re...@apache.org>
wrote:
> Hi,
>
> We have some builds that so far occasionally run on Windows and other
> times on Ubuntu depending which resources are free. It is also a nice way
> to randomly check if the build works on both of these platforms.
>
> Looking at the matrix, it seems that none of the JDK labels works cross
> platform, i.e. on Windows and Ubuntu - is that correct?
>
Yes correct. I would create a matrix build perhaps, making sure to chose
labels that have 'Windows' in them for that platform.
HTH
Gav...
> Cheers,
>
> -- Richard
>
> > On 29.07.2016, at 13:03, Gav <gm...@apache.org> wrote:
> >
> > Hi All,
> >
> > So 99% of our Jenkins build machines are now puppetised with our configs
> in our Git repos.
> > Going forward this should make things easier to maintain the software
> (and versions of) on the nodes.
> >
> > I went through all the JDK drop down options available in the Jenkins UI
> when
> > creating a build.The Confluence wiki page at :-
> >
> > https://cwiki.apache.org/confluence/display/INFRA/JDK+
> Installation+Matrix
> >
>
>
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Richard Eckart de Castilho <re...@apache.org>.
Hi,
We have some builds that so far occasionally run on Windows and other times on Ubuntu depending which resources are free. It is also a nice way to randomly check if the build works on both of these platforms.
Looking at the matrix, it seems that none of the JDK labels works cross platform, i.e. on Windows and Ubuntu - is that correct?
Cheers,
-- Richard
> On 29.07.2016, at 13:03, Gav <gm...@apache.org> wrote:
>
> Hi All,
>
> So 99% of our Jenkins build machines are now puppetised with our configs in our Git repos.
> Going forward this should make things easier to maintain the software (and versions of) on the nodes.
>
> I went through all the JDK drop down options available in the Jenkins UI when
> creating a build.The Confluence wiki page at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
>
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Suresh Marru <sm...@apache.org>.
Hi Gav,
When I change Airavata job from latest1.8 to JDK 1.8 (latest) an extra -XX shows up in command and the build fails. Any guidance on a fix?
Modules changed, recalculating dependency graph
Established TCP socket on 47606
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[Airavata] $ /home/jenkins/tools/java/latest1.8/bin/java -Xmx2g -Xms256m -XX -cp /home/jenkins/jenkins-slave/maven32-agent.jar:/home/jenkins/tools/maven/latest3/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/latest3/conf/logging jenkins.maven3.agent.Maven32Main /home/jenkins/tools/maven/latest3/ /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven32-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 47606
Unrecognized option: -XX
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
ERROR: Failed to launch Maven. Exit code = 1
Thanks,
Suresh
> On Aug 4, 2016, at 8:13 PM, Gav <gm...@apache.org> wrote:
>
>
>
> Hello PMCs,
>
> 7 days ago I informed the builds@ and infrastructure@ mailing lists the intention to consolidate JDK versions in
> our Jenkins instance. I gave 7 days notice. (Anyone configuring builds should be subscribed to the builds@
> mailing list)
>
> Today I find that there are still :-
>
> 109 jobs configured to use the 'latest1.8'
> 67 jobs configured to use the 'latest1.7'
> 7 jobs configured to use the 'latest 1.6'
>
> 45 jobs configured to use '1.8.0_66'
> 4 jobs configured to use '1.8.0_05'
> 4 jobs configured to use '1.8.0_11'
>
>
> This wider distribution email to all PMC private lists is to let you know I'm going to delay the migration for '3 more days'
> at which point I will migrate any remaining jobs myself.
>
> I prefer of course that projects make the changes themselves.
>
> Below I include a copy of the mail I sent 7 days ago FYI.
>
> tl;dr please take a look at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix <https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix>
>
> There are also plans to consoildate Maven and Ant versions - please do check the
> builds@ mailing list archives for these notices - these are due to be migrated by
> Sunday at the latest
>
> Any questions please email me direct or reply to any of the builds@ mails.
>
>
> HTH
>
> Gav... (ASF Infrastructure Team)
>
>
> ---------- Forwarded message ----------
> From: Gav <gmcdonald@apache.org <ma...@apache.org>>
> Date: Fri, Jul 29, 2016 at 9:03 PM
> Subject: Jenkins JDK Matrix - and consolidating of versions.
> To: builds@apache.org <ma...@apache.org>, "infrastructure@apache.org <ma...@apache.org> Infrastructure" <infrastructure@apache.org <ma...@apache.org>>
>
>
> Hi All,
>
> So 99% of our Jenkins build machines are now puppetised with our configs in our Git repos.
> Going forward this should make things easier to maintain the software (and versions of) on the nodes.
>
> I went through all the JDK drop down options available in the Jenkins UI when
> creating a build.The Confluence wiki page at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix <https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix>
>
> lists all them all. When choosing a version to use I hope that this information will
> prove useful - any changes made we will keep this page upto date.
> However, some are not currently installed on the new puppetised
> slaves (on purpose) and others we intend to consolidate down to fewer versions.
>
> In contrast, we will be able to make newer release versions available quicker.
>
> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>
> Ok to specifics,
>
> First major change to get out of the way is the removal of the 'auto install' JDK
> versions. They overlap with installed versions and going forward we would rather
> manage installation via Puppet and roll them out to all slaves in one hit.
>
> Looking at the table in the linked wiki page above, this means we'll be removing
> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> To avoid confusion we'll also be removing the auto install 'latest1.6' 'latest1.7' and 'latest1.8' options.
>
> The best options for 'latest' versions is the ones at the top of the table 'JDK 1.x (Latest)'
> which are all installed on all nodes and managed via puppet.
>
> I'll point out also that we have installed 'unlimited security' versions of 1.6,1.7,1.8 jdks.
>
> Very recent addition is also that of the JDK 9 b128 Early Access Build. We hope you enjoy
> this addition and please do give feedback on this version to the builds@ mailing list so we can pass it on - but certainly do not plan to base your releases on these 'ea' builds. I'll try my best to add new ea builds as they come through.
>
> Last ones to mention are the IBM and Harmony versions. I'm not sure how much in use
> these are so I'm holding off on installing these for now. Please do ask for a specific version
> if needed. I'll drop the from the UI in time.
>
> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45, 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now, along with the auto install latest links. Please plan
> on migrating your builds away from these versions before then.
>
> Any follow questions, please do concentrate your email responses to the builds@ mailing list.
>
> Thanks!
>
> Gav... (On behalf of the Infrastructure Team)
>
>
>
FW: Jenkins JDK Matrix - and consolidating of versions.
Posted by "Sun, Dapeng" <da...@intel.com>.
FYI.
The failure of nightly build for v1(https://builds.apache.org/job/Sentry-jdk-1.7) is caused by the following reasons, I changed the JDK version to 1.7u51.
Regards
Dapeng
From: Gav [mailto:gmcdonald@apache.org]
Sent: Friday, August 05, 2016 8:14 AM
To: gmcdonald@apache.org
Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
Hello PMCs,
7 days ago I informed the builds@ and infrastructure@ mailing lists the intention to consolidate JDK versions in
our Jenkins instance. I gave 7 days notice. (Anyone configuring builds should be subscribed to the builds@
mailing list)
Today I find that there are still :-
109 jobs configured to use the 'latest1.8'
67 jobs configured to use the 'latest1.7'
7 jobs configured to use the 'latest 1.6'
45 jobs configured to use '1.8.0_66'
4 jobs configured to use '1.8.0_05'
4 jobs configured to use '1.8.0_11'
This wider distribution email to all PMC private lists is to let you know I'm going to delay the migration for '3 more days'
at which point I will migrate any remaining jobs myself.
I prefer of course that projects make the changes themselves.
Below I include a copy of the mail I sent 7 days ago FYI.
tl;dr please take a look at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
There are also plans to consoildate Maven and Ant versions - please do check the
builds@ mailing list archives for these notices - these are due to be migrated by
Sunday at the latest
Any questions please email me direct or reply to any of the builds@ mails.
HTH
Gav... (ASF Infrastructure Team)
---------- Forwarded message ----------
From: Gav <gm...@apache.org>>
Date: Fri, Jul 29, 2016 at 9:03 PM
Subject: Jenkins JDK Matrix - and consolidating of versions.
To: builds@apache.org<ma...@apache.org>, "infrastructure@apache.org<ma...@apache.org> Infrastructure" <in...@apache.org>>
Hi All,
So 99% of our Jenkins build machines are now puppetised with our configs in our Git repos.
Going forward this should make things easier to maintain the software (and versions of) on the nodes.
I went through all the JDK drop down options available in the Jenkins UI when
creating a build.The Confluence wiki page at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
lists all them all. When choosing a version to use I hope that this information will
prove useful - any changes made we will keep this page upto date.
However, some are not currently installed on the new puppetised
slaves (on purpose) and others we intend to consolidate down to fewer versions.
In contrast, we will be able to make newer release versions available quicker.
Once we are done with the JDKs, we'll move on to Maven, and then the rest.
Ok to specifics,
First major change to get out of the way is the removal of the 'auto install' JDK
versions. They overlap with installed versions and going forward we would rather
manage installation via Puppet and roll them out to all slaves in one hit.
Looking at the table in the linked wiki page above, this means we'll be removing
eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
To avoid confusion we'll also be removing the auto install 'latest1.6' 'latest1.7' and 'latest1.8' options.
The best options for 'latest' versions is the ones at the top of the table 'JDK 1.x (Latest)'
which are all installed on all nodes and managed via puppet.
I'll point out also that we have installed 'unlimited security' versions of 1.6,1.7,1.8 jdks.
Very recent addition is also that of the JDK 9 b128 Early Access Build. We hope you enjoy
this addition and please do give feedback on this version to the builds@ mailing list so we can pass it on - but certainly do not plan to base your releases on these 'ea' builds. I'll try my best to add new ea builds as they come through.
Last ones to mention are the IBM and Harmony versions. I'm not sure how much in use
these are so I'm holding off on installing these for now. Please do ask for a specific version
if needed. I'll drop the from the UI in time.
I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45, 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now, along with the auto install latest links. Please plan
on migrating your builds away from these versions before then.
Any follow questions, please do concentrate your email responses to the builds@ mailing list.
Thanks!
Gav... (On behalf of the Infrastructure Team)
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 5/08/2016 10:13am, Gav wrote:
> 7 days ago I informed the builds@ and infrastructure@ mailing lists the
> intention to consolidate JDK versions in
> our Jenkins instance. I gave 7 days notice.
I did this a few days ago for Cayenne. I also took the opportunity to add Java 9 just for laughs. That build failed because of MaxPermSize (now an error in Java 9 rather than a warning) which I now removed and ran it again. Let's see if it goes through, and whether Java 9 gives us any other errors.
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Fwd: Jenkins JDK Matrix - and consolidating of versions.
Posted by Werner Keil <we...@gmail.com>.
Dear All,
Do we have to make or request changes to the DeviceMap build jobs based on
that?
AFAIK we're still running Java 6 and unlesss changes are made that would
require 7 or 1.6 was dropped from Apache Jenkins I see no reason to change
it.
Cheers,
Werner
---------- Forwarded message ----------
From: Gav <gm...@apache.org>
Date: Fri, Aug 5, 2016 at 2:13 AM
Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
To: gmcdonald@apache.org
Hello PMCs,
7 days ago I informed the builds@ and infrastructure@ mailing lists the
intention to consolidate JDK versions in
our Jenkins instance. I gave 7 days notice. (Anyone configuring builds
should be subscribed to the builds@
mailing list)
Today I find that there are still :-
109 jobs configured to use the 'latest1.8'
67 jobs configured to use the 'latest1.7'
7 jobs configured to use the 'latest 1.6'
45 jobs configured to use '1.8.0_66'
4 jobs configured to use '1.8.0_05'
4 jobs configured to use '1.8.0_11'
This wider distribution email to all PMC private lists is to let you know
I'm going to delay the migration for '3 more days'
at which point I will migrate any remaining jobs myself.
I prefer of course that projects make the changes themselves.
Below I include a copy of the mail I sent 7 days ago FYI.
tl;dr please take a look at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
There are also plans to consoildate Maven and Ant versions - please do
check the
builds@ mailing list archives for these notices - these are due to be
migrated by
Sunday at the latest
Any questions please email me direct or reply to any of the builds@ mails.
HTH
Gav... (ASF Infrastructure Team)
---------- Forwarded message ----------
From: Gav <gm...@apache.org>
Date: Fri, Jul 29, 2016 at 9:03 PM
Subject: Jenkins JDK Matrix - and consolidating of versions.
To: builds@apache.org, "infrastructure@apache.org Infrastructure" <
infrastructure@apache.org>
Hi All,
So 99% of our Jenkins build machines are now puppetised with our configs in
our Git repos.
Going forward this should make things easier to maintain the software (and
versions of) on the nodes.
I went through all the JDK drop down options available in the Jenkins UI
when
creating a build.The Confluence wiki page at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
lists all them all. When choosing a version to use I hope that this
information will
prove useful - any changes made we will keep this page upto date.
However, some are not currently installed on the new puppetised
slaves (on purpose) and others we intend to consolidate down to fewer
versions.
In contrast, we will be able to make newer release versions available
quicker.
Once we are done with the JDKs, we'll move on to Maven, and then the rest.
Ok to specifics,
First major change to get out of the way is the removal of the 'auto
install' JDK
versions. They overlap with installed versions and going forward we would
rather
manage installation via Puppet and roll them out to all slaves in one hit.
Looking at the table in the linked wiki page above, this means we'll be
removing
eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
To avoid confusion we'll also be removing the auto install 'latest1.6'
'latest1.7' and 'latest1.8' options.
The best options for 'latest' versions is the ones at the top of the table
'JDK 1.x (Latest)'
which are all installed on all nodes and managed via puppet.
I'll point out also that we have installed 'unlimited security' versions of
1.6,1.7,1.8 jdks.
Very recent addition is also that of the JDK 9 b128 Early Access Build. We
hope you enjoy
this addition and please do give feedback on this version to the builds@
mailing list so we can pass it on - but certainly do not plan to base your
releases on these 'ea' builds. I'll try my best to add new ea builds as
they come through.
Last ones to mention are the IBM and Harmony versions. I'm not sure how
much in use
these are so I'm holding off on installing these for now. Please do ask for
a specific version
if needed. I'll drop the from the UI in time.
I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
along with the auto install latest links. Please plan
on migrating your builds away from these versions before then.
Any follow questions, please do concentrate your email responses to the
builds@ mailing list.
Thanks!
Gav... (On behalf of the Infrastructure Team)
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Suresh Marru <sm...@apache.org>.
Hi Gav,
When I change Airavata job from latest1.8 to JDK 1.8 (latest) an extra -XX shows up in command and the build fails. Any guidance on a fix?
Modules changed, recalculating dependency graph
Established TCP socket on 47606
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[Airavata] $ /home/jenkins/tools/java/latest1.8/bin/java -Xmx2g -Xms256m -XX -cp /home/jenkins/jenkins-slave/maven32-agent.jar:/home/jenkins/tools/maven/latest3/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/latest3/conf/logging jenkins.maven3.agent.Maven32Main /home/jenkins/tools/maven/latest3/ /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven32-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 47606
Unrecognized option: -XX
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
ERROR: Failed to launch Maven. Exit code = 1
Thanks,
Suresh
> On Aug 4, 2016, at 8:13 PM, Gav <gm...@apache.org> wrote:
>
>
>
> Hello PMCs,
>
> 7 days ago I informed the builds@ and infrastructure@ mailing lists the intention to consolidate JDK versions in
> our Jenkins instance. I gave 7 days notice. (Anyone configuring builds should be subscribed to the builds@
> mailing list)
>
> Today I find that there are still :-
>
> 109 jobs configured to use the 'latest1.8'
> 67 jobs configured to use the 'latest1.7'
> 7 jobs configured to use the 'latest 1.6'
>
> 45 jobs configured to use '1.8.0_66'
> 4 jobs configured to use '1.8.0_05'
> 4 jobs configured to use '1.8.0_11'
>
>
> This wider distribution email to all PMC private lists is to let you know I'm going to delay the migration for '3 more days'
> at which point I will migrate any remaining jobs myself.
>
> I prefer of course that projects make the changes themselves.
>
> Below I include a copy of the mail I sent 7 days ago FYI.
>
> tl;dr please take a look at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix <https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix>
>
> There are also plans to consoildate Maven and Ant versions - please do check the
> builds@ mailing list archives for these notices - these are due to be migrated by
> Sunday at the latest
>
> Any questions please email me direct or reply to any of the builds@ mails.
>
>
> HTH
>
> Gav... (ASF Infrastructure Team)
>
>
> ---------- Forwarded message ----------
> From: Gav <gmcdonald@apache.org <ma...@apache.org>>
> Date: Fri, Jul 29, 2016 at 9:03 PM
> Subject: Jenkins JDK Matrix - and consolidating of versions.
> To: builds@apache.org <ma...@apache.org>, "infrastructure@apache.org <ma...@apache.org> Infrastructure" <infrastructure@apache.org <ma...@apache.org>>
>
>
> Hi All,
>
> So 99% of our Jenkins build machines are now puppetised with our configs in our Git repos.
> Going forward this should make things easier to maintain the software (and versions of) on the nodes.
>
> I went through all the JDK drop down options available in the Jenkins UI when
> creating a build.The Confluence wiki page at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix <https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix>
>
> lists all them all. When choosing a version to use I hope that this information will
> prove useful - any changes made we will keep this page upto date.
> However, some are not currently installed on the new puppetised
> slaves (on purpose) and others we intend to consolidate down to fewer versions.
>
> In contrast, we will be able to make newer release versions available quicker.
>
> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>
> Ok to specifics,
>
> First major change to get out of the way is the removal of the 'auto install' JDK
> versions. They overlap with installed versions and going forward we would rather
> manage installation via Puppet and roll them out to all slaves in one hit.
>
> Looking at the table in the linked wiki page above, this means we'll be removing
> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> To avoid confusion we'll also be removing the auto install 'latest1.6' 'latest1.7' and 'latest1.8' options.
>
> The best options for 'latest' versions is the ones at the top of the table 'JDK 1.x (Latest)'
> which are all installed on all nodes and managed via puppet.
>
> I'll point out also that we have installed 'unlimited security' versions of 1.6,1.7,1.8 jdks.
>
> Very recent addition is also that of the JDK 9 b128 Early Access Build. We hope you enjoy
> this addition and please do give feedback on this version to the builds@ mailing list so we can pass it on - but certainly do not plan to base your releases on these 'ea' builds. I'll try my best to add new ea builds as they come through.
>
> Last ones to mention are the IBM and Harmony versions. I'm not sure how much in use
> these are so I'm holding off on installing these for now. Please do ask for a specific version
> if needed. I'll drop the from the UI in time.
>
> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45, 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now, along with the auto install latest links. Please plan
> on migrating your builds away from these versions before then.
>
> Any follow questions, please do concentrate your email responses to the builds@ mailing list.
>
> Thanks!
>
> Gav... (On behalf of the Infrastructure Team)
>
>
>
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Juan Pablo Santos Rodríguez <ju...@gmail.com>.
Nope, I can login, but haven't access to the configure screen :-/
We requested our jenkins job through Jira, and we've only requested a
change on it, which was also on jira, if I recall correctly. I don't
currently have access to my pc, so I can't fiddle around too much, but most
probably we can request configure permissions for our job :-?
br,
juan pablo
El 16 ago. 2016 4:52 p. m., "Harry Metske" <ha...@gmail.com>
escribió:
> JP? Do you have access?
>
> Op 16 aug. 2016 16:13 schreef "David Vittor" <dv...@gmail.com>:
>
> > Hi Harry,
> >
> > Yeah, I just logged in to Jenkins also, but no "Configure" option for me
> > either. Yes I think this is a authorization setting.
> >
> > I also had a look at the environment settings, but I'm not sure that is
> for
> > JSPWiki directly.
> > https://builds.apache.org/view/All/job/JSPWiki/414/injectedEnvVars/
> >
> > If we could get "configure" access, I'd be happy to update us. I think we
> > can also bump maven up from 3.0.4 to 3.3.9 without any issues.
> >
> > Cheers,
> > David V
> >
> >
> >
> > On Fri, Aug 5, 2016 at 10:05 PM, Harry Metske <ha...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > I subscribed to the builds@apache.org mailing list.
> > > I logged in the Jenkins and tried to check which JDK we were using, but
> > > there is no "Configure" option for me. Is this because I lack
> > > authorizations?
> > >
> > > See: https://builds.apache.org/view/All/job/JSPWiki/
> > >
> > > regards,
> > > Harry
> > >
> > >
> > >
> > > ---------- Forwarded message ----------
> > > From: Gav <gm...@apache.org>
> > > Date: 5 August 2016 at 02:13
> > > Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
> > > To: gmcdonald@apache.org
> > >
> > >
> > > Hello PMCs,
> > >
> > > 7 days ago I informed the builds@ and infrastructure@ mailing lists
> the
> > > intention to consolidate JDK versions in
> > > our Jenkins instance. I gave 7 days notice. (Anyone configuring builds
> > > should be subscribed to the builds@
> > > mailing list)
> > >
> > > Today I find that there are still :-
> > >
> > > 109 jobs configured to use the 'latest1.8'
> > > 67 jobs configured to use the 'latest1.7'
> > > 7 jobs configured to use the 'latest 1.6'
> > >
> > > 45 jobs configured to use '1.8.0_66'
> > > 4 jobs configured to use '1.8.0_05'
> > > 4 jobs configured to use '1.8.0_11'
> > >
> > >
> > > This wider distribution email to all PMC private lists is to let you
> know
> > > I'm going to delay the migration for '3 more days'
> > > at which point I will migrate any remaining jobs myself.
> > >
> > > I prefer of course that projects make the changes themselves.
> > >
> > > Below I include a copy of the mail I sent 7 days ago FYI.
> > >
> > > tl;dr please take a look at :-
> > >
> > > https://cwiki.apache.org/confluence/display/INFRA/JDK+
> > Installation+Matrix
> > >
> > > There are also plans to consoildate Maven and Ant versions - please do
> > > check the
> > > builds@ mailing list archives for these notices - these are due to be
> > > migrated by
> > > Sunday at the latest
> > >
> > > Any questions please email me direct or reply to any of the builds@
> > mails.
> > >
> > >
> > > HTH
> > >
> > > Gav... (ASF Infrastructure Team)
> > >
> > >
> > > ---------- Forwarded message ----------
> > > From: Gav <gm...@apache.org>
> > > Date: Fri, Jul 29, 2016 at 9:03 PM
> > > Subject: Jenkins JDK Matrix - and consolidating of versions.
> > > To: builds@apache.org, "infrastructure@apache.org Infrastructure" <
> > > infrastructure@apache.org>
> > >
> > >
> > > Hi All,
> > >
> > > So 99% of our Jenkins build machines are now puppetised with our
> configs
> > in
> > > our Git repos.
> > > Going forward this should make things easier to maintain the software
> > (and
> > > versions of) on the nodes.
> > >
> > > I went through all the JDK drop down options available in the Jenkins
> UI
> > > when
> > > creating a build.The Confluence wiki page at :-
> > >
> > > https://cwiki.apache.org/confluence/display/INFRA/JDK+
> > Installation+Matrix
> > >
> > > lists all them all. When choosing a version to use I hope that this
> > > information will
> > > prove useful - any changes made we will keep this page upto date.
> > > However, some are not currently installed on the new puppetised
> > > slaves (on purpose) and others we intend to consolidate down to fewer
> > > versions.
> > >
> > > In contrast, we will be able to make newer release versions available
> > > quicker.
> > >
> > > Once we are done with the JDKs, we'll move on to Maven, and then the
> > rest.
> > >
> > > Ok to specifics,
> > >
> > > First major change to get out of the way is the removal of the 'auto
> > > install' JDK
> > > versions. They overlap with installed versions and going forward we
> would
> > > rather
> > > manage installation via Puppet and roll them out to all slaves in one
> > hit.
> > >
> > > Looking at the table in the linked wiki page above, this means we'll be
> > > removing
> > > eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk
> 6.
> > > To avoid confusion we'll also be removing the auto install 'latest1.6'
> > > 'latest1.7' and 'latest1.8' options.
> > >
> > > The best options for 'latest' versions is the ones at the top of the
> > table
> > > 'JDK 1.x (Latest)'
> > > which are all installed on all nodes and managed via puppet.
> > >
> > > I'll point out also that we have installed 'unlimited security'
> versions
> > of
> > > 1.6,1.7,1.8 jdks.
> > >
> > > Very recent addition is also that of the JDK 9 b128 Early Access Build.
> > We
> > > hope you enjoy
> > > this addition and please do give feedback on this version to the
> builds@
> > > mailing list so we can pass it on - but certainly do not plan to base
> > your
> > > releases on these 'ea' builds. I'll try my best to add new ea builds as
> > > they come through.
> > >
> > > Last ones to mention are the IBM and Harmony versions. I'm not sure how
> > > much in use
> > > these are so I'm holding off on installing these for now. Please do ask
> > for
> > > a specific version
> > > if needed. I'll drop the from the UI in time.
> > >
> > > I intend to drop all the auto-install versions (they are 1.6u45,
> 1.7u45,
> > > 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from
> > now,
> > > along with the auto install latest links. Please plan
> > > on migrating your builds away from these versions before then.
> > >
> > > Any follow questions, please do concentrate your email responses to the
> > > builds@ mailing list.
> > >
> > > Thanks!
> > >
> > > Gav... (On behalf of the Infrastructure Team)
> > >
> >
>
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by Harry Metske <ha...@gmail.com>.
JP? Do you have access?
Op 16 aug. 2016 16:13 schreef "David Vittor" <dv...@gmail.com>:
> Hi Harry,
>
> Yeah, I just logged in to Jenkins also, but no "Configure" option for me
> either. Yes I think this is a authorization setting.
>
> I also had a look at the environment settings, but I'm not sure that is for
> JSPWiki directly.
> https://builds.apache.org/view/All/job/JSPWiki/414/injectedEnvVars/
>
> If we could get "configure" access, I'd be happy to update us. I think we
> can also bump maven up from 3.0.4 to 3.3.9 without any issues.
>
> Cheers,
> David V
>
>
>
> On Fri, Aug 5, 2016 at 10:05 PM, Harry Metske <ha...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I subscribed to the builds@apache.org mailing list.
> > I logged in the Jenkins and tried to check which JDK we were using, but
> > there is no "Configure" option for me. Is this because I lack
> > authorizations?
> >
> > See: https://builds.apache.org/view/All/job/JSPWiki/
> >
> > regards,
> > Harry
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: Gav <gm...@apache.org>
> > Date: 5 August 2016 at 02:13
> > Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
> > To: gmcdonald@apache.org
> >
> >
> > Hello PMCs,
> >
> > 7 days ago I informed the builds@ and infrastructure@ mailing lists the
> > intention to consolidate JDK versions in
> > our Jenkins instance. I gave 7 days notice. (Anyone configuring builds
> > should be subscribed to the builds@
> > mailing list)
> >
> > Today I find that there are still :-
> >
> > 109 jobs configured to use the 'latest1.8'
> > 67 jobs configured to use the 'latest1.7'
> > 7 jobs configured to use the 'latest 1.6'
> >
> > 45 jobs configured to use '1.8.0_66'
> > 4 jobs configured to use '1.8.0_05'
> > 4 jobs configured to use '1.8.0_11'
> >
> >
> > This wider distribution email to all PMC private lists is to let you know
> > I'm going to delay the migration for '3 more days'
> > at which point I will migrate any remaining jobs myself.
> >
> > I prefer of course that projects make the changes themselves.
> >
> > Below I include a copy of the mail I sent 7 days ago FYI.
> >
> > tl;dr please take a look at :-
> >
> > https://cwiki.apache.org/confluence/display/INFRA/JDK+
> Installation+Matrix
> >
> > There are also plans to consoildate Maven and Ant versions - please do
> > check the
> > builds@ mailing list archives for these notices - these are due to be
> > migrated by
> > Sunday at the latest
> >
> > Any questions please email me direct or reply to any of the builds@
> mails.
> >
> >
> > HTH
> >
> > Gav... (ASF Infrastructure Team)
> >
> >
> > ---------- Forwarded message ----------
> > From: Gav <gm...@apache.org>
> > Date: Fri, Jul 29, 2016 at 9:03 PM
> > Subject: Jenkins JDK Matrix - and consolidating of versions.
> > To: builds@apache.org, "infrastructure@apache.org Infrastructure" <
> > infrastructure@apache.org>
> >
> >
> > Hi All,
> >
> > So 99% of our Jenkins build machines are now puppetised with our configs
> in
> > our Git repos.
> > Going forward this should make things easier to maintain the software
> (and
> > versions of) on the nodes.
> >
> > I went through all the JDK drop down options available in the Jenkins UI
> > when
> > creating a build.The Confluence wiki page at :-
> >
> > https://cwiki.apache.org/confluence/display/INFRA/JDK+
> Installation+Matrix
> >
> > lists all them all. When choosing a version to use I hope that this
> > information will
> > prove useful - any changes made we will keep this page upto date.
> > However, some are not currently installed on the new puppetised
> > slaves (on purpose) and others we intend to consolidate down to fewer
> > versions.
> >
> > In contrast, we will be able to make newer release versions available
> > quicker.
> >
> > Once we are done with the JDKs, we'll move on to Maven, and then the
> rest.
> >
> > Ok to specifics,
> >
> > First major change to get out of the way is the removal of the 'auto
> > install' JDK
> > versions. They overlap with installed versions and going forward we would
> > rather
> > manage installation via Puppet and roll them out to all slaves in one
> hit.
> >
> > Looking at the table in the linked wiki page above, this means we'll be
> > removing
> > eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> > To avoid confusion we'll also be removing the auto install 'latest1.6'
> > 'latest1.7' and 'latest1.8' options.
> >
> > The best options for 'latest' versions is the ones at the top of the
> table
> > 'JDK 1.x (Latest)'
> > which are all installed on all nodes and managed via puppet.
> >
> > I'll point out also that we have installed 'unlimited security' versions
> of
> > 1.6,1.7,1.8 jdks.
> >
> > Very recent addition is also that of the JDK 9 b128 Early Access Build.
> We
> > hope you enjoy
> > this addition and please do give feedback on this version to the builds@
> > mailing list so we can pass it on - but certainly do not plan to base
> your
> > releases on these 'ea' builds. I'll try my best to add new ea builds as
> > they come through.
> >
> > Last ones to mention are the IBM and Harmony versions. I'm not sure how
> > much in use
> > these are so I'm holding off on installing these for now. Please do ask
> for
> > a specific version
> > if needed. I'll drop the from the UI in time.
> >
> > I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
> > 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from
> now,
> > along with the auto install latest links. Please plan
> > on migrating your builds away from these versions before then.
> >
> > Any follow questions, please do concentrate your email responses to the
> > builds@ mailing list.
> >
> > Thanks!
> >
> > Gav... (On behalf of the Infrastructure Team)
> >
>
Re: Jenkins JDK Matrix - and consolidating of versions.
Posted by David Vittor <dv...@gmail.com>.
Hi Harry,
Yeah, I just logged in to Jenkins also, but no "Configure" option for me
either. Yes I think this is a authorization setting.
I also had a look at the environment settings, but I'm not sure that is for
JSPWiki directly.
https://builds.apache.org/view/All/job/JSPWiki/414/injectedEnvVars/
If we could get "configure" access, I'd be happy to update us. I think we
can also bump maven up from 3.0.4 to 3.3.9 without any issues.
Cheers,
David V
On Fri, Aug 5, 2016 at 10:05 PM, Harry Metske <ha...@gmail.com>
wrote:
> Hi,
>
> I subscribed to the builds@apache.org mailing list.
> I logged in the Jenkins and tried to check which JDK we were using, but
> there is no "Configure" option for me. Is this because I lack
> authorizations?
>
> See: https://builds.apache.org/view/All/job/JSPWiki/
>
> regards,
> Harry
>
>
>
> ---------- Forwarded message ----------
> From: Gav <gm...@apache.org>
> Date: 5 August 2016 at 02:13
> Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
> To: gmcdonald@apache.org
>
>
> Hello PMCs,
>
> 7 days ago I informed the builds@ and infrastructure@ mailing lists the
> intention to consolidate JDK versions in
> our Jenkins instance. I gave 7 days notice. (Anyone configuring builds
> should be subscribed to the builds@
> mailing list)
>
> Today I find that there are still :-
>
> 109 jobs configured to use the 'latest1.8'
> 67 jobs configured to use the 'latest1.7'
> 7 jobs configured to use the 'latest 1.6'
>
> 45 jobs configured to use '1.8.0_66'
> 4 jobs configured to use '1.8.0_05'
> 4 jobs configured to use '1.8.0_11'
>
>
> This wider distribution email to all PMC private lists is to let you know
> I'm going to delay the migration for '3 more days'
> at which point I will migrate any remaining jobs myself.
>
> I prefer of course that projects make the changes themselves.
>
> Below I include a copy of the mail I sent 7 days ago FYI.
>
> tl;dr please take a look at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
>
> There are also plans to consoildate Maven and Ant versions - please do
> check the
> builds@ mailing list archives for these notices - these are due to be
> migrated by
> Sunday at the latest
>
> Any questions please email me direct or reply to any of the builds@ mails.
>
>
> HTH
>
> Gav... (ASF Infrastructure Team)
>
>
> ---------- Forwarded message ----------
> From: Gav <gm...@apache.org>
> Date: Fri, Jul 29, 2016 at 9:03 PM
> Subject: Jenkins JDK Matrix - and consolidating of versions.
> To: builds@apache.org, "infrastructure@apache.org Infrastructure" <
> infrastructure@apache.org>
>
>
> Hi All,
>
> So 99% of our Jenkins build machines are now puppetised with our configs in
> our Git repos.
> Going forward this should make things easier to maintain the software (and
> versions of) on the nodes.
>
> I went through all the JDK drop down options available in the Jenkins UI
> when
> creating a build.The Confluence wiki page at :-
>
> https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
>
> lists all them all. When choosing a version to use I hope that this
> information will
> prove useful - any changes made we will keep this page upto date.
> However, some are not currently installed on the new puppetised
> slaves (on purpose) and others we intend to consolidate down to fewer
> versions.
>
> In contrast, we will be able to make newer release versions available
> quicker.
>
> Once we are done with the JDKs, we'll move on to Maven, and then the rest.
>
> Ok to specifics,
>
> First major change to get out of the way is the removal of the 'auto
> install' JDK
> versions. They overlap with installed versions and going forward we would
> rather
> manage installation via Puppet and roll them out to all slaves in one hit.
>
> Looking at the table in the linked wiki page above, this means we'll be
> removing
> eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
> To avoid confusion we'll also be removing the auto install 'latest1.6'
> 'latest1.7' and 'latest1.8' options.
>
> The best options for 'latest' versions is the ones at the top of the table
> 'JDK 1.x (Latest)'
> which are all installed on all nodes and managed via puppet.
>
> I'll point out also that we have installed 'unlimited security' versions of
> 1.6,1.7,1.8 jdks.
>
> Very recent addition is also that of the JDK 9 b128 Early Access Build. We
> hope you enjoy
> this addition and please do give feedback on this version to the builds@
> mailing list so we can pass it on - but certainly do not plan to base your
> releases on these 'ea' builds. I'll try my best to add new ea builds as
> they come through.
>
> Last ones to mention are the IBM and Harmony versions. I'm not sure how
> much in use
> these are so I'm holding off on installing these for now. Please do ask for
> a specific version
> if needed. I'll drop the from the UI in time.
>
> I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
> 1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
> along with the auto install latest links. Please plan
> on migrating your builds away from these versions before then.
>
> Any follow questions, please do concentrate your email responses to the
> builds@ mailing list.
>
> Thanks!
>
> Gav... (On behalf of the Infrastructure Team)
>
Fwd: Jenkins JDK Matrix - and consolidating of versions.
Posted by Harry Metske <ha...@gmail.com>.
Hi,
I subscribed to the builds@apache.org mailing list.
I logged in the Jenkins and tried to check which JDK we were using, but
there is no "Configure" option for me. Is this because I lack
authorizations?
See: https://builds.apache.org/view/All/job/JSPWiki/
regards,
Harry
---------- Forwarded message ----------
From: Gav <gm...@apache.org>
Date: 5 August 2016 at 02:13
Subject: Fwd: Jenkins JDK Matrix - and consolidating of versions.
To: gmcdonald@apache.org
Hello PMCs,
7 days ago I informed the builds@ and infrastructure@ mailing lists the
intention to consolidate JDK versions in
our Jenkins instance. I gave 7 days notice. (Anyone configuring builds
should be subscribed to the builds@
mailing list)
Today I find that there are still :-
109 jobs configured to use the 'latest1.8'
67 jobs configured to use the 'latest1.7'
7 jobs configured to use the 'latest 1.6'
45 jobs configured to use '1.8.0_66'
4 jobs configured to use '1.8.0_05'
4 jobs configured to use '1.8.0_11'
This wider distribution email to all PMC private lists is to let you know
I'm going to delay the migration for '3 more days'
at which point I will migrate any remaining jobs myself.
I prefer of course that projects make the changes themselves.
Below I include a copy of the mail I sent 7 days ago FYI.
tl;dr please take a look at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
There are also plans to consoildate Maven and Ant versions - please do
check the
builds@ mailing list archives for these notices - these are due to be
migrated by
Sunday at the latest
Any questions please email me direct or reply to any of the builds@ mails.
HTH
Gav... (ASF Infrastructure Team)
---------- Forwarded message ----------
From: Gav <gm...@apache.org>
Date: Fri, Jul 29, 2016 at 9:03 PM
Subject: Jenkins JDK Matrix - and consolidating of versions.
To: builds@apache.org, "infrastructure@apache.org Infrastructure" <
infrastructure@apache.org>
Hi All,
So 99% of our Jenkins build machines are now puppetised with our configs in
our Git repos.
Going forward this should make things easier to maintain the software (and
versions of) on the nodes.
I went through all the JDK drop down options available in the Jenkins UI
when
creating a build.The Confluence wiki page at :-
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
lists all them all. When choosing a version to use I hope that this
information will
prove useful - any changes made we will keep this page upto date.
However, some are not currently installed on the new puppetised
slaves (on purpose) and others we intend to consolidate down to fewer
versions.
In contrast, we will be able to make newer release versions available
quicker.
Once we are done with the JDKs, we'll move on to Maven, and then the rest.
Ok to specifics,
First major change to get out of the way is the removal of the 'auto
install' JDK
versions. They overlap with installed versions and going forward we would
rather
manage installation via Puppet and roll them out to all slaves in one hit.
Looking at the table in the linked wiki page above, this means we'll be
removing
eight (8) drop down options , 5 of those jdk 8, 2 x jdk 7 and 1 x jdk 6.
To avoid confusion we'll also be removing the auto install 'latest1.6'
'latest1.7' and 'latest1.8' options.
The best options for 'latest' versions is the ones at the top of the table
'JDK 1.x (Latest)'
which are all installed on all nodes and managed via puppet.
I'll point out also that we have installed 'unlimited security' versions of
1.6,1.7,1.8 jdks.
Very recent addition is also that of the JDK 9 b128 Early Access Build. We
hope you enjoy
this addition and please do give feedback on this version to the builds@
mailing list so we can pass it on - but certainly do not plan to base your
releases on these 'ea' builds. I'll try my best to add new ea builds as
they come through.
Last ones to mention are the IBM and Harmony versions. I'm not sure how
much in use
these are so I'm holding off on installing these for now. Please do ask for
a specific version
if needed. I'll drop the from the UI in time.
I intend to drop all the auto-install versions (they are 1.6u45, 1.7u45,
1.7u51, 1.8.0_05, 1.8.0_11, 1.8.0_45, 1.8.0_25, 1.8.0_66) 7 days from now,
along with the auto install latest links. Please plan
on migrating your builds away from these versions before then.
Any follow questions, please do concentrate your email responses to the
builds@ mailing list.
Thanks!
Gav... (On behalf of the Infrastructure Team)