►
From YouTube: 2021 01 29 Platform SIG
Description
Jenkins Platform SIG January 29, 2021 with topics including CentOS with AdoptOpenJDK, multiarch support for Docker images, Jenkins Contributor Summit, and coordinating proposed Docker image changes.
A
A
So
here's
what
I've
got
as
topics
for
today
open
action
items
jenkins,
mass,
the
docker
master
branch,
docker
changes
that
I
think
is
probably
going
to
be
likely
most
of
the
meeting
and
jim.
It's
wonderful
that
you're
here
for
this
conversation,
because
your
key
participant
there,
a
jet
platform
proposal
that
we
may
do
just
briefly
and
then
contributor
summit
discussion-
are
there
other
agenda
items
that
need
to
be
added
to
this
list
before
we
actually
start
through
the
agenda.
A
A
The
draft
is
there
I'd
like
to
not
spend
a
lot
of
time
here
today
on
it,
because
I
think
we've
got
more
practical
things
to
discuss
in
terms
of
proposals
that
are
actively
in
in
progress,
but
it
is,
it
is
available
there
and-
and
we
can
certainly
certainly
look
at
it
if,
if
we,
if
there
are
questions
about
what
it
says,
alex
centos
for
adopt
open,
jdk,
you've
submitted
the
pr
anything
you
want
to
share
there.
Further
on
that.
B
A
A
Anyone
else
with
objections
on
merging
that
centos
use,
adopt
open,
jdk
pr
that
will
give
us
the
benefit
that
now,
alpine
debian
and
centos
will
all
be
using
adopt
over
jdk
for
their
jdk
great
all
right.
So
then,
I
had
an
action
item
on
the
plug-in
installation
manager,
and
I,
like
that,
alex
you'd
suggest
we
consider
a
shim
the
more
I
looked
at
that
the
more
interested
I
am
in
doing
that
to
simplify.
A
Great
excellent,
thank
you
so
so
the
installplugins.sh
script
would
then
continue
to
exist,
but
would
actually
call
the
plugin
installation
manager
java
code,
rather
than
doing
it
all
from
the
shell,
excellent.
Okay
and
jim.
We
had
an
item
for
you
on
parallelization
and
multi-arc
ci.
Is
there
anything
you
wanted
to
report
there.
D
D
A
Sure,
gareth,
gareth
and
cara,
I
believe,
are
also
at
least
maybe
interested
in
that
area.
So
jim
don't
be
shy.
Jim
crowley,
gareth
for
your
info
is
part
of
ibm.
Gareth
is
part
of
cloudy's,
cara
is
part
of
cloudbees,
and
so,
and
so
we're
we're
delighted
to
all
be
contributing
to
open
source
is
a
wonderful
thing.
B
A
A
All
right
next
topic
was
proposed.
Docker
changes,
so
this
one
is,
as
I
was
looking
at,
the
things
that
are
pending
in
in
various
poll
requests.
It
feels
like
we've
got
several
very
interesting
changes
coming
in
in
our
docker
infrastructure
in
our
docker
environment,
so
alex
yours
adopt
open,
jdk
change.
A
I
proposed
an
upgrade
from
stretch
to
buster
jim's
got
the
proposal
for
multi-arch
and
then
coming.
We've
got
this
alex
the
the
one.
You
noted
that
you're
working
on
to
replace
the
contents
of
install
plugins.sh
with
a
call
to
plugin
install
manager,
those
are
the
controller
side
and
then
cara
has
a
pr
open
for
non-root
user
on
the
agents
and
for
docker
build
improvements.
A
A
E
A
My
thought
was
that
there
are
probably
downstream
users
that
are
that
were
running
as
running
the
image,
and
today
it's
running
as
rude
and
in
the
future
it
won't
run
as
rude
right.
The
idea
is,
stop
running
is
rude
and
that's
going
they're
going
to
see
that
as
a
compatibility
change
and
we're
going
to
say
yes,
it's
intentional,
we
we
really
mean
it.
You
shouldn't
run
as
root.
E
So
how
we're
handling
that?
I
believe
this
handles
it
from
a
technical
perspective
is
that
we
are
leaving
those
images
up,
so
these
will
be
published
separately,
so
this
will
be
an
entirely
different
new
set.
So
I
hope,
but
yes,
we
will
do
messaging
around.
Why
we're
making
this
change.
Why
we're
making
these
available,
and
why
you?
You
know
why
we
advise
you
not
to
run
this
room.
A
A
E
A
E
A
In
the
past,
what
we
did
was
we
would,
we
would
announce
a
we
would
announce
with
a
blog
post,
so
when
we,
for
instance,
switched
from
alpine
3.9
to
0.3.12,
we
just
did
a
blog
post
and
then
made
the
change
and,
and
that
one
was
actually
surprisingly
quiet.
So
I
was
assuming
I'll
do
a
blog
post
on
this
oops
on
the
stretch
to
buster
change
there
on
this
change
from
stretch
to
buster
I'll
do
a
blog
post.
I
would
do
a
blog
post
on
that
saying:
hey
we're
doing
this!
A
This
change,
because
the
user
will
see
yesterday
they're
running
jenkins,
slash
jenkins
colon
latest,
and
it
was
actually
building
using
debian
nine
tomorrow
they
run
jenkins
jenkins,
calling
latest
and
it's
suddenly
running,
debian
10
and
they'll.
Be
oh,
but
my
scripts
are
different
or
whatever
happens
inside
them
has
changed
for
them.
D
Mark,
I
think
one
of
the
I
think
I
think
it
was
in
my
pr-
and
I
know
we
had
an
issue.
Excuse
me
talking
about
it,
but
the
more
verbose
tags
should
help
or
alleviate
some
of
these
pressure
people.
You
know
having
conflicts
like
if
we
have
a
verbose
tag
where
it's
you
know
latest,
then
we
had
a
debian
tag
and
then
we
had
w9
or
debbie's
stretch
or
whatever
you
know
dash
stretch
and
then
a
debian
dash
buster.
As
we,
you
know,
people
kind
of
want.
D
That
could
avoid
some
confusion
of
you
know:
hey
I'm
pulling
down
just
latest
which,
as
everyone
knows,
if
you
just
pull
down
the
latest
image
on
any
repository,
you're
asking
for
you
know
some
sort
of
unstability
and
also
for
some
trouble,
like
you
don't
know,
if
they're
ever
going
to
change
latest
to
be
a
different
distro
or
whatever
that's
why
more
specific
tags
allow
for
that?
More
control
for
our
users.
B
D
Yeah,
I
think
the
deprecation
is
still
very
important,
but
hopefully
if
they
really
do
care
about
the
os
and
specific
version
of
that
os,
they
can
have
a
more
specific
image
to
hold
on
to
for
a
little
bit
until
right.
You
know,
deprecation
is
fully
gone
and
we
stop
supporting
it
and
stop
publishing
all
together
right.
A
Okay,
so
so
jim,
it
sounds
like
what
that
does
that
lobby
that
we've
intentionally
held
off
on
pr
1070,
waiting
to
get
a
formal
announcement
and
etc
seems
like
we
would
benefit
if
we
also
had
yours
in
before,
so
that
we
could
announce
those
two
things
together,
I
don't
think
we
need
to
combine
it
with
the
agent
change
cara.
It
sounds
like
you've
got
the
compatibility
thing
solved
there,
but
for
for
the
controller
side,
does
that
make
sense
to
you,
jim
that
and
is
the
is
1034
the
the
pr
that
adds
the
more
verbose
tags.
D
Yeah
1034
does
alex
actually
started,
producing
more
verbose
tags,
pretty
similar
to
the
exact
same
style
that
I
was
suggesting
for
windows
images,
I'm
pretty
sure.
So
again,
I
think
in
that
pr
I
made
a
comment
of
like
a
demonstration
of
like
what
the
verbose
tags
are
and
how
all
the
tags
that
you
guys
still
have,
or
still
support
right
now
are
still
there,
but
the
verbose
tags
add
more
clarity
for
users
who
want
a
specific
version.
A
B
D
A
A
Great
excellent,
all
right,
I
would
also
like
to
propose
that
we
close
several
prs
in
or
any
other
discussion
on
that
question
of
coordinated
announcement.
Do
we
need
it
alex?
Do
we
need
to
include
in
the
coordinated
announcement
installplugins.sh
as
part
of
that
or
is
it
you
have
viewed
as
separate.
A
Right,
okay,
so
then
the
last
the
last
topic
on
that
that
general
theme
for
me
was
there
are
several
pr's
in
the
in
the
controller
repository
that
given
this
path,
I
think
we
can
safely
close,
there's
one
offering
jdk
13
another
one.
That's
proposing
amazon
linux
and
I
don't
intend
to
maintain
either
of
those
and
jdk
13
is
already
unmaintained
by
providers.
So
any
objections,
if
I
were
to
go
in
and
actively
close,
several
of
those
with
the
explanation
that
hey
we're
going
forward
with
this.
A
A
A
So
there
I've
sent
a
proposal
out
to
the
to
the
jenkins
developer
mailing
list
for
this
concept
of
a
contributor
summit
in
february
23-25.
So
about
a
month
from
now.
The
idea
is
we
use
this
as
an
annual
event.
We've
done
it
before
and
use
it
as
an
annual
event
to
set
the
plan
for
the
jenkins
project
and
where
we're
going
and
to
coordinate
with
each
other.
One
of
the
topics.
A
A
So
the
the
event
is
actually
a
three-day
exercise
day
one.
We
start
with
a
90-minute.
Everyone
welcome
together
and
then
we
have
separate
tracks
on
various
topics,
and
I
proposed
a
I
don't
know
if
I've
put
it
in
yet
so
I'll
propose
a
platform
track.
Something
like
this
one
that
focuses
on
what
the
platform
sig
does
we'll
schedule
sessions
to
meet
together
as
a
as
people
interested
in
platform
and
bring
proposals
ready
for
the
concluding
meeting
on
the
last
day
of
the
of
the
summit.
B
A
A
E
A
A
A
Okay
and
the
last
one
I'm
actually
prone
to
just
drop
the
topic
for
now,
because
I
have
not
done
any
further
edits
to
that
since
initially
proposing
it.
It's
there,
I'm
happy
to
discuss
it
here.
If
you'd
like
jim,
I
suspect,
you're,
probably
you
and
alex,
are
two
crucial
ones
to
see
hey.
Does
this
make
sense
in
the
way
you
think
about
things?
A
The
idea
here
is:
let's
propose
to
have
the
concept
of
a
maintainer
and
images
that
don't
have
maintainers
go
into
the
adopt
this
image
program
somewhat,
like
the
jenkins
adopt
this
plug-in
program,
so
the
idea
being,
if
we
don't
have
an
owner
for
something
we
probably
shouldn't,
keep
attempting
to
update
it
at
the
moment
as
an
example,
I
feel
risky
with
centos
7,
because
I
don't
I
don't
work
on
it.
Alex
thankfully,
submitted
a
pull
request.