Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
From: =?ISO-8859-1?Q?Herv=E9?= BOUTEMY <herve.boutemy@free.fr>
To: builds@apache.org
Subject: Re: JDK names on Windows nodes & Jenkinsfile
Date: Sat, 25 Mar 2017 06:23:43 +0100
Message-ID: <1859728.nXJGUVqyHz@herve-desktop>
User-Agent: KMail/5.2.3 (Linux/4.8.0-42-generic; KDE/5.26.0; x86_64; ; )
In-Reply-To: <6DE8613F-C70D-43A0-AB02-6654EDEACAEA@16degrees.com.au>
References: <1663789.AU79qohh2U@herve-desktop> <6DE8613F-C70D-43A0-AB02-6654EDEACAEA@16degrees.com.au>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
archived-at: Sat, 25 Mar 2017 05:23:49 -0000

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
> 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?

> > We're using Jenkinsfiles, with JDK names coded inside (we =3D Maven, bu=
t I
> > suppose others do the same): until now, it was not fun to have a differ=
ent
> > 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=
=2E)
thank you

> > 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 the=
m=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-1363=
2=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 genera=
l)

Regards,

Herv=C3=A9

>=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.acti=
on?
> > pageId=3D65147537