►
From YouTube: 2020 12 04 Platform SIG
Description
JEP, Windows, Docker, Bugs, and PRs
A
All
right
welcome
everyone.
This
is
the
jenkins
platform
special
interest
group.
It's
the
4th
of
december
thanks
for
joining
us.
So
here's
what
I've
got
as
agenda
topics,
open
action
items.
A
A
Okay,
then,
let's
go
through
action
items.
So,
yes,
I
still
have
the
action
item.
Yes,
I
think
it's
shaping
now
started
the
process
this
morning.
A
Open
j9,
I
need
some
maintainer
etc.
So
I'll
include
those
in
that
jet
and
I
hope
to
get
it
done
quickly.
I'll
send
everyone.
What
I'll
do
is
send
everyone
a
draft
privately
likely
so
that
we
or
would
you
alex,
maybe
you
and
gareth
can
give
me
insight.
Should
I
submit
it
as
a
pull
request
in
draft
to
the
to
the
jab
repository
and
we
just
do
it
in
the
in
the
jeff
repository
or
the
user.
Worry
that
hey.
This
is
going
to
be
so
controversial
that
we
should
review
it
as
a
group.
First.
B
Repository
and
then
like
very
few
people
like
monitor
that
repository,
I
think
so
until
you
send
out
the
jet
on
like
the
dev
mailing
list
or
something
like
that,
I
don't
think
it's
gonna
have
a
lot
of
like
a
lot
of
people
are
gonna,
have
an
issue
with
it.
A
A
B
I
I
have
a.
I
should
have
a
pr
soon
that
uses
the
yam
repository
from
adopt
adoptium,
so
I'll,
create
the
pr,
and
then
we
can
have
discussion
on
that
pr
just
to
see
if
people
really
care
or
not.
A
B
Well,
I
know
that
there
is
recently
some
discussion
that
the
centos
images
are
the
most
secure.
They
have
the
they
have
zero
cves
when
scanned
in
terms
of
the
image.
So
I
don't
know
if
that's
going
to
cause
more
people
to
start
using
them
or
not,
I'm
not
sure,
but
it's
it's
possible
that
that
that
more
people
might
use
them.
Since
they
have.
A
A
A
B
I
don't
know
I
mean
the
other
thing
we
could
do
is
create
a
shim
it
like
replace
the
contents
of
install
plugins.sh
and
shim
it
to
the
plugin
installation
manager,
and
then
people
will
be
using
plug-in
simulation
manager
just
without
knowing
it
there.
There
are
some
differences
between
arguments
between
install
plugins.sh
and
the
plug-in
the
cli
tool,
but
I
think
it
could
be
used
as
a
there
could
be
a
shim
implemented
instead
of
doing
any
sort
of
upkeep
on
that
script
and
just
replace
it
with
the
shim.
A
A
B
Yeah,
so
that's
just
one
option:
I
don't
know
if
it's
we
have
a
separate
script
right
now,
the
that
is
used
as
a
wrapper
around
the
tool
it
just.
It
just
passes
the
options
directly
though,
so
it's
it's
slightly
different,
so
this
would
be.
I
don't,
and
I
I
don't
know
if
we
want
to
put
the
effort
into
doing
anything
with
install
plugins.sh
instead
of
just
saying,
hey
move
over.
So
those
are
just
some
options.
B
C
B
C
B
Sorry
there
are
some
behavior
between
the
cli
tool
and
the
script,
but
I
think
that
some
effort
has
been
put
in
to
reduce
that
so
we'd
have
to
see
if
it
was,
and
that's
why
I
was
saying:
do
we
really
want
to
put
the
effort
in
there
to
have
some
sort
of
translation
layer,
implement
a
translation
layer
and
test
it
and
stuff
like
that,
so
that
that's
kind
of
the
trade-off?
I
would
think.
A
A
Okay,
anything
else
on
that
plug-in
installation
manager
and
install
plugins.sh
topic,
no
okay
great.
So
we
had
one
topic
on
jim
submitting
refinements
for
parallelization
alex.
I'm
not
aware.
I
haven't
been
following
his
his
work
there
anything
you
want
to
report
there
or
gareth
anything.
You've
got.
B
I
started
looking
at
the
pr
I
I
need
to
the
the
it
looks
pretty
good
I'll
say
that
the
the
only
question
I
have
is
how
it
fits
in
with
the
jenkins
file,
because
that's
kind
of
important
how
we
actually
invoke
it.
So
I
need
that's
kind
of
the
part
that
jim
says
he
doesn't
have
a
lot
of
experience
with,
and
so
so
I
need
that's
kind
of
what
he
wanted
me
to
look
at.
So
I
that's
kind
of
what
I'm
going
to
be
looking
at
to
see
you
know,
is
it
easy?
B
B
Yeah
I
was
concerned
about
the
declarative,
just
because
we
are
introducing
more
of
this
parallel
stuff
that
may
need
to
be
scripted,
but
we
can
definitely
look
at
that
too.
A
B
Right,
okay-
and
I
have
a
pr
that
that
adds
those
in
the
the
multi-arc
stuff,
but
it
would
need
to
be
reworked
once
jim's
stuff
is
integrated,
okay
got
it
and
we
need
to
have
a
stable
power
pc
agent.
A
A
A
All
right,
simplified
labeling
of
docker
images.
I
proposed
we'd
put
that
one
at
the
bottom
since
jim's,
not
here
we'll.
Let
him
talk
to
it
when
he
gets
here,
if
he's
here
and
if
he
doesn't
make
it
we'll
leave
it
off.
The
topics.
Topic
was
docker
images
for
ltsc
2019.
gareth.
You
want
to
give
us
an
overview
there.
C
I
mean
no
update
really
on
that.
We
were
holding
off
merging
the
pr
until
after
the
lts
had
gone
out,
which
so
I
believe
we
can
merge
that
one
now,
which
should
give
us
the
windows
of
coil,
ltsc,
2019
jenkins
image.
C
I
just
rebased
that
with
the
latest
plugin
manager
update
this
morning,
so
that
it
should
be
consistent.
I
think
it's
two
to
zero.
It's
using
across
all
of
the
images
now.
A
C
Yeah,
it
doesn't
give
you
a
a
rate
limiting
error,
but
we
think
that
we're
doing
the
docker
login
too
late
in
the
process.
B
The
so
the
it
should
be
any
docker
command,
though,
should
be
using
the
docker
config
environment
variable,
which
should
have
the
credentials.
That
was
my
understanding.
When
I
read
through
the
information
you
shouldn't
have
to
explicitly
dock
or
log
in.
If
you
have
the
docker
config
set
up,
because
it
should
use
those
credentials
automatically.
B
But
maybe
we
need
to
look
at
that
in
more
in
depth,
because
that's
how
we
do
it
on
ci
dot
jenkinson
as
we
we
have
a
with
docker
credentials
or
with
credentials,
and
it
provides
a
zip
file
that
has
the
the
docker
config
information,
the
json
file
that
has
a
username
and
password
and
so
forth
or
api
token
or
whatever
is
needed.
So
my
understanding
of
the
docker
config
environment
variable
is,
it
should
do
any
sort
of
authentication
needed.
B
So
it
may
just
be
that
we,
our
plan,
is
not
we're
not
on
the
sponsored
plan.
Yet.
A
C
Well,
we'll
we
will
see
a
failure
on
the
master
branch
anyway,
because
that's
that
hasn't
been
working
for
a
while,
but
so
this
morning,
when
I
rebased
the
pr
it
it
went
through
all
the
builds
passed.
So
I
I
seem
to
get
more
success.
C
I
I
haven't.
I
haven't,
put
this
data
into
a
spreadsheet
or
anything
but
anecdotally.
I
feel
like
I
get
more
success
in
the
morning,
my
time
rather
than
in
the
afternoon,
so
I'm
yeah
european
time
zone.
So
I
wondered
whether
that
was
because
changes
come
through
a
bit
faster
in
the
afternoon
and
yeah.
We
start
hitting
a
rate
limit
or
something
like
that.
A
B
The
the
failures
are
happening
during
the
build
right,
not
not
direct,
so
so
that
wouldn't
be
the
docker
login
stuff.
I
don't
think
because
that
the
the
docker
build
there's,
there's
never
a
call
to
docker
login
the
make
files,
don't
call
that
ever
right.
They
just
call
docker
build
t
whatever.
B
A
B
Was
that
was
part
of
the
publishing
to
like
the
experimental
that
wasn't
part
of
the
build
process,
so
what
we
need
to
do
is
we
need
to
determine
and
see
if
there's
a
way
we
can
figure
out,
if
we're
being
rate
limited
via
the
docker
api
or
something
similar
and
put
some
debug
statements
in
to
figure
out.
B
If
that's
what
we're
actually
hitting,
if
that's
what
we're
actually
hitting,
then
we
can
determine
how
we
can
solve
that
problem,
but
we
need
to
figure
out
why,
if
we
are
actually
getting
rate
limited
or
if
it's
something
where
maybe
the
docker
cleanup
is
not
being
run
successfully
all
the
time,
and
so
our
the
the
images
or
the
disks
are
getting
filled
up.
B
So
we
need
to
figure
out
why
it's
it's
failing
at
that
point,
I
think
gareth's
information
about
it
being
related
to
rate
limiting,
would
be
great
to
investigate
and
to
kind
of
zero
in
on
that
and
determine.
If
that's
the
actual
issue,
we're
running
into.
C
What
one
of
one
of
jim's
prs
had
he'd
moved
some
of
the
some
of
these
sort
of
docker
login
commands
into
like
a
common
functions
area,
and
so
it
may
be
worth
pulling
some
of
that
into
a
smaller
pr,
so
that
we
can
start
to.
You
know,
use
the
same
bits
with
some
debugging
in
throughout
the
scripts.
B
So
so
that's
kind
of
the
reason
that
we
haven't
had
the
docker
login
in
process,
because
the
understanding
was
that
docker
config
should
take
care
of
that.
So
we,
but
I
think
the
rate
limiting
stuff
is,
would
be
good
to
look
at
and
make
sure
we
have
the
right
credentials
that
are
being
used
so
that
it's
a
non-rate
limited
the
sponsored
plan
or
whatever
that
olivier
would
know.
C
That's
something
I
can
invest.
I
can
investigate
how
if
we
can
pull
that,
certainly
like
where
we
are,
with
a
rate
limiting
backup.
B
You
should
be
a
trusted
account
now
on
that
repository,
so
you
should
be
able
to
like
make
changes
to
the
jenkins
file
in
a
par
for
debug
purposes
and
stuff,
like
that.
So.
A
A
B
On
the
not
on
the
docker
hub
side,
but
he
is
on
the
he's
been
added
to
the
the
github
docker
packaging.
I
think
it's
docker
packaging
group.
C
Yeah,
I
can't
merge,
but
I
don't
have
mode
rights,
but
I
I
have
noticed
that
if
I
change
the
jenkins
file,
I
think
I'm
down
as
a
contributor
or
something
oh.
B
A
A
B
So
that
so
that's
true
of
the
the
github
side
mark
he
he
does
have
permissions
there.
The
docker
hub
side
would
be
something
we
would
need
to
to
look
at
more
if
he
needs
permissions
there
and.
A
C
B
A
new
repository
deleting
tags
stuff
like
that
are
you
do
you
have
access
on
the
jenkins
for
eval?
I
notice
there's
some
of
the
open,
jdk
images
published
there.
Are
you
publishing
those
or
is.
D
C
And
olivier
created
the
repositories
for
me.
A
B
So
go
to
repositories,
mark
repositories;
okay,
oh
sorry,
up
at
the
top,
oh
up
here
got
it
yeah
and
then
there
should
be
a
drop
down
that
you
can
change
to
the
jenkins.
C
A
All
right
so
so
we've
got
gareth
the
permission
to
merge,
that's
good,
okay,
anything
else
we
need
to
discuss
then
on
the
windows.
Docker
images
and
the
docker
login
topic
help
me
out
here.
So
it's
still
gareth
will
you'll.
Do
some
investigation
see
if
we
can
figure
out
why
the
failures
are
occurring
on
the
on
pr's
and
places.
We
know
that
it's
failing
on
master,
but
this
is
a
different
class
of
failure,
not
the
failure.
That's
causing
the
master
branch
to
break.
D
B
Yeah,
so
daniel
beck
is
very
concerned
about
the
number
of
images
that
we
publish
as
an
official
list,
because
it
takes
a
significant
amount
of
time
when
doing
security
releases
and
so
forth
that
he
has
to
wait
until
those
images
are
ready
before
we
before
he
can
proceed
with
his
process.
B
So
what
I
wanted
to
unders
to
propose
is
that
we
adopt
a
similar
method
as
to
what
the
like
adoptium
project
does,
where
they
have
an
official
set
of
images
and
an
unofficial
set
of
images,
and
the
proposal
would
be
that
we
determine
which
set
of
images
we
want
to
be
official
and
those
would
be
the
only
ones
that
daniel
would
have
to
worry
about
in
terms
of
waiting
for
a
security
release
and
then
the
unofficial
ones.
B
We
could
add
as
many
images
as
we
want
the
unofficial
list,
but
that
would
be
a
possibly
separate
build
process
for
those
unofficial
ones
such
that
daniel
didn't
need
to
wait
for
that
right
now.
We
have
quite
a
number
of
images.
We
have
sentos,
we
have
debian,
we
have
some
ubuntu,
we
have
open
j9
versus
hotspot.
B
We
have
multiple
windows
variants,
although
we
actually
reduced
that
number
jdk8
versus
jdk
11..
So
you
know,
and
that
can
only
grow
right
as
we.
If
people
want
specific
other
things
like
alpine
or
this
or
that
right,
then
it
just
it
causes
that
build
to
increase
in
time.
So
this
proposal
would
be
maybe
part
of
your
jet
mark
where
we
have
two
tiers
of
of
support.
One
is
the
official
list
and
those
are
the
ones
that
that
have
all
the
security
fixes
and
stuff
like
that.
B
The
other
ones
maybe
have
a
a
later
update
for
security
issues,
and
things
like
that,
and
you
know
the
official
ones
may
be
reduced
to
just
jdk
11
or
something
like
that
right,
because
it
is
a
controller
image
rather
than
like
an
agent
or
or
anything
like
that,
reducing
that
to
maybe
jdk
11
and
then
one
linux
variant
and
one
windows
variant
or
something
similar,
but
just
reducing
that
set
for
the
official
list
versus
unofficial
and
unofficial.
B
We
could
have
amazon,
linux
and
five
different
jdks
and
all
that
stuff,
but
that's
not
going
to
impact
the
the
security
process
for
daniel.
B
That
would
be
a
question
adoptium
does
that
you
they
have
the
the
adopt
open,
jdk
right
now,
anyway,
that's
the
official
one
that
has
a
specific
set
of
tags
that
are
quote
unquote
official
and
then
they
have
sub
repositories
under
that
for
like
open,
jdk,
8
and
open
jdk,
11
and
other
open,
jdks
and
stuff
like
that,
where
they
have
lots
of
different
tags
available
there.
So
that
is,
that
might
be.
B
The
best
way
to
go
is
to
have
a
jenkins
official
or
or
something
like
that,
where
those
official
images
are
published-
and
you
know
that's
the
the
stuff
that
the
security
fixes
will
always
be
in
the
other
stuff
will
have
a
delayed
set
of
things.
B
We'd
have
to
definitely
pull
in
daniel
on
this,
because
if
there
are
releases
of
jenkins
docker
images
that
don't
have
security
fixes,
is
that
going
to
be
a
problem
or
not?
But
but
this
is
just
going
to
get
the
ball
rolling
on
what
we
can,
what
we
could
possibly
do.
He.
A
B
Did
have
some
initial
interest
in
that,
when
I
put
it
on
irc,
but
we'd
have
to
pull
him
in
to
make
sure
it
was
something
that
he
he'd
be
okay
with
in
the
process.
A
And
I
think
that's
a
very
healthy
thing
to
include
in
the
gym,
because,
because
we've
we've
got,
we've
got
a
a
big
challenge
there.
Right
now,
it
feels
like
we've
got
far
more
doppler
images
than
we
have
maintainers
to
support
the
images,
and
so
I
think,
as
in
good
conscience,
I
feel
like
we
need
to
reduce
the
number
of
officially
supported
images
just
because
we
don't
have
enough
bodies
of
us
to
maintain
them
adequately
and
and
if,
if
people
want
want
to
maintain
an
image,
they
should
become
a
maintainer,
they
should
volunteer
and
come
help.
A
A
A
A
A
A
B
A
Okay,
so
requesting
stats
data
to
confirm
which
configurations
are
most
interesting.
A
A
B
It's
just
the
publish
experimental
and
I
think
that
jim's
pr
is
supposed
to
help
with
that.
So
we
merged
in
a
previous
pr
from
jim
to
do
some
parallelization
stuff
and
there
was
not
a
jenkins
file
update
associated
with
it,
and
so
the
wrong
thing
is
being
called
right
now
in
the
the
jenkins
file.
I
can
look
at
that.
You
can
assign
an
action
item
to
me
to
look
at
that
and
I'll
I'll
try
and
figure
it
out.
A
B
B
A
B
Yeah
I
mean
we
could
disable
it
for
now
and
then
just
have
a
pr
that
has
it
enabled
that
that
we
do
the
debug
in
that
would
make
it
pass
you're
not
going
to
have
images
actually
published
to
jenkins
for
eval,
but
they're
not
being
published
right
now
anyway.
So
it's
kind
of
a
six
dozen
one
halftone
is
the
other
six
of
one
half
to
the
dozen
of
the
other.
B
B
A
A
A
B
No,
I'm
I'm
that's
kind
of
the
part
of
the
pr
too
that
we
talked
about
earlier.
So
it's
just
something
I
need
to
review.
A
B
B
B
You
use
plugin
manager,
so
we
just
need
to
do
a
bug
scrub
of
of
all
the
docker
repos.
I
think
okay.
A
Right
yeah
sure,
well,
one
of
the
things
that's
helped
me
in
the
past
is:
should
we
show
some
graphs
once
a
month
from
the
linux
foundation's
tracking
system,
they've
got
a
system
that
watches
our
repositories
for
us,
we
use
it
in
the
doc
sig
and
it
it
it
produces
some
interesting
data
to
show
hey.
How
are
we
doing
or
not
doing
to
investigate
bring
it
to
the
next?
That's.