►
From YouTube: Java 11 & Java 17
Description
Jenkins Contributor Summit June 25, 2021 - Java 11 and Java 17
slides https://docs.google.com/presentation/d/1i1gkUQ0Ha-CRgFvRRpRWUDjbpPr383D0DSywLGAFN-Y/edit?usp=sharing
A
A
A
A
All
right,
so
I
think
I
think
the
the
crucial
questions
here.
Maybe
let's,
let's
start
the
the
conversations
mike
you
had,
you
had
assembled
some
initial
slides.
Do
we
want
to
look
at
those
first
as
a
first
first
conversation,
starter
and
I'll
take
some
notes
in
the
the
notes,
while
we're
discussing.
A
A
Yeah
yeah,
so
the
one
of
the
one
of
the
points
there
is
we
are.
We
are
now
in
the
jenkins.io
documentation,
recommending
users
use
java
11
and
we're
guiding
them
to
use
java
11
in
the
docker
images
that
we
build
and
in
other
other
locations
suggesting
it
still.
The
java
11
adoption
rate
is,
is
relatively
lower
right.
It's
most
of
the
jenkins
users
are
still
running
java.
8.
A
A
A
C
A
D
A
A
E
A
A
A
B
And
what's
what's
next,
I'm
not
aware
of
anything
offhand,
and
it's
mostly
because
I
haven't
maybe
dug
deep
enough,
but
I'm
not
aware
of
any
major
java,
11
related
updates
and
for
the
september
lts,
but
I'm
not
as
involved
day
to
day
and
in
some
of
that,
so
I
don't
it's
quite
possible.
There's
some
things
I
don't
know
about.
I
think,
if
anything
it'll
just
be
incremental,
you
know.
Maybe
some
more
plug-ins
have
been
fixed.
A
So
I
had
started
on
that.
First
bullet
I
had
started
a
mailing
list
thread
proposing
that
we
would
switch
the
switch
additional
defaults
to
java
11.
with
the
september
lts.
The
particular
examples
there
were
the
docker
images.
So
today
we
ship
a
docker
image,
that's
based
on
debian
with,
so
we
have
a
docker
image
named
jenkins
jenkins,
colon
lts.
A
So
it's
ambiguously
named
in
terms
of
it
doesn't
promise
what
jdk
it's
running.
It
doesn't
promise
what
operating
system
it's
running
and
my
proposal
was
september-
might
be
a
good
time
to
upgrade
its
operating
system
from
debbie
and
buster.
The
current
thing:
it's
shipping
to
debian
bullseye,
so
debian
from
debian
10
to
debian,
11
and
use
that
same
place
to
upgrade
that
thing
from
jdk
8
to
jdk
11
as
the
thing
we're
shipping.
A
A
And
I
think
I
think
you've
got
a
good
point,
james
and,
and
that
actually
is
a
it
was
one
of
the.
So
when
the
last
time
we
did
a
docker
change,
what
we
did
is
we
did
it
sort
of
midstream
and,
and
one
concept
might
be
what
if
we
did,
the
switch
from
the
the
image
switch
in
a
weekly
first
and
change
the
docker
image
weekly,
four
or
six
weeks
prior
to
lts
and
then
admitted
we
will
change
the
lts
on
a
dot
one.
A
A
A
A
We
are
publishing
both
a
java
8
and
a
java
11
image
and
and
the
change
would
be
that's
actually
a
very
good
point.
Today.
We
have
a
thing
named
jenkins,
jenkins,
colon
latest,
and
the
proposal
was
switch
that
to
java
11,
but
the
problem
is
that
leaves
no
docker
image.
That's
delivering
java
8
then
for
weekly.
A
Yeah-
and
I
think
I
think
that's
a
good
idea
that
maybe
we
should
declare
all
right
to
keep
to
keep
transition
viable.
We
say:
look,
we
admit
we
were
ambiguous.
We
should
have
had
an
image
all
the
while
that
was
called
jdk8
and
now
we're
going
to
create
one
call.
It
jenkins
jenkins,
colon
jdk8
for
those
who
want
to
remain
with
jdk8.
A
G
A
C
Yeah
right
now
we
release
and
then
the
default
for
for
the
ddk8
and
also
we
we
release
lts
dash
gtk11.
If
I
record
currently
so
we
can
add
another
tag
that
is
lts
or
whatever
we
version.
We
want
to
release
dash
gdp8
and
that's
it.
We
keep
the
default
with
11
and
we
release
another
two
tax,
one
for
gdp8
and
another
for
gdk811.
A
Right,
okay,
good,
so
so
that
that
makes
sense
to
you
marcel.
I
think
that
would
not
affect
your
your
system
at
all
right,
because
you've
already
made
your
base
image,
use
the
dash
jdk
11
variant,
not
affected
by
that
right
and-
and
so
I
I
think,
that's
that
at
least
for
me
seems
viable
mike.
Do
you
see
any
barriers
to
that
kind
of
idea?
Anything
that
we
should
be
worried
about?
I
mean.
B
I
don't
really
know
any
way
around
that,
because
I
can't
really
change
that
name.
Pattern
of
the
jenkins
jenkins
go
on
latest
so
that
there's
only
ever
explicit
jdk
version.
So
as
long
as
we
do
a
good
job
of
communicating
across
the
mediums
that
we've
made
this
switch
in
the
default,
but
you're
welcome
to
still
pick
a
jdk
specific,
whether
it's
8
or
11
base
image
for
any
given
release.
A
Okay,
good
that
make
that
makes
sense
to
me
all
right
so
so
now
that
that
touches
and
the
slide
has
the
next
topic
is
java.
17.
are
there
other
things
we
need
to
discuss
around
java
11.?
For
me,
what
what's
been
proposed
feels
viable
and
answers.
One
of
my
big
concerns,
which
was
some
of
the
threads
on
the
on
the
initial
september.
Lts
idea,
said:
hey,
let's
just
drop
java
8
at
at
september,
and
for
me
that's
too
big
of
a
drop
this
soon
it
would.
A
It
feels
like
to
me
we
need
three
or
six
months
more
than
that
at
least
to
get
the
word
out
to
get
more
people
on
to
java
11
before
we
would
dare
consider
dropping
java
8.
do
others
have
a
different
approach
on
that.
Do
you
feel
differently
than
that?
I'm
I'm
admitting
I'm
giving
my
biases
to
compatibility
and
retaining
things
rather
than
moving
rapidly
to
job
11,
fully.
D
You
know,
because
one
thing
I
think
you
have
to
remember
for
some
people
like,
for
example,
one
of
the
reasons
like
we
have
a
technical
reason
for
having
to
stick
with
java.
We
also
have
a
procedural
one,
because
we
do
a
lot
of
work
for
the
us
government
and
we've
been
through
multiple
rounds
of
compliance
and
stuff.
I
know
there's
better
ways
of
doing
that,
but
the
other
one
also
is
that
with
open
gdk,
the
active
support
ends
in
2022,
but
they're
continuing
support
for
security
to
2025.
D
A
G
The
yeah
the
end
of
the
end
of
support
for
java
8
lts,
is
at
least
may
2026
java
11
from
adopt
jdk
java
11
is
at
least
october
2024
yeah.
So
so
so
they
by
moving
to
java
11,
you
end
up
with
less
support
or
less
of
a
date,
but
you
know
the
the
idea
is
one
once
you've
moved
to
java
11
moving
to
12,
13,
14,
15
and
stuff,
it
is
a
lot
easier
yeah.
B
A
Good
point:
okay,
so
your
your
point
is
it's
best
to
keep
pace
with
the
java
world.
I've
been
less
concerned
about
the
13
14
15
16,
because
they
weren't
lts
and
so
yeah
their
life
spans.
What?
If
I
remember
right
only
like
six
months
or
12
months
of
support,
whereas
17,
I
think
they
intend-
and
I
haven't
seen
any
variants
from
that
of
they
really
intend
to
make
it
a
long-term
support,
release
comparable
to
java
11.
A
G
A
Not
and
they're,
I
think,
you're
correct.
There
certainly
are
so
it's
not
enough
for
us
just
to
update
the
the
the
controller
images.
I
think
we
have
to
update
the
agent
images
with
a
similar
naming
pattern,
and-
and
so
that
means
the
agent
images
would
get
a
dash
jdk8
suffix
at
the
same
time
and
they
would
get
switch
their
default.
A
G
Do
you
I
don't
know,
because
a
version
of
remoting
goes
into
a
weekly
and
a
version
of
remoting
goes
into
lts
and
those
versions
should
be
different,
and
ideally
you
want
to
use
a
version
of
remoting
in
the
agent
that
matches
the
controller.
You
don't
want
to
use
a
newer
version
of
of
something
on
on
a
agent
than
is
on
the
controller.
I
know
you
can
use
an
older
version
on
an
agent
than
is
in
the
controller,
but
I'm
not
sure
it
will
necessarily
work
the
other
way
around.
G
C
C
A
Yeah,
so
we've
got:
we've
got
mike
posted
in
the
chat,
the
link
to
a
list
of
the
images
that
I
think
would
need
adjustment,
and
so
the
jenkins
agent
is
a
base
image,
but
then
we
it's
turned
into
two
images
that
are
used
for
for
actual
agents
right
jenkins,
ssh
dash
agent,
yvonne.
I
think
that's
the
one
where
you
said
the
remoting
is
actually
downloaded
from
the
controller
to
the
agent.
B
B
A
You
ask
a
fascinating
question
because
I
I
failed
to
tell
people
that
ci.jenkins.io
has
been
running
java
11
for
I
think
a
year
or
more,
and
so
so
we're
already.
If
I
remember
correctly,
let
me
double
check
just
to
be
sure,
but
I
think
it's,
I
think
it's
already
on
java
11
and
has
been
for
an
extended
period.
G
A
Yeah,
so
so,
as
far
as
I
can
tell,
I
look
at
our
agents
on
on
ci.jenkins.io
and
the
ec2
agents
are
definitely
running
java
11,
but
then
they
have
inside
there
a
a
target
or
a
label
named
maven
and
that
definitely
uses
java
8.
And
if
you
want
to
use
or
or
if
you
want
to
use
java
11
with
maven,
you
have
to
call
from
maven
dash
11..
A
A
A
A
Moment:
okay,
so
testing
testing
the
waters,
then
we
said
earlier
and
and
I'm
prone
to
propose
a
jenkins
enhancement
proposal
that
would
describe
this
more
precisely
that
what
we
would
do
is
four
to
six
weeks
prior
to
september
lts.
We
would
roll
the
controller
images
for
weekly
so
that
they
are
using
java
11
instead
of
java
8
in
in
their
default
images.
The
latest
the
image
colon
latest
and
the
the
others
like
that
which
have
no
java
version
number
included
in
them.
A
We
would
add
a
jdk8
image
so
that
people
have
it
to
fall
back
to
if
they
need
it,
and
then
we
would
watch
for
those
four
to
six
weeks
to
see
if
there
were
any
disasters
detected.
That
cause
would
cause
us
to
roll
back
that
change
before
september
lts,
then
similar
change
in
the
september
lts
now
james.
I
think
you
had
concerns
about
too
many
the
the
changes
I
was
describing
operating
system
update
java
11
being
too
many
are
there?
Is
there
a
subset?
G
G
G
A
G
A
A
B
A
With
the
analogy
okay,
so
I'm
not
sure
who
the
pig
is,
but
I
feel
like
the
pig
and
I
I
feel
like
that,
if,
if
things
go
badly
wrong
I'll
I'll
hear
about
it
all
sorts
of
ways,
but
even
as
the
in
that
role,
I
still
feel
like.
We've
got
a
viable
proposal
to
say:
hey
we're
going
to
allow
an
escape
hatch.
A
A
Yeah
very
good,
okay,
anything
else,
and
so
we're
we're
about
45
minutes
into
this
session.
We've
got
about
another
15
minutes.
We've
got
two
topics
I
would
propose.
We
talked
java
17
next,
just
to
see
what
we
think
about
it,
but
I
still
want
to
get
to
the
what
kind
of
time
frame
would
we
consider
or
envision
for
drop
eventual
dropping
support
of
8.?