You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by Harry Metske <ha...@gmail.com> on 2016/08/05 12:05:10 UTC
Fwd: Jenkins JDK Matrix - and consolidating of versions.
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 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)
>