►
From YouTube: 2021 02 12 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
Welcome
everyone
to
the
jenkins
platform,
special
interest
group
meeting.
You
should
see
the
agenda
on
screen
gareth.
Could
you
give
me
an
up
and
down
nod
of
your
head
to
confirm
that
great?
Thank
you
all
right.
So
welcome
to
the
this
special
interest
group.
It's
for
the
platform
reminder
that
we
follow
the
jenkins
code
of
conduct,
proposed
action,
proposed
items,
action
items,
status
of
the
master
branch
pending
doctor
changes
and
contributor
summit.
Any
other
topics
you'd
like
to
add
to
the
agenda.
B
I
actually
have
one
that
I
have
just
thought
of
okay,
which
kind
of
relates
to
our
conversation
earlier.
I,
I
suppose,
a
proposal
about
adding
the
open
container
labels
to
all
of
our
docker
images.
B
It
may
it
may
well
be
okay,
okay,.
C
B
A
All
right,
let's
let's
go
forward,
then
so.
Action
item
reports,
docker
items
operating
system,
jeb
draft-
is
still
there.
I
would
like
to
discuss
the
draft
during
a
track
at
the
contributor
summit,
so
that'd
be
my
proposal
and,
and
that
would
be
a
place,
a
format
where
we
do
it,
try
to
invite
people
and
encourage
them
to
to
to
be
there.
A
So
any
objections
to
that
as
a
as
a
topic
for
one
of
the
tracks:
there,
okay,
plugin
installation
manager
and
update
center
blog.
So
we've
got
the
shim
replacement
for
installplugins.sh,
which
we
thought
might
lobby
that
we
don't
need
to
even
do
this
blog
post
alex.
What's
your
sense
based
on
installplugins.sh,
I
started
my
evaluation
found
no
issues
with
it
but
feel
like.
I
need
to
do
more.
C
Yeah,
I
think
it
might
be
good
to
have
a
blog
post
just
talking
about
our
idea
and
and
so
forth.
Just
you
know,
we
don't
want
people
to
be
super
surprised.
I
don't
know
how
many
people
actually
read
the
blog
post
and
still
be
surprised
if
they
don't,
but
we
can
always.
You
know,
be
a
little
bit
proactive
about
it.
A
A
That's
great
thanks
all
right,
so
so
other
changes
we've
successfully
completed.
Our
santos
image
is
now
using
adoptium.
It's
using
adopt
open
jdk,
just
like
our
alpine
image
and
our
debian
image,
so
big
win.
Thanks
alex,
we
have
replaced
debian
9
with
debian
10.
We
are
no
longer
shipping,
an
operating
system
that
the
vendor
has
shifted
to
only
doing
lts
security
support.
For
so
we
are
on
the
current
operating
system.
Bullseye.
A
A
A
B
Yeah,
so
it's
just
about
adding
a
consistent
set
of
labels
to
all
of
the
images
that
we
produce
so
that
we
can
provide
hints
at
the
origin
of
those
images.
Really
it's
worth
noting
that
you
can
obviously
fake
the
labels
and
you
don't
have
to
add
them
and
there's
no
way
of
proving
that
the
labels
that
you've
added
are
in
fact
correct
or
validated,
but
it
just
it
helps
I'm
trying
to
understand
where
something
has
come
from.
C
B
So
that
is
yeah,
so
there's
there
seems
to
be
two
specs,
so
there's
the
label
schema
is
one
of
them
and
the
open
container
set
of
labels
that
are
another
and
they're
pretty
much
the
same
thing.
So
we
could
add
one
of
those
or
both
of
those.
That
would
be
something
like
that.
Yeah.
B
Yeah,
I
think
it's
an
awkward
one
to
add,
because
there's
probably
a
few
other
labels
that
you
want
to
add,
such
as
things
like
bill
date
that
we
don't
have
there
and
the
the
really
useful
one
is
the
commit
show
that
it
comes
from
which
you
can't
really
add
from
inside
the
docket
image.
Unless
you
pass
it
in,
it's
either
a
build
arc
or
you
just
pass
on
the
command
line.
So
I
think
we
would
need
further
changes
to
this,
but
I
think
I
think
just
looking
at
that
pr.
C
Yeah,
I
think
the
other
problem
we
had
was
that
for
windows.
We
we
fully
control
the
build
process,
and
so
we
can
add
additional
arguments
and
things
like
that
to
the
build
process,
but
for
linux
we're
we're
currently
using
docker
hub
builds,
and
I
don't
think
you
can
inject
any
additional
arguments
on
docker
hub
builds
to
do
like
build
date
and
stuff
like
that.
So
that
was,
I
think,
one
thing
that
was
kind
of
holding
this
up
as
well
as
we.
B
Right
so
there's
certain
there's
sort
of
more
of
the
static
labels
we
can
add
because
we
can
add
them
inside
the
docker
file
but
yeah
anything
dynamic,
okay
right
so
do
you
know
which
ones?
Sorry
sorry
go
mark.
No!
No
after
you
gary!
Well,
I
think
we're
about
to
say
the
same
thing
I
was.
Is
there
already
a
proposal
to
switch
from
docker
hub.
C
A
Okay,
so
so
that's
a
that's
still
a
topic,
because
I
think
there
is
interest
in
in
having-
and
I
thought
that
jim
crowley
had
vermont
noted
to
us
that
there
were
problems
associated
with
choosing
to
use
a
docker
house-based
build
where
if
we
build
our
own
hardware,
we
can
avoid
those
problems.
So
I
think
it's.
This
sounds
like
a
very
reasonable
one
for
us
to
be
reminded
of,
and
continue
working.
A
A
D
No,
there
may
have
been
some
work
on
the
windows,
images
that
need
to
be
done
possibly,
but
no
everything
is
fine.
There.
I've
just
been
pulled
away
from
that
in
the
last
week
or
so.
A
A
Okay-
and
we
this
one-
I
think
the
tagging
tagging
and
announcement
if
we
were
to
do
open
container
and
label
and
or
label,
schema
and
add
more
verbose
tags.
Those
all
feel
like
a
good
fit
for
a
blog
post,
saying,
hey
here's,
what
we're
doing
and
why
we're
doing
it.
A
Last
topic
on
my
list
was
the
contributor
summit,
and
I've
got
a
note
on
the
contributor
summit
here
that
what
I've
done
is
I've
drafted
up
a
section
proposing
a
jenkins
on
docker
track,
or
we
could
call
it
just
a
a
jenkins
platform.
Sig
track
jenkins
platforms
track.
The
contributor
summit
will
be
february,
23,
24
and
25.
A
The
first
session
will
be
inviting
everyone
to
come
together,
90
minutes
of
that
session,
we'll
be
talking
and
presenting
what
we've
done
so
far
and
what
we're
envisioning
next
from
people
who
are
leads
of
various
special
interest
groups
or
officers
in
various
roles,
then
the
last
30
minutes
we'll
use
to
coordinate
how
we're
going
to
use
the
next
48
hours
in
that
sequence,
to
do
these
tracks
and
find
times
that
work
for
people,
then,
after
that
48
hour
period,
the
when
these
tracks
have
all
met
talk
then
we'll
do
a
concluding
session
and
hear
from
the
various
track
leaders
to
talk
about
hey.
A
We
found
this.
We
found
this.
The
ideas
will
make
things
fit
with
our
various
time
zones
during
that
48
hour
period,
I'll,
send
out
registration
information
on
the
plot.
On
the
the
contributor
summit,
it'll
be
a
google
form
based
on
conversations
in
jenkins
governance
a
day
or
two
ago
any
questions
or
concerns
on
the
concept
of
contributor
summit
or
the
platform
6
involvement
in
it.
A
Containers
really
good
good
point,
so
maybe
what
we
should
call.
It
is
jenkins
on
containers
yeah,
because
because
my
thought
was
this,
I
just
wanted
a
platform
track,
but
maybe
jenkins
eye
containers
is
a
much
better
choice
for
a
name,
because
docker
is
not
the
only
container
spec
in
the
world.
Is
it
my
assumption
is.
We
would
not
talk
here
about
running
jenkins
inside
a
freebsd
jail.
Much
as
I
love
my
jails
and
much
as
I
think,
they're
so
cool.
That's
not
the
topic
here.
A
A
I
guess
one
open
question
is:
should
we
meet
as
platform
sig,
thus,
the
day
after
the
contributor
summit
ends
and
my
preference
is
probably
not?
Let's
cancel
the
next
meeting
in
favor
of
in
favor
of
attending
the
contributor
summit.
A
Yeah,
so
the
opening
session
will
be
from,
I
think
it's
scheduled
from
15
to
1700
hours.
Utc,
so
it'll
be
a
european
european
time
zone
for
those,
because
those
seem
to
work
well
for
us
for
large
group
meetings,
then
we'll
do
this
we'll
find
times
that
the
the
other
tracks
work
based
on
who's
involved
in
the
track.