►
From YouTube: 2021 04 09 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
agenda
item
review
proposed
to
review
the
open
action
items.
We
had
a
discussion
on
java
11
as
default
in
all
our
images
with
alex.
Not
here
I'd
like
to
talk
to
that
one
so
that
we
we've
continued
the
discussion,
then
we've
got
pending
changes
to
docker
images.
A
That
needs
some
further
discussion.
I
think
securing
the
delivery
pipeline
gareth.
I
think
this
is
one
where
some
question
and
answer
discussion
with
you
on
your
current
experiences
and
would
be
a
big
help
and
then
security
scanning
just
a
status
report.
Anything
else
that
needs
to
go
on
the
agenda.
A
Okay,
all
right,
so
I've
got
the
action,
I'm
still
to
do
the
docker
operating
system
jeff.
There
is
a
discussion
right
now
testing
the
idea-
and
I
like
that,
if
there's
a
pr
where
a
user
has
proposed
an
arch
image,
so
an
arch
linux
image
and
answered
alex's
question:
would
you
be
willing
to
maintain
it
with?
Yes,
I'm
willing
to
maintain
it.
A
And
so
that
one
needs
more
evaluation
and
then
we
need
to
decide
how
we,
how
we
put
that
person
as
a
code
owner
over
over
that
particular
thing,
etc.
A
Plug-In
installation
manager,
gareth
and
I
were
just
discussing
there-
are
some
additional
enhancements
there,
and
this
is
becoming
more
and
more
widely
used.
It's
standard
documentation
and-
and
it
really
does
belong
in
the
documentation,
there's
so
many
good
things
we
can
do
with
plug-in
installation
manager,
tool.
A
A
Next
topic,
then,
was
java
11
in
our
default
images.
So
this
one
there
is
continuing
discussion.
Should
we
consider
doing
a
jenkins
3
release
in
september
make
a
major
change.
The
discussion
will
continue
happening
in
the
in
the
mailing
lists,
and
at
that
point
the
idea
was:
should
we
make
java
11
the
standard
everywhere
or
even
before
that,
just
make
it
the
default
everywhere,
and
if
you
want
java
8,
it
takes
a
little
more
work.
B
So
I
suppose
one
of
the
issues
is
around
then
the
labels
on
the
docker
images
because
you'll
be
changing
the
you
know
the
the
one
that's
just
called
lts
will
jump
from
java
8
to
f11
right.
A
Exactly
right
and
and
the
way
we
handled
that
the
last
time
was,
we
just
announced
we're
we're
changing
from
debian
stretch
to
buster.
You
know
from
debian
9
to
10..
We
announced
it
as
a
blog
post
and
the
contents
inside
the
image
changed
and
it
seems
to
have
actually
worked
out
okay,
but
we
would
do
the
same
kind
of
thing
where
we
just
use
a
blog
post
announcement.
Hey
the
the
base
java
version
that's
running
inside.
This
is
switching
from
8
to
11.
A
B
So
there
was
com,
there
was
conversations
with
oleg
around
running
agents
and
running
controllers
with
different
jdk
versions,
and
how
that
it's?
Not
it's,
not
a
recommended
thing.
B
I
suppose
it
could
cause
issues,
but
I
suppose,
as
long
as
there
is
a
a
jdk
8
variant
that
people
can
switch
back
to
but
yeah,
then
that's
probably
okay.
I
know
that
it's
where
they
switch
to
jdk
11
automatically
in
the
helm
chart.
So
if
you
upgrade
to
the
latest
version
of
the
home
chart,
you
will
get
a
jdk
11.
A
B
Yeah,
no,
no,
not
not
not
that
I
can
tell
you
know
we're
in
the
past.
B
A
B
A
A
A
B
A
A
Okay,
so
multiple
docker
changes-
these
have
been
somewhat
on
hold
for
me,
as
I've
had
to
focus
on
other
things.
I
think
the
most
interesting
one
is
this
replacement
of
installplugins.sh
with
plugin
installation
manager,
accompanied
by
documentation
better
documentation
to
support
it.
So
it
would
be
a
good
thing
to
merge
about
the
same
time
or
when
we
provide
the
new.
B
No,
I
know
that
damien
has
been
working
on
a
plug-in
library
to
allow
easier
building
of,
like
monorepo
style,
docker
images
which,
which
is
one
of
the
things
that
was
kind
of
holding
up
a
lot
of
these.
B
I
think
it's,
the
non-root
user
part
and
those
changes,
so
I
think
because
because
it
was
actually
we
wanted
to
use,
we
wanted
to
have
all
the
features
of
plug-in
library,
but
the
plug-in
library
assumes
one
docker
file
in
the
root
normally
for
repo
to
do
it's
lagging
and
everything
like
that.
But
actually
what
we
want
to
do
is
build
multiple
images
from
the
same
repository,
so
he's
he's
been
experimenting
with
ways
that
we
can
get
it
to
do.
That.
A
B
Yeah,
so
it
it
all
in
all,
it's
been
it's
a
much
nicer
release
process
than
what
we've
currently
had
or
what
we've
previously
had,
especially
for
plugins
that
I
used
to
maintain
and,
like
I
don't
know
where
my
credentials
or
information
like
trying
to
release
it
from
my
local
machine
and
having
it
set
up,
is
something
that
I
always
forget
about.
So
having
like
a
single
place,
where
you
can
do
it
automatically
on
a
interesting
commit,
is
really
useful.
B
Yeah,
it's
really
handy
some
of
the
kind
of
enhancements
that
we've
been
looking
at
on.
Some
plugins
are
around,
rather
than
using
the
generated,
build
a
number
which
you've
got
an
example
of
that
like
820
dot,
bab,
something
or
that,
because
that's
not
semantic,
that's
not
a
semantic
version
is
to
use
jx
release
version
to
determine
the
next
semantic
version.
For
you
automatically,
we've
had
some
good
success
with
that.
A
B
I
mean
yeah
sure
so
it's
it's.
It
tries
to
determine
the
latest
tag,
that's
already
there
and
it
uses
that
as
a
starting
point,
and
it
will
then
look
at
the
commits
that
have
been
added
since
that
bag
and
where
you're
currently
at,
and
it
will
then
calculate
what
the
version
bump
should
be
based
on
the
conventional
commit
sort
of
stuff,
yeah
conventional
bits
format.
B
B
And
and
just
using
that
that
sort
of
versioning
scheme
means
that,
when
you're
looking
at
plugins
in
either
in
the
plugin
installation
manager
or
the
the
manage
jenkins
interface,
you
can
actually
kind
of
see
what
the
changes
are.
You
get
straight
away,
and
you
can
say:
oh
I'm
fairly
close
to
this
plugin
rather
than
I
don't
know,
builds
820
jumping
to
build
824
with
a
random
shot
at
the
end.
I
don't
know
what
I
don't
know
what
that
is.
A
A
A
That
will
allow
us
to
use
semantic
versioning
thanks
to
and
you
described
it,
it
was
convenient
yeah.
B
A
Know,
okay,
which,
which
I
mean
we've
done
developer
online
meetups
before
for
these
kinds
of
things.
This
might
be
a
great
one
to
do
a
developer
online,
meetup
to
say:
look:
here's
how
you
can
improve
your
development
process
as
a
plugin
developer.
Life
gets
simpler.
If
you'll
do
this
and
here's
this
tool
that
will
help
you
do
that.
A
B
From
the
the
plugin
developer,
part
of
jenkins.io.
A
B
So
that
it
ignore
it
can
be
searched,
and
it's
indexed
with
with
a
link
to
the
recording
of
the
online
meetup
or
something
like
that.
That
would
be.
That
would
be
really
handy.