►
From YouTube: 2020 10 08 Platform SIG
Description
Jenkins platform special interest group meeting Oct 8, 2020 with topics including Docker platforms, AdoptOpenJDK, IBM s390x, and Windows Server 1909
A
A
The
idea
is
I've
got
an
outline
later
that
I'll
outline
for
you,
but
we've
got
to
consider.
Debian
9
has
already
ended.
Its
typical
support.
Lifecycle
is
now
into
long-term
support
and
the
debian
project
when
they
release
bullseye
debbie.
What
is
debian
11
will
stop
supporting
w9
so
and
that'll
be
in
sometime
in
2021.
A
So,
given
that
operating
system
vendor
support
is
is
ending
on
this
thing.
The
other
example
is
that
operating
vendor
supports
ended
long
ago
on
alpine
3.9,
and
oleg
nanashev
did
a
a
quick
upgrade
for
us
to
3.12,
but
really
our
process
and
our
our
rules
for
support
should
have
caused
us
to
do
that
automatically
anyway
and
did
not
so
so.
That's
that's
those
two
things
I'll
use
as
test
cases
now
test
case
additions,
s390x
and
arm
64
will
be
on
the
the
the
other
examples
right.
A
So
s,
s398x
and
arm
64,
as
example,
additions
because
we've
now
got
the
the
graviton
instances
available
for
us
from
ci.jenkins.io
for
arm64
and
we've
had
the
s390x
available
for
quite
a
while
alex
had
the
action
to
investigate
options
for
centos
and
adopt
open
jdk.
Now
jim
you've
been
a
good
voice
for
us
to
adopt
open,
jdk
anything
you
wanted
to
share
there.
B
Yeah
we
do
have
centos
support
it's
in
the
unofficial
images.
One
of
the
major
things
that
I've
been
working
with
adopts
since
I
started
working
with
you
guys
over
a
year
ago
or
almost
a
year
ago,
is
pushing
the
unofficial
images
too
official,
so
that
you
know
it's
a
little
more.
I
know
you
guys
graciously
started
utilizing
some
of
the
unofficial
images,
because
really
not
that
much
difference,
but
we
have
I
I
worked
with
the
testing
team.
B
A
All
right
so
already
provide
s390x,
so
that
that's
good.
That
gives
me
hope
that
I
can
put
one
of
one
of
the
noise
sources
in
our
platform
plan.
Is
we
have
some
images
based
on
open,
jdk
and
others
based
on
adopt
open
jdk,
and
so
this
that
sounds
like
your
work
with
adopt,
will
allow
us
to
consider
making
everything
based
on
adopt
so
that
we
can
delegate
the
worrying
about
operating
system
care
to
them.
Excellent
yeah.
B
A
A
Of
plugins
it's
in
preview,
and
so
it's
available
in
in
all
our
docker
images
for
core
for
jenkins
core
and
thus
far,
I've
pointed
several
people
to
it
and
said:
look
you've
reported
this
problem.
The
solution
is
to
use
plugin
installation
manager
instead
of
complaining
that
installplugins.sh
does
not
resolve.
A
B
Yeah
one
of
my
action
items
was
in
that
pr.
I
I
submitted
a
while
back
that
got
accepted
about
the
parallelization
and
the
the
rearranging
of
the
ci
build
tools
for
the
multi-arch
images
in
that
pipeline.
We,
you
guys
are
using
majority
open,
jdk
images.
Now
it
seems
like
the
shift
and
correctly
moving
wrong
is
now
more
majority
of
adopt
open,
jdk
images
and
inside
that
script
I
think
we're
still
calling
open
jdk.
B
So
I
need
to
go
through
and
prune
the
open,
jdk
references
and
make
slight
modifications
and
the
the
the
core
of
the
scripts.
There
just
needs
to
point
to
the
different
base,
images
and
stuff
like
that.
It
should
be
a
minor
tweak
for
that
excellent.
You
know
also,
I
misspoke
on
s
on
center
west
support
adopt
open
jdk
does
provide
pretty
much
all
the
architectures,
but
for
any
os,
but
for
centos,
especially
it's
a
kind
of
pain
in
the
butt
centos
themselves.
B
Yes,
yeah
yep,
red
hat
red
red
hat
runs
fine
s390
and
power.
There
is
a
ubi
image,
a
universal
base,
image,
which
is
what
red
hat
puts
pushes
out.
It's
not
called
red
hat
os
or
whatever
it's
not
rel,
but
it's
ubi,
which
is
based
off
of
rail.
It
just
stripped
out
some
of
the
more
like
proprietary
stuff,
but
ubi
works
on
pretty
much
all
the
architectures.
A
B
To
use
ubi
right,
no,
no,
you
don't
need
any
license.
You
don't
need
a
subscription
manager.
You
don't
need
anything
like
that.
As
long
as
I
everything
I've
read
and
everything
I've
done
with
ubi,
you
don't
need
a
subscription
manager
like
you
would
need
they
give
you
on
rel
or
something
like
that
right.
Okay,
the
ubi's
is
available
for
every
architecture.
You
guys
support
right
now.
Arm
64..
I
don't
think
it
has
arm
32
support,
but
I
I
know
it
has
power
and
s390
in
amd
and
arm
64..
A
A
A
A
A
A
Okay,
so
next
is
retirement
plan
and
schedule
for
retiring
debian
9..
This
is
we've
got
to
find
a
way
to
notify
people
that
debian
9
support
is
going
away,
or
it
would
be
nice.
I
should
say
it
differently.
Alpine
certainly
didn't
find
any
way
to
tell
us.
3.9
was
no
longer
supported,
they
just
said
it
on
their
web
pages.
We
could
do
the
same,
but
there
is.
A
And
yeah
here
we
go
so
it's
part
of
the
part
of
the
platform
plan
is
includes
research
on
other
examples
like
alpine,
like
debian,
like
adopt
open
jdk,
because
certainly
they've
got
the
same
same
challenge.
Right,
debian
9
was
supported
by
them
and
if
I
remember
correctly
now,
they've
they've
switched
everything
to
buster
and
beyond.
So.
B
Any
questions
mark
at
one
time
I
know
alex,
I
think,
was
alex.
It
was
talking
to
glitter.
Isn't
there
like
some
sort
of
tool
that
scans
docker
images
looking
for
like
vulnerabilities
and
stuff
like
that,
because
you
know
what
you
were
mentioning
was
that
the
way
we
found
out
or
the
way
you
guys
found
out
for
alpine
being
retired
was
oh
hey?
You
went
on
the
website
or
someone
went
on
the
website
and
saw
it
or
someone
raided
an
issue.
Is
there
not
a
way
to
be
preemptive
in
terms
of
that?
B
A
A
Schnick
encore
and
there
are
that
it's
it's
an
entire
market
space
yeah,
and
so
there
are
many
different
competitors
in
that
space.
We
just
don't
have
any
of
them
enabled.
So
it's
a
good
point
and
that's
a
that
would
be
a
nice
addition
to
our
ci
processes
to
scan
our
docker
images
for
vulnerabilities
from
through
one
of
these
one
of
these.
A
B
A
C
B
D
A
Okay,
that's
a
good
question
and
I
haven't
seen
any
discussion
about
switching
the
default
image
from
jdk
to
jdk
11,
but
I
think
it's
a
worthwhile
topic
and
it's
that
again
fits
with
part
of
the
platform
support
plan.
It's
a
good
thing
for
us
to
get
into
those
conversations
so
so
that
we
shift
should
we
shift
people
the
day
will
come
when
jdk
8
will
support
will
end
from
from
various
people.
It
may
be
many
years
away,
but
it
will
end
and
we'll
need
to
transition
people.
B
B
Yeah,
like
you
know,
I
mean
like
you-
could
still
use
eight
as
the
default.
You
would
just
need
to
make
sure
if
you're,
building,
4s
or
90
to
instead
of
using
hotspot
as
the
base
image,
make
sure
you
do
the
open,
j9
variant,
but
that's
it,
but
with
11
you
wouldn't
need
to
care.
You
just
build
all
hotspot.
A
B
A
The
reason
I
ask
is
open:
j9
is
a
is
an
open
topic
for
me
as
part
of
the
platform
support
where
I'm
thinking,
one
way
to
reduce
our
our
platform
matrix
the
depth
and
breadth
of
the
thing
is:
should
we
should
we
not
do
open
j9?
But
if
we
said
oh
we're
not
doing
open
j9,
that
means
we
would
say
we
can't
do
s390
on
jdk8
and
that
that
that
could
be
a
blocker.
You
say
no.
We've
got
to
have
s390
at
least
open
j9
for
that,
in
order
to
do
jdk
on
s390x.
B
B
A
A
A
Access
from
ci.jenkins.io
is
unreliable
and
we
don't
know
why
and-
and
I
I'm
just
completely
perplexed
by
it-
is
it
a
networking
issue
from
aws
that
my
home,
my
home,
where
my
machines
are
don't
have
we
need
to
investigate
further
and
alex,
has
has
started
the
investigators
started
and
the
experiment
to
see
if
he
can
understand.
What's
going
on,
my
initial
experiments
failed
and
it
made.
B
A
On
azure,
okay-
and
I
don't
right
now-
I
don't
have
personally
the
time
to
do
the
investigation,
so
I'm
not
sure
there's
any
gain
for
you.
Invoking
raphael
right
now,
but
alex
alex
may
and
mike
might
appreciate
any
any
insights
that
insights
they
have
on
how
to
diagnose
where's
the
problem
yeah,
I'm
not
used
to
diagnosing
cloud
vendor
to
cloud
vendor
connection
yeah.
Is
it
just
connection
dropouts.
A
Connection
is
established,
it
runs
it.
It
continues
to
operate,
but
the
for
instance,
the
remoting
jar
does
not
seem
to
finish
loading
or
finish
copying
from
from
the
from
from
the
controller
to
the
agent,
and
it's
not
clear
why
we
can
see
that
there's
there's
in
the
log
file
there's
clearly
a
connection
and
yet-
and
it
says
copying
the
remoting
jar,
but
then
nothing
further.
A
B
A
Yeah,
in
fact,
I
can
even
here
we'll
just
let's
go,
live
and
I'll
show
you,
because
I
suspect
the
agent
is
currently
disconnected
and
we
can
see
the
log
and
so
that
will
that
will
helps
us
visualize
it
it's
here
and
the
the
log
is
completely
perplexing
because
it's
clearly
doing
real
ssh
work
on
the
remote
side,
and
this
is
hey.
This
is
the
correct
machine
type.
A
Yes,
we
expected
it
to
be
a
red
hat
linux
and
it
is,
it's
got
a
reasonable
path,
all
those
things,
but
then
it
hits
this
point
and
seems
to
progress
no
further,
and
I
don't
I
don't
understand
why
and
haven't
had
the
capacity
to
do
the
investigation.
But
that's
that's
the
kind
of
thing
that's
happening.
B
Is
that
is
that
link
publicly
accessible
or
no?
Is
that
just
he
is
yes,
I
think
so,
but
yeah.
So
let
me
I'll
just
put
it
into
the
notes.
Yeah!
Thank
you.
No,
I
appreciate
it
yeah
I'll
get
with
alex
on
that
then
and
tried
to
figure
out.
Maybe
it's
some
sort
of
stupid
firewall
or
something
like
that.
Did
it
ever
work.
A
Or
it
was
just
it,
it
has
worked
on
occasion
and
alex
saw
it
work,
and
then
it
started
failing
again,
so
it's
it's
intermittent,
which
is
of
course
the
worst
of
all
possible.
Yes,
exactly
and-
and
it
still
works
great
for
me,
my
my
agent
is
still
perfectly
well
connected
and
let's
see
if
I
can
show
that
the
agent
from
my
machine
is
there
and
runs
great.
So
here
we
are,
it's
called
this
one.
A
A
Yeah
great,
thank
you
all
right.
Next
topic:
windows,
server,
1909
agent,
support
so
gareth.
This
is
the
thank
you
very
much
deep
and
sincere
thanks
to
gareth.
What
we've
got
is
november
of
2020
will
be
the
last
windows
server
1809
security
release.
So
that's
the
docker
image
our
docker
images
are
based
on
1809..
A
Our
docker
agent
images
are
based
on
1809
windows,
docker
agent,
docker
agent
images
1809,
so
we're
at
end
of
life.
For
for
that
that
operating
system
version
we
need
to
get
running
on,
or
building
versions
based
on
1909
and
alex
and
gareth
are
going
to
be.
Investigating
alex
had
done
some
initial
investigating
initial
prototyping
to
see
if
we
could
already
build
1909
and
as
far
as
I
can
tell
he's
confirmed
that
we
need
to
change
the
base
windows
operating
system
we're
using
before
we
can
build
the
windows,
1909
image,
gareth.
C
A
A
Super
and
thank
you
for
doing
it
thanks
in
advance
for
doing
that.
That's
a
that's
a
sort
of
a
dark
corner
for
me,
where
alex
really
knows
very
well
how
the
windows,
agent
windows
images
are
built
and
I
feel
like
I'm
just
barely
learning,
okay,
more
details
on
on
the
docker
platform.
Actually,
maybe
what
we
do
is,
let's
take
oracle
cloud
as
a
topic
here
and
I'll
give
a
free
status
report,
then
we'll
use
some
more
time
on
the
platform
support
proposal.
A
And
other
hardware
related
things:
they
apparently
have
a
virtual
machine
style,
more
of
a
virtual
machine,
centered
focus
and,
and
that
could
help
us
with
getting
extra
compute
capacity.
If
we
need
it
now,
I
don't
have
anything
more
than
that
other
than
to
say
that
yes,
we'll
continue,
and
just
like
jim
our
gratitude
to
ibm
for
being
a
cloud
provider
for
for
equipment.
We
look
to
other
cloud
providers
to
help
thanks
very
much
any
questions
on
oracle
cloud.
A
Okay,
next
topic,
then
docker
platform
support.
So
here's
here's
my
rough
idea
on
how
I
want
to
frame
the
initial
document,
starting
with
what
we
have
today
in
terms
of
a
tabular
survey
of
the
image
types
we
support
so
core
and
ssh
agent,
the
jnlp
agent
of
various
other
images
that
the
project
supports,
which
jdk
sources
we
support.
A
B
B
A
A
A
Good
any
other
things
in
the.
How
do
we
highlight
what
we
have
today?
Did
I
miss
something
else
looks
good
okay.
Then
I
thought
the
next
step
is
talk
about
what
we
want.
Oh,
oh,
no.
I
had
one
more,
which
was
issues
with
what
we
have
and
the
reason
to
put
that
there
is
highlight
debian,
9
obsolescence,.
B
B
Are
they
producing?
I
don't
think
the
at
least
the
last
time
I
checked.
I
think
there
was
a
proposal
from
the
official
docker
image
publisher,
the
you
know
the
group
that
published
the
official
images.
I
think
they
stopped
supporting
openjdk.
I
don't
think
they're
publishing
new
new
builds.
Besides
x86,
I
think
it's
just
they're
pushing
out
open
jdk,
x86,
new
new
images,
but
s390
power
arm
and
all
that
stuff
they
officially
stopped.
A
Excellent
good
good,
good
examples
of
issues
to
highlight,
saying:
hey
look!
This
is
what
I
like
that,
because
for
me,
what
we
show
is
hey
an
image
or
a
series
of
tables
which
illustrate
just
how
complicated
the
things
are
that
we
currently
have
because
of
all
the
different
mixes
and
all
right.
Here's
the
the
issues
that
come
from
that
complication
and
then
switch
into
a
okay.
Here's
what
we
want.
We
know
we've
got
to
do
intel.
A
B
B
A
A
So
so
it's
again
a
place
where
we're
being
unclear
and
this
this
platform
support
proposal
can
highlight.
Hey
here
are
the
things
where
we're
absolutely
unclear
on
what
what
this
thing
is,
because
it's
not
just
slim,
it's
debian
buster,
that
happens
to
be
the
lightweight
the
the
small
version
of
it.
B
Also,
you
guys
not,
I
think
I
asked
this
in
the
glitter
chat.
It
looks
like
adopt
and
pretty
much
everyone
else
is
starting
to
drop
support
for
amd.
Oh
sorry,
arm
32-bit
processors
like
arm
v6,
or
something
like
that.
I
figured
which
one
v,
whatever
you
guys,
aren't
planning
to
do,
arm,
32
or
whatever
its
name.
A
Okay,
as
far
well
so
one
of
it's
a
good
good
question,
and
one
of
my
arguments
why
I
think
we
should
not
consider
adding
32-bit
arm
is
in
order
to
support
a
processor.
We
need
to
have
access
to
that
processor,
from
ci.jenkins.io
and
from
trustedci
and
and
you
can't
get
cloud
hosted,
32-bit
arm
yeah
at
least
not.