►
From YouTube: Jenkins Platform SIG Meeting, Nov 19, 2020
Description
The Jenkins Platform SIG has met to discuss the status of multi-platform Docker images, Windows Docker images for LTSC 2019, membership in the OpenJDK Quality Outreach program, future of Docker packaging for Stretch, and adoption of the new Plugin Installation Manager tool. Full agenda and meeting notes: https://docs.google.com/document/d/1bDfUdtjpwoX0HO2PRnfqns_TROBOK8tmP6SgVhubr2Y/edit#heading=h.r97hloffu9u4
A
A
A
Great
all
right
super,
so
what
we'll
do
is
we'll
review
the
open
action
items
oleg
had
had
suggested.
We
might
put
a
quality
outreach
program
topic
on.
I
would
hold
that,
if
he's
here
and
leave
it,
if
he's
not,
we
can
talk
briefly
about
it,
but
then
adopt
open
jdk
for
docker
on
debian
retirement
plan
for
stretch
is
the
topic.
C
A
A
A
A
B
A
B
A
A
E
E
E
A
E
E
A
Well-
and
it's
important
important
point
that
you
know
that
may
lobby
that
we
should
not
add,
we
should
not
obsolete,
install
bashplugins.sh
until
we're.
We
have
more
confidence
that
all
the
use
cases
are
covered
well
enough
with
plug-in
installation
manager.
We
may
make
plugin
installation
manager
the
preferred
choice,
but
better
that
it
we
use.
We
have
it
still
available
to
use,
install
plugins.sh
great.
B
B
A
A
E
A
C
C
The
wrapper
is
really
utilized
for
ci
cd
implementations.
It's
pretty
easy,
you
just
say
hey.
I
want
to
build
debian
images
and
it
will
handle
all
the
tagging.
All
the
you
know,
votes
tagging
scanning
the
docker
scan
the
repo
for
docker
files
and
doing
all
that,
for
you,
it's
pretty
simple
to
use.
I
have
documentation
in
the
ci
folder
that
kind
of
goes
over
each
script.
The
parameters
that
you
pass
in
and
a
couple
examples.
B
C
C
I
opted
more
for
just
clarifying
it's
debian
slim,
so
you
know
you
can
see
the
difference,
but
it's
easy
enough
just
to
go
in
there
and
add
in
slim.
It's
just
one.
If
statement
I
need
to
add
in
if
we
want
that
yeah,
the
the
only
other
thing
I
would
need
help
from
alex,
probably
on
the
parallelization.
C
I
did
not
touch
the
jenkins
file
as
I'm
not
really
that
verse
in
groovy.
That
much
so
I
would
need
some
help
kind
of
adding
the
parallelization
to
the
jenkins
file
and
pointing
to
the
right
scripts
to
call-
and
I
I
mention
these
two
points
in
the
the
pr
as
places
I
need
help
to
kind
of
finish
up.
The
pr.
A
B
C
A
C
Yes,
these
so
the
scripts,
you
can
run
images
and
tags,
the
publish
images
publish
tags
on
well,
they
need
to
be
run
on
arch
to
generate
the
s390
arm
or
power
images.
The
manifests
can
be
run
on
any
arch,
actually
constructing
the
manifest,
because
for
manifest
you're
just
pulling
down
all
the
images
they
don't
actually
need
to
be
ran
or
anything
like
that.
I
think
technically,
tagging
you
don't
need
to
run
on
a
different
arch
too,
but
yeah.
C
A
Okay,
but
but
that
is
currently
separate,
okay-
and
that's
a
good
one
for
this
for
gareth
to
just
report
for
us
on
how
his
progress
is
going
there,
I'm
not
sure
what
it
would
mean
yeah,
because
don't
I
do.
I
remember
correctly
that
the
windows
images
are
generated
from
powershell
scripts,
not
really
from
make
files.
B
C
E
C
Okay,
sweet.
The
one
thing
I
did
add
was
there
is
environment.
Variable
I
managed
on
this
pr
you
could
you
can
actually
override
changing
the
the
image
repository
you
guys
pushed
to.
So
if
you
ever
want
to
start
publishing
for
multiple
repositories
like
cue,
o
or
github's
docker
repository
that
is
possible
with
the
scripts.
A
A
E
E
A
C
E
We
had
quite
productive
discussions
with
opportunity,
k
jigsaw
team
at
that
moment
to
be
basically
able
to
support
java
10
and
java
11.,
but
we
haven't
been
really
active
with
regards
to
supporting
higher
java
versions,
and
this
topic
might
become
actual
when
the
new
java
lcs
is
released
so
far.
The
plan
is
it's
going
to
be
java,
17.,
so
half
a
year
from
now,
we
should
be
able
to
test
the
upcoming
lcs.
E
E
So
yeah
does
it
make
sense
to
support
java
17,
probably
yes,
but
it
means
that
we
would
be
supporting
three
lcs
baselines.
You
would
need
someone
to
actually
add
support
and
testing.
You
would
need
to
create
a
ci
cd
pipelines,
increase
cost
of
all
testing
across
the
agency
organization
and
if
it
happens
like
with
java
11,
when
we
have
less
than
two
percent
of
users
running
this
version,
I'm
not
sure.
What's
at
the
point.
A
E
E
So
there
is
a
reason
to
update,
for
example,
we
run
searching
say
on
java
11
and
if
you're
using
newer
versions,
we
would
have
even
better
garbage
collector.
We
would
have
even
better
diagnostics
tools,
so
in
principle
it
makes
sense
to
update,
especially
if
you
run
your
own
service
and
when
the
cost
of
operating
this
service
is
something
important
to
you.
But
if
you
ship
on
premise
version
so
that
others
run
it
basically,
others
yeah.
E
A
A
And-
and
that's
a
that's
a
good
point,
for
example:
we've
got.
We
can't
fundamentally
support
the
adopt
open,
jdk
jdk
8
on
system
390z,
because
it
doesn't
use
just
in
time
compilation
but
java
11
does
use
it
and,
and
is
great
it's
so
that
you've
got
a
good
point,
that
there
is
a
there's,
a
motivation
on
s390z
and
other
places
that
java
11
just
behaves.
B
A
Good
all
right
anything
else
I
like,
should
we
should
we
call
for
a
decision
here,
call
for
it,
because
I
think
I
think
we've
got
the
right
people
on
the
call
to
decide
if
we
should,
if
we
should
continue
being
part
of
the
quality
outreach
program
and
just
then
give
them
the
answer
accordingly,
would
would
that
be
okay
or
do
we
need
the
governance
board
to
to
get
involved
in
that?
I
don't
think
the
governance
board
was
involved
in
the
initial
joining
of
it.
E
E
The
problem
is
whether
somebody
wants
to
contribute.
Even
when
we
were
doing
java
10
java
11
support,
we
organized
a
hack
first,
we
also
used
other
events.
We
had
more
than
30
contributors
in
total,
but
at
the
same
time
a
significant
part
of
changes
came
from
cloudbees
at
that
point
and
yeah,
I'm
not
sure
whether
there
would
be
investment
in
java
17
support
at
the
moment,
I'm
not
a
product
management
manager.
I
cannot
say
but
yeah.
A
E
B
A
So,
plus
one
from
from
mark
to
step
away
and
and
to,
I
should
state
it
differently
to
officially
state
that
we
are
dropping,
because
I
don't
want.
I
don't
want
the
job
equality
outreach
people
to
think
that
we're
we're
somehow
going
to
step
up
and
do
more
or
but
rather
let's
just
let's
step
out
so
alex.
I
took
that
from
plus
one
from
you
as
well
oleg
your
your
feeling.
A
E
A
B
C
A
A
So
any
objections
to
to
that,
so
we
just
we
allow
the
stretch
image
to
retire
as
its
current
configuration
used
in
open
jdk
and
it's
currently
using
open,
jdk
8u
242
currently,
and
it
will
just
stay
there
until
we
obsolete
it
remains
until
stretch
is
obsolete
or
they
upgrade
jdk.
They
do
the
upgrade
themselves.
A
A
A
Debian
alex
any
any
concerns
there
or
places
where
ooh.
This
is
this.
This
is
a
bad
plan,
something
like
that.
No
sounds
good
to
me.
Okay,
all
right
so
retire,
and
so
I
just
to
be
sure
I
think
what
that
means
is
we
will.
The
the
label
latest
will
switch
at
some
point
in
the
future
from
stretch
based
to
buster.
A
E
E
A
A
A
A
A
For
each
image,
what
I've
seen
is
that
I
don't
monitor
the
centos
images,
for
instance,
because
they
just
aren't
relevant
to
my
use
cases,
but
there
are
probably
people
who
do,
and
so
we
would
like.
I
think
we
need
the
concept
of
a
maintainer
for
each
image
and
I
believe
that
the
github
code
owners
concept
may
help
us
there.
I'm
open
to
the
comments,
though,
is
that.
E
C
Yeah,
so
the
like,
I
mentioned
before
the
pr
has
been
submitted.
The
whole
point
of
this
is
to
add
a
couple:
more
verbose
tags.
The
idea
is,
you
publish
the
super
verbose
tags
which
include
the
jdk
jvm
os
name,
os
version
jenkins
version
yeah.
I
think
that's.
Actually
it's
and
you
publish
those
and
then
you
re-tag,
those
with
the
the
tags
you
guys
are
all
used
to,
like
slim,
debian,
latest
lts,
and
basically
that
way.
C
C
A
E
A
Great
okay
well-
and
I
like
that-
that's
that
has
we
can.
We
could
certainly
use
the
controller
naming
pattern
if
someone
says
hey,
I
need
this
support
for
this
type
of
agent
great,
we
can
use
the
we
can
at
least
use
the
naming
pattern
that
jim's
created
if
we
needed
to
be
more
verbose
in
the
agent.
C
Okay,
because
the
if
and
when
you
guys
did
want
to
do
the
verbose
naming
the
scripts
are
written
in
a
way
where
it
scans
those
folders.
So
as
long
as
that,
like
folder
structure
is
the
same
on
the
controller
or
on
the
agent's
repos,
the
scripts
should
be
pretty
easy,
actually
just
to
carry
over
a
slight
modification,
not
a
whole
rewrite
or.
A
F
A
A
B
F
A
A
F
F
A
B
The
windows
builds
like
we
have
for
the
linux
builds,
but
I
just
haven't
had
the
time
to
look
at
it:
okay,
great
all
right,
because
we
actually
do
build
we're,
building
eight
images
and
testing
them,
so
it
I
think
it's
eight
that
may
be
wrong
on
that.
So
it
does
take
some
time.
So
if
we
could
parallelize
that
it
would
be
good.