►
From YouTube: 2022 03 25 Platform SIG
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
it's
the
25th
of
march
2022.
This
is
the
jenkins
platform,
sig
special
interest
group
meeting
today's
agenda
items:
we've
got
open
action
items,
docker
agent,
support
editions,
linux
packages
for
system
d,
java
11
for
jenkins
core
operating
system,
support
policy
exit
life
cycle
changes.
I
think
we'll
hold
on
this
one
and
replacing
these
these
last
two
will
will
hold
not
bother
with
them
today
at
all
because
they
need
more
discussion
in
in
the
groups,
any
other
topics
that
need
to
be
added
here.
A
A
A
A
A
A
B
I
think
we,
I
know
we
have
some
road
map
time
as
far
as
when
the
I
believe
it's
the
2019
lts
or
the
1809
image,
it's
hard
to
say
how
it's
listed
as
we
have
some.
We
have
some
time.
That's
still
going
to
be
supported
and
I
believe
I
don't
have
the
exact
version,
but
I
think
it's
kubernetes
123
that
provides.
B
That
starts
to
have
support
for
the
2022
ltsc
image,
and
I
don't
think
I
I
don't
know
if
the
jenkins
infrastructure
team
is
using
that
for
that,
but
at
least
for
the
kubernetes
agent
images,
I
don't
believe
that's
available
on
aws
or
azure
at
this
time.
A
Yeah-
and
we
are,
I
think,
still
we
may
still
be
at
1.21,
so
the
jenkins
infra
is
definitely
not
using
1.23
1.23,
yet
yeah.
Now
they
we,
we
tend
to
do
a
kubernetes
upgrade
pretty
much
every
quarter,
and
so
so
I
suspect
we'll
be
close
to
that.
But
that
may
mean
we're
three
to
six
months
away
before
we
can
use
the
image.
B
Has
the
adopt-
or
I
don't
know
if
it's
the
adopt
open,
jdk
or
who
is
hosting
the
jvm
portion
of
that
image?
Has
that
been
created
already
or
is
that
what
the
pull
request.
A
Was
created
for,
I
think
I
think
we
structure
our
own
image
based
on
the
windows
server
core
base,
and
then
we
put
tamarin
onto
it
ourselves.
Okay,.
B
A
I
don't
think
we're
relying
on
them
to
give
us
an
operating
system
image.
At
least
we
haven't
been
on
the
linux
side.
We've
we've
intentionally
shifted
away
from
relying
on
somebody
else,
giving
us
the
operating
system
image.
Instead,
we
take
it
from
the
provider
like
from
alma
linux
or
ubi
or
or
debian,
and
then
we
use
their
base
image
and
then
we
layer
tamarin
as
the
as
the
jdk
on
top
of
it.
Okay.
A
All
right,
good,
excellent,
okay,
so
we've
got
we've
got
docker
agent.
Support
then
seems
like
it's
not
not
crushingly
urgent
right
now,
but
we
can
go
ahead
with
it
and
the
positives
are
are
ahead.
For
us.
That's
great,
I
hope,
someday
microsoft
will
get
out
of
the
requirement
that
we
have
to
use
an
exact
matching
kernel,
but
we're
not
there
yet.
A
All
right,
mike
anything
else
from
you
on
windows,
server,
2022,
ltsc,
that
we
need
to
be
aware
of
not
that
I
can
think
of
at
the
moment.
Okay,
all
right
good!
So
next
topic,
then,
was
the
linux
packages
using
systemd
instead
of
system
five
in
it
we
just
had
a
blog
post
published
today,
giving
more
details,
some
history,
etc.
It's
a
it's,
a
truly
a
brilliant
blog
post.
Let's
see
if
it's
visible,
already
bowser
crow
did
it.
A
It's
got
some
great
history
in
it
of
hey:
let's
go
all
the
way
back
to
solaris
into
real
system,
five
ancient
stuff
and
talks
about
2010s.
How
change
just
came
in
a
nice
nice
blog
post
worth
reading,
but
in
terms
of
the
the
relatively
low
rate
of
bugs,
even
for
such
a
large
change
and
we're
going
to
continue.
It
looks
good
it's
in
in
the
lts
already
and
in
weekly.
B
Was
there
any
pushback
or
any
questions
for
operating
systems
that
don't
have
system
d
in
the
in
customers
that
still
want
to
customers
of?
I
guess
the
jenkins
platform
that
want
to
use
that.
B
B
A
Since
it's
no
longer
supported
by
amazon,
the
jenkins
project
stance
is
that
if
the
operating
system
vendor
doesn't
support
it,
we
don't
either
okay
and
so
amazon
linux,
one
that
was
easy.
But
there
is
a
current
operating
system
version,
a
linux
that
does
not
do
systemd
dev1
and
we've
had
at
least
one
user.
Who
said
hey?
Could
you
please
not
abandon
support
for
init
scripts,
and
so
what
basel
did
is
he's
actually
continuing
to
deliver
the
init
scripts
so
that
they
should
still
be
able
to
use
it?
A
A
Yeah
good
question
very
good
question
now
the
for
me:
it's
a
it's
a
really
it's
a
very
nice
story,
the
number
of
tests
that
are
running
now,
because
what
basel
did
before
he
started
the
work
on
systemd.
Is
he
implemented
a
bunch
of
tests
for
installation
on
all
sorts
of
interesting
variants,
including
amazon,
linux
2,
for
example?
A
A
A
A
A
A
A
And
it's
based
on
this,
what
we
actually
test
there
are
three
levels
we
support
it
and
supported
means.
We've
got
something,
that's
tested
and
we're
running
some
test
automation.
So,
for
example,
we
test
regular
on
amd64
we
test
on
arm64,
on
system
390
and
on
power,
pc
and
and
those
test
results.
We
can
monitor
them
and
see
that
hey
they're
well
behaved
that
gives
us
a
level
one
platform
level.
Two
platforms,
we're
willing
to
consider
patches
for
these,
but
we
don't
automate
it.
We
don't
run
automated
tests
and
we
don't.
A
A
Then
the
level
three
is:
if
the
vendor
doesn't
support
it,
we
don't
support
it
and
we
will
not
accept
patches
to
attempt
support.
So
as
an
example,
we
had
a
question
just
recently.
What
about
ubuntu
1604
and
the
answer
is:
that's
a
level
three
platform.
It
happens
to
work,
but
that's
a
level
three
platform,
because
the
vendor
does
not
support
it.
B
I
had
one
mark,
I
know
with
java
11
coming
out
what
I
guess,
what
topics
are
there
for
java
17,
because
I
know
java
11's
initial.
I
think
it's
what
the
initial
end
of
life
is
next
year,
so
we
have
about
a
year
of
run
time
on
11.,
like
what
like
next
steps
for
17
like
proposed
timeline
on
the
jenkins
platform
of
when
it's
going
to
be
moving
to
17.
A
Good
good
question:
so
we
just
had
a
blog
post
that
came
out
announcing
preview
availability
of
of
java
17
support.
So
that's
that's
a
good
one.
Basel
has
found
that,
while
he's
doing
the
java
11
work
he's
visiting
many
of
the
same
places
that
will
need
thought
for
java
17,
so
he's
been
doing
java
17
in
parallel,
and
so
this
preview
release
this
preview
preview
availability
gives
us
a
good
way
for
people
to
help
us
with
the
evaluation
and
we're
visiting
the
same
things
that
we
would
visit.
A
We
would
have
to
visit
for
java
11
anyway.
Okay,
what
he
found
in
his
exploring
was
that
it
was
surprisingly
surprisingly
smooth
that
the
work
that
tim,
jacom
and
others
have
already
done
has
made
things
work
quite
well,
and
so
he's
continuing
to
propose
he's
also
created
a
series
of
epics
in
jenkins
jira.
So
here's
one
java,
17
phase
two
and
the
he's
got
a
series
of-
I
think
it's
five
phases
for
the
java
17
support
that
are
represented
here
in
jira
and
you
can
track
through
these
okay.
A
Here's
the
first
phase,
second
phase
third
phase
and
he's
been
moving
issues
into
those
as
as
as
he
detects
them,
so
we've
got
a
reasonable
way
of
managing.
What's
java
17
going
to
look
like,
we
don't
have
a
timeline,
that's
being
discussed,
but
we've
got
a
picture
that
lays
out.
Okay,
here
are
the
things
that
are
we're
discovering
about
java
17.
A
Did
that
answer
your
question
ben
yeah,
great,
so
jira
epics
used
to
track
the
work,
and
let
me
put
the
links
to
those
in
there
so
that
so
that
we've
got
those
it's
just
a
it's
a
really
for
me.
This
technique,
he's
used
of
doing
phased,
phased
epics
in
jira
has
been
really
helpful
to
for
me
to
see
what
where
we
are
and
how
things
are
going.