Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
From: Gavin McDonald <gavin@16degrees.com.au>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_B4ED12D9-3588-4160-BF77-053A70778207"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: JDK names on Windows nodes & Jenkinsfile
Date: Sun, 26 Mar 2017 18:12:36 +1100
References: <1663789.AU79qohh2U@herve-desktop>
 <6DE8613F-C70D-43A0-AB02-6654EDEACAEA@16degrees.com.au>
 <1859728.nXJGUVqyHz@herve-desktop>
To: builds@apache.org
In-Reply-To: <1859728.nXJGUVqyHz@herve-desktop>
Message-Id: <48E23651-9431-491B-BD36-14BAFDA10704@16degrees.com.au>
archived-at: Sun, 26 Mar 2017 07:15:18 -0000

--Apple-Mail=_B4ED12D9-3588-4160-BF77-053A70778207
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

Please see:-

=
https://builds.apache.org/view/I/view/Infrastructure/job/infra-test-all-pi=
peline/ =
<https://builds.apache.org/view/I/view/Infrastructure/job/infra-test-all-p=
ipeline/>=20

and

=
https://github.com/apache/infrastructure-test/blob/master/Jenkinsfile.samp=
le =
<https://github.com/apache/infrastructure-test/blob/master/Jenkinsfile.sam=
ple>=20

tl=E2=80=99dr it is perfectly possible to use the same jdk|maven|ant =
latest links for both Windows
and Ubuntu.

Overriding tool location variables on the Windows machines have made =
this possible.

recap: using a Jenkinsfile or tool locations or drop down lists all are =
possible for using=20
the same (latest) link for Windows and Ubuntu.

I=E2=80=99ll add this information to our wiki Infra space docs.

Gav=E2=80=A6

> On 25 Mar 2017, at 4:23 pm, Herv=C3=A9 BOUTEMY <herve.boutemy@free.fr> =
wrote:
>=20
> Le samedi 25 mars 2017, 05:28:37 CET Gavin McDonald a =C3=A9crit :
>>> On 24 Mar 2017, at 2:55 pm, Herv=C3=A9 BOUTEMY =
<herve.boutemy@free.fr> wrote:
>>>=20
>>> Hi,
>>>=20
>>> It seems new JDKs were added to Windows nodes recently [1]: instead =
of
>>> "JDK
>>> 1.8 (unlimited security) 64-bit Windows only", we now have 2 =
options: "JDK
>>> 1.8.0_92 (unlimited security) 64-bit Windows only" and "JDK =
1.8.0_121
>>> (unlimited security) 64-bit Windows only".
>>>=20
>>> Having new JDKs is great, but changing names is not great :)
>>=20
>> Yes I realise that and am sorry for the change - however we have also =
been
>> told that it would be great if the drop down options (and in turn =
tool
>> location variables) had versions is them - JDK 1.8 by itself was not
>> complete enough for some people.
> yes, different projects with different requirements: each requirement =
is=20
> valid, then if we can support both, please :)
>=20
>>=20
>> Which then led to renaming the existing link and adding a new version =
in
>> also.
> sorry to be picky: I saw the new "JDK Latest (Windows Only)" entry
> *Could it be renamed to "JDK 1.8 Latest (Windows Only)"*, to match =
general=20
> convention, please?
>=20
>>> We're using Jenkinsfiles, with JDK names coded inside (we =3D Maven, =
but I
>>> suppose others do the same): until now, it was not fun to have a =
different
>>> JDK names for Linux and Windows nodes, but now having to follow very
>>> precise JDK name on Windows nodes is a new hurdle.
>>>=20
>>> Is it possible:
>>> 1. to have a JDK 8 alias on Windows that won't change over time, =
even if
>>> detailed version changes (like "JDK 1.x (latest)" on Ubuntu =
nodes=E2=80=9D?
>>=20
>> Sure , we have latest links all over the place and do try to actually =
keep
>> them updated these days (and not just for Java, but Ant, Maven and =
others.)
> thank you
>=20
>>> 2. ideally to have the same name on Windows as on Linux nodes?
>>=20
>> Yes, more thought needed on this though - drop down options require a
>> defined JAVA_HOME - a path to the location as you well know, and that =
is
>> different for Linux and Windows. Currently its easier in a =
Jenkinsfile to
>> seperate out the Windows and Linux nodes I imagine.
> this windows specific tools naming convention adds some complexity to =
the=20
> Jenkinsfile: ideally, it would be great if we could avoid it.
> But I imagine we're trading complexity for Jenkins administrators with=20=

> complexity for Jenkins users: I don't really know how to really =
compare them=20
> in a neutral way, I'm a user, I know my Jenkinsfile complexity, but I =
don't see=20
> the complexity for Jenkins admin. I imagine that's what's behind =
INFRA-13632=20
> issue: finding a reasonable complexity for admins that will ease life =
for=20
> developpers (since having Windows specific tools names are a pain in =
general)
>=20
> Regards,
>=20
> Herv=C3=A9
>=20
>>=20
>> Gav=E2=80=A6
>>=20
>>> And of course, if I can help to make this happen, just tell me what =
to do.
>>>=20
>>> Regards,
>>>=20
>>> Herv=C3=A9
>>>=20
>>> [1] =
https://cwiki.apache.org/confluence/pages/viewpreviousversions.action?
>>> pageId=3D65147537
>=20
>=20


--Apple-Mail=_B4ED12D9-3588-4160-BF77-053A70778207--