►
From YouTube: 2021 03 26 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
Okay,
welcome
to
the
jenkins
platform
special
interest
group.
It's
the
26th
of
march
great
to
be
here
so
topics
for
the
agenda
have
action
items
we'll
defer
the
open
container
labeling
until
gareth's
available
to
hand
I
wanted
to
give
a
status
update
on
she
code,
africa
just
so
that
people
are
aware,
and
then
we
had
coordinating
proposed,
docker
changes
and,
let's
see
topic
for
me,
was
securing
the
pipeline.
The
delivery
pipeline
just
a
brief
status
there,
and
this
one.
We
had
last
time
security
scanning
of
images
with
no
no
real
change.
B
Alex
any
topics
you
want
to
be
sure
we
touch.
No,
I
don't
think
so.
C
Something
for
a
future
agenda
maybe
is
moving
to
java
11
as
default
for
all
images.
Oh,
oh.
A
Java
11,
as
default
in
all
our
images,
we're
doing.
A
Yeah,
let's
I
think,
let's,
let's
put
it
in
there.
Let's
be
sure:
we've
got
windows
now:
windows
docker
now
we've
got
install
instructions
now
and
and
it's
getting
more
and
more
right,
I'm
not
sure,
even
that
debian,
for
instance,
will
with
bullseye
naturally
include
java
8
at
all.
So
so
it's
more
and
more.
The
default
java
is
11.
yeah,
good,
okay,.
A
A
Okay,
well,
then,
what
I'd
do
say
is:
let's
put
that
one
right
at
the
top
of
the
heap
and
assure
that
we
get
to
it
so
action
items.
I've
still
got
the
jet
to
do,
and
the
plug-in
installation
manager
increases
in
popularity,
it's
being
more
and
more
used
all
the
time.
So
I
think
we're
getting
closer
and
closer
to
just
merging
your
pull
requests
to
replace
installplugins.sh
internal
implementation
with
plugin
installation
manager.
A
A
Good,
okay,
yeah-
and
I
I
haven't
done
specific
testing
that
I
think
gareth
had
and
I'm
seeing
lots
of
activity
in
bug
reports
where
they're
using
plug-in
installation
manager
to
replicate
problems.
So
it's
it's
more
and
more.
The
the
tool
of
choice.
A
C
Would
like
to
at
some
point
use
like
an
environment
file
or
something
that
specifies
the
version
of
certain
things.
So
we
don't
have
to
go
around
and
update
20
docker
files,
but
that's
something.
A
A
Yeah
and
for
me
I
don't
mind
it
because
it's
it's
actually
a
pretty
easy
said
command
to
do
a
bulk,
replace.
So
don't
don't
don't
feel
obligated,
that's
great.
If,
if
it
happens,
that's
wonderful.
In
my
case
I
just
do
a.
I
get
ls
files
pipe
to
said
minus
I,
and
so
it's
it's
actually
quite
straightforward.
C
Okay,
I
I
know
if
there
are
other
things
that
we
eventually
have
that
have
like
versions.
We
have
to
update
all
over
the
place,
it's
kind
of
annoying
like
specific
cases
in
the
docker
agent,
where
you
have
to
go
around
and
update
several
places
for
the
remoting
version,
so
we're
looking
at
doing
something
for
that,
but
maybe
it
doesn't
apply
for
the
controller
image.
I
don't
know.
A
Well,
and-
and
that's
so
that
that
lobbies
for
a
more
general
purpose
tool,
good
good
suggestion,
the
there
is
a
tool,
olivier
verneen-
has
a
tool
called
update,
cli
that
he
uses
to
do
these
kind
of
sort
of
sophisticated
updates.
It's
a
piece
of
golang
code
that
he
uses
for
various
update
checks.
A
A
A
Then
we
we
still
have
a
topic
on
multi-arch
improvements
for
docker
images.
It
will
probably
be
many
weeks
before
I'm
back
to
that
one.
I
haven't
seen
any
activity
from
gm
on
it,
so
I'm
assuming
it's
quiet
for
now,
and
I've
still
got
the
action
item
to
note
the
the
pr
for
the
road
map
changes
that
came
out
of
the
contributor
summit.
We
do
have
a
new
june
concert.
Contributor
summit
is
being
planned
now,
the
day
after
or
the
day
before,
cdcon.
A
They
are
they're
still
connected
still
working
and
in
fact
I'm
using
them
at
times
for
just
general
purpose,
testing
and
they're,
quite
reliable.
A
C
Are
you
using
the
new
arm,
64
agents
that
are
even
lighter
weights
than
the
ones
we're
previously
using.
A
C
So
I
think,
there's
a
cheaper
option
now
that
we
maybe
can
look
into
so
I'll.
Look
into
that
for
the
packer
image.
A
C
A
Cool,
okay,
so
so,
and
I
think
tim
has
tim
jacom
has
proposed
additional
default
changes
and
I
forget
where
they
were,
but
I
know
I've
seen
a
pull
request
recently
from
him
proposing
it.
A
I
think
it's
it's
worth
us
continuing
along
that
path
and
just
planning
that
we
need
to
more
and
more
persuade
our
users.
They
should
be
using
java
11
for
their
own
benefit.
C
Yeah,
and
especially
for
docker,
it
seems
to
me
that
that's
kind
of
like
if
you're
running
a
jenkins
controller
under
docker.
You
know
why
would
you
care
whether
it's
java,
8
or
java
11.?
A
C
A
Yeah
well,
and
and
that's
we
did
it-
we,
when
we
did
the
docker
image
change
from
from
stretch
to
buster,
we,
we
blogged
it
right
and
made
the
change,
and
it
doesn't
seem
to
have
been
a
terrible
disaster
right.
I
haven't
had
any
active
hate,
mail
or
anybody
saying
that
was
a
terrible,
awful
decision
you
made.
A
A
And,
and
certainly
that's
a
place
where
we
would
probably
want
to
do
it
likely
want
that
change
based
on
daniel
beck's
guidance
earlier
on
an
lts
dot,
one
release
so
two
dot.
What
would
we
guess,
2.9
x,
2.29,
x,
dot,
one
or
something
after
that
now
there
is.
There
is
a
conversation
going
on
about
when
should
should
we
consider
doing
a
jenkins
3
in
september,
and
that
might
be
an
ideal
place
to
say
jenkins
3
is
is
going
to
go
java,
11.
A
C
Yeah,
I
think
that's
what
oleg
was
kind
of
looking
at
I
know
jenkins
is
not
currently,
the
tests
will
not
currently
function
under
java,
16.
A
C
So
there's
a
bug
on
their
repo
for
that
right
now,
so
I
I
just
did
a
tried
to
do
a
build
just
to
see
what
what
things
fell
out,
and
that
was
the
major
thing
I
found
was.
The
testing
does
not
work
correctly.
A
A
A
I
I
would
think
so
as
well
yeah.
I
think
it's
still
in
discussion,
but
it's
what
you
remind
me
is
that
I
need
to
be
sure
when
I'm
in
any
of
those
other
meetings
that
are
talking
about
jenkins
3
is
yes,
let's
use
this
as
our
chance
to
do.
You
know,
for
instance,
our
base
image
instead
of
buster
should
at
that
time
be
bullseye
are
we
should
be
using
jenkins
three?
We
should
be
using
java
11
and
be
ready,
hopefully
pretty
soon,
to
support
java
17
in
that
time
frame.
C
Adoption
does
have
java
16
images
that
we
could
base
things
on.
At
least
we
could
build
and
not
test
a
jenkins
war
and
then
pull
that
into
a
java,
16
docker
image
to
see
if
it
runs
at
all.
You
know
so
separate
from
just
the
testing
portion.
We
could
at
least
see
if
it
runs.
So
I
can
do
something
like
that.
A
Oh,
that's
and
that's
that's
so
that
would
say
we
would
take
the
code
we
currently
have
compiled
but
executed
on
java
16..
Is
that
what
you're
saying.
C
Well,
you
can
build
the
the
war
file
if
you
just
can't
test
it
under
java
16..
So
what
I
was.
C
Just
building
without
doing
any
tests
and
then
creating
a
docker
image
with
a
jdk
16
and
see
if
it
runs
at
all
you
know
or
what
errors
pop
up
or
things
like
that.
A
C
Yeah,
if
there
are
any,
I
know
there
are
some
changes
to
the
just
in
time,
compilation
and
things
like
that.
So
it's
possible
that
or
sorry
there
are
optimizations
in
the
16
and
17.
From
my
understanding
that
might
be
useful.
That
might
be
helpful
for
for
our
workloads,
but
we
can
just
take
the
the
java
8.
A
C
Run
it
under
java
16..
I
can
do
that
too.
A
C
Yeah,
that
was
my
kind
of
assumption.
I
don't
think
that
they're
producing
any
docker-based
images
with
a
17
early
access.
A
A
A
A
C
A
C
Than
than
intel
or
amd,
so
I
think
it's
just
gonna
get
more
popular,
so
they're,
probably
just
spending
more
time.
Adding
you
know,
fixing
bugs
improving
things
is
my
understanding.
A
A
Yeah,
so
that's
I
am,
I
am
thrilled
we
may.
We
may
do
more
than
that
for
right
now,
this
that
looks
like
about
the
stretch
of
it
and
I've
got
mentors
aligned.
We
may
have
to
go
begging,
specific
plug-in
maintainers
for
a
little
additional
help
as
we
go
through
it,
but
we'll
see
so
next
one
was
proposed,
docker
changes
and
I
think
the
big
one
here
is
installplugins.sh.
A
A
Okay,
all
right
and
quick
update
on
securing
the
jenkins
delivery
pipeline.
Jep
229,
using
plug-in
release
delivery
through
on
what
we
call
trusted
infrastructure
or
on
non-developer
desktops
is
so
outside
the
developer.
Desktop
is
working
and
we've
got
some
first
experiments.
The
platform
labeler
plug-in
is
has
implemented.
It.
C
Don't
have
any
pr's
yet
to
merge
to
have
a
release
done,
but
it
it
publishes
the
incrementals
and
has
the
correct
version
and
stuff
like
that.
So
I'm
I'm
assuming
when
there
is
a
pr
it
will
work
so.
A
Excellent
yeah,
so
so
I've
released
several
versions
of
platform
labelers.
Some
of
them
are
kind
of
nonsense.
It
was
oh,
this
feature
is
documentation,
but
it's
it's
worked.
I'm
there
is
additional
work
happening
there.
Gareth
evans
is
exploring
to
see
if
there's
a
way
that
we
could
preserve,
preserve
semantic
versioning
and
still
have
jep
229
working.
C
Yeah,
that
was
one
thing
that
I
was
there
is
a
way
you
can
do
that,
but
you
have
to
manually
update
the
prefix
versions
as
opposed
to
having
them
auto,
updated.
A
And
I
agree
wholeheartedly
and
what
gareth's
got
is
because
of
his
past
experience
on
jenkins
x.
They
were
doing
semantic
version
with
versioning,
with
automatic
maintenance
of
the
version
number
based
on
commit
messages.
There's
a
there's,
a
sort
of
a
standard
on
called
conventional
commits
where
they
you,
you
put
specific
text
into
your
commit
message
and
that
is
used
to
apply
labels
to
the
github
repository
or
to
the
pull
request,
and
let
it
decide
then,
which
kind
of
version
number
increment
it
needs
to
use.
A
Yeah
and
it's
a
it's
actually
a
google
summer
of
code
project
idea,
so
so
we'll
see
how
it
works.
He
may
implement
it
himself
or
or
just
continue
the
idea,
but
it
looks
like
I
love
jep
229,
but
the
version
numbers
are
a
little
intimidating
and
if
we
could
preserve
semantic
versioning
with
still
automation,
that's
oh.
That
sounds
very
interesting.
A
A
Okay,
security
scanning-
I
don't
have
anything
to
report
there,
I'm
watching
watching
the
sneak
scan
results
and
and
the
the
thing
that
I
learned
from
talking
with
oleg-
is
that
the
a
key
gap
is
that
the
jenkins
hpi
packaging
is
not
understood
it's
by
by
the
scanners,
and
this
was
thing
I
didn't
realize,
and
thus
it
flags
outdated
dependencies.
C
Is
there
a
way
to
help
depend
the
pentabot
with
certain
things,
because
it
doesn't
seem
to
like
it'd,
be
really
nice,
that
dependbot
could
manage
the
plug-in
installation
manager
tool,
for
instance?
Is
there
a
way
to
help
it.