►
From YouTube: 2023 06 06 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
Yes,
oh
sorry
about
that,
I
thought
we
were
still
waiting.
Anyhow.
Sorry
thanks.
A
lot
welcome
everyone.
This
is
a
Jenkins
platform
Sig
meeting
today
we're
on
the
6th
of
June
2023
and
we
have
Mark
Wade,
Damien,
Dupont
and
Kenneth
Salerno,
hello,
everyone
and
thanks
for
coming,
we
had
the
usual
open,
Action
items,
but
one
of
them
is
somehow
progressing.
We'll
see
that
later
on,
we
have
the
ongoing
the
what
has
been
done
and
an
open
question
in
the
end.
A
So,
first
of
all
for
the
open
action
item,
we
have
the
usual
Docker
images.
We
should
let
people
know
when
our
image
is
get
outdated
and
so
on
so
most
of
the
time
it
doesn't
progress
but
Mark
you
created
or
participated
in
a
major
update
regarding
depreciation.
We
talked
about
that
in
the
previous
meeting
and
the
first
effects
should
be
seen
from
this
week
or
something
like
that.
I've.
B
A
That's
super
cool,
but
it's
not
yet
about
the
bluish
and
container
image
correct.
It's
not
you
set
up
a
framework
and
foundation
work
name
it
that
will
allow
us
whenever
the
time
comes
to
say:
hey
it's
deprecated
or
am
I
wrong
or
am
I
right
about
that.
You're.
B
Correct
it's.
We
need
more
work
in
order
to
do
in
order
to
deprecate
Containers
independent
of
the
operating
system
on
which
they
are
running.
So
so
the
container
image
can
be
deprecated,
even
though
the
operating
system
is
still
fully
supported.
These
blue
ocean
containers,
for
example,
are
actually
running
Debian
and,
and
we
continue
to
support
Debian,
but
we
don't
want
to
support
that
container.
So
what
we'll
do
is
We'll
add
a
little
bit
of
some
extra
stuff
into
those
container
images
that
will
let
the
detector
say.
Oh
you're,
running
a
deprecated
container
image
switch.
B
It
was
just
that
it
mistakenly
the
the
warning
mistakenly
appeared
telling
you
that
Fedora
38
end
of
life
has
happened
and
I
think
Kenneth
actually
is
running
Fedora
37,
so
he
didn't
detect
it.
I
didn't
detect
it,
but
a
user
did
and
said.
Look
Fedora
38
is
very
much
still
alive.
Oops.
Please
correct
your
message
and-
and
it
was
only
an
off
by
one
error-
I,
don't
know
what
everybody's
complaining.
A
Okay,
that's
funny.
Last
time,
I
looked
at
Community,
jenkins.io
I
didn't
see
any
people
complaining
about.
What
are
you
saying?
My
operating
system
is
out
of
date
or
something
I
don't
know
if
this
has
happened
since
yesterday,.
B
A
A
A
We
can
hope
that
people
that
use
old
operating
system
don't
update
weekly
the
weekly.
D
And
actually
I,
don't
think
I
would
I'm
trying
to
think
if
I
would
catch
it.
In
my
build
environment,
oh
no
I
did
I
did
switch
to
Fedora,
so
I
should
have
yeah,
but.
D
Do
I
pulled
down
the
latest
basic
image
so
I
so
I
it
would
be
38
for
me.
C
B
A
Thank
you
Mark
next
was
the
ongoing
work.
I
started.
I.
Think
two
weeks
ago
worked
on
Alpine
images
with
Damian.
The
first,
which
was
it
Docker
resist
agent,
can't
remember
all
Docker
agent.
It
worked,
but
then
I
stumbled
on
an
issue
related
to
regex,
of
course,
for
updates
July.
So
for
the
time
being,
it's
stuck
waiting
for
some
help.
A
Yes,
without
regex,
timestamps
and
short
set,
we
would
be
out
of
work
anyhow
what
else
yeah
send
to
S7
early
end
of
life
so
mark
your
pull
request
is
merge
pass
off
to
407,
so
you
got
some
warning
from
users
because
there
was
something
about
Federal
but
sent
to
i7
no
news
from
anybody
or
the
time
being,
the
blog
post
is
now
yeah
visible
thanks
a
lot
for
sharing
that.
A
And
I
guess:
if
we
had
a
look
at
the
logs
for
the
genkisabi
website,
we'll
see
you
pick
from
now
on
regarding
this
very
much
this
article
and
as
a
rem,
we
have
to
remember
that
this
will
appear
in
the
LTS
in
August
yeah.
That's
it
at
the
end
of
August
and
not
before
Mark.
Aren't
we
supposed
to
go
to?
Oh?
No,
we
don't
know
yet
sorry,
so
it
will
be
2.413.x.
We.
A
A
Yep,
so
it's
still
the
right
candidate,
we'll
see
cool
next
thing.
We
have
to
replace
into
S7
usage
in
our
Jenkins
controller
containers.
That
was
something
Damien
you
proposed
in
the
last
meeting.
So
I
may
have
misunderstood
what
you
were
looking
for,
but
nonetheless
I
made
a
draft
PR.
A
That
I
wanted
to
be
an
open
discussion
with
the
community,
except
that
it
was
not
clear
at
all
in
the
description
of
the
pr,
so
I
have
something
that
works,
but
it's
very
much
a
draft
of
course.
There
are
a
lot
of
things
which
are
hard-coded
like
the
checksums,
for
example.
So
it
does
work,
but
it
needs
a
lot
of
work
and
I'd
like
if
possible,
that
the
community
chimes
in
and
says
that's
a
good
idea.
That's
a
bad
idea.
Maybe
we
should
do
something
else,
we'll
see
Damian.
A
You
had
quite
a
lot
of
Pros
for
doing
so,
but
also
maybe
a
few
comments.
C
Will
demonstrate
that
we
can
keep
the
multi-stage
build
with
the
g-link
using
the
direct
installer
from
demarin.
The
initial
idea
was
to
consider
that
solution
as
a
fallback.
If
we
see
issues
with
the
Alma
and
UB
selection
in
the
case,
in
the
eventual
case
of
we
don't,
we
cannot
use
a
parent
image
that
would
have
the
same.
That
would
have
that
wouldn't
have
a
compliant
GDK
installed
Within,
the
the
probability
of
this
was
low,
but
not
sure
we
had
to
check.
So
that
was
a
proposal.
C
If
we
are
stuck
on
one
of
the
H
cases,
we
could
directly
download
the
official
Tamarind,
zip
and
zip
it
and
build
the
g-link.
So
that's
the
proposed
official
that
should
be
compliant
will
be
linked
and
adapted
to
our
image.
What
you
did
demonstrate
that
it
works
very
well.
It
requires
a
bit
of
code
that
might
require
the
checksum
with
the
update,
CLI
or
renovo
bot
or
Dependable.
If
we
want
to
keep
it
updated
but
outside
is
that
work
very
well?
C
Another
reason
was
big,
sometimes
not
all
the
time
when
there
is
a
May,
a
significant
GDK,
updated
Tamarind.
The
installer
is
available
way
sooner
than
the
docker
images
most
of
the
time.
The
default
Ubuntu
image
with
the
timarine
within
is
available
immediately
for
Intel,
but
then
the
rest
it
depends
sometimes
the
ERM
are
there
quickly,
sometimes
not
sometimes
same
for
PPC
or
sun
to
SUV
Etc.
So
if
we
have
the
installer,
the
installer
is
the
first
step
when
the
publish
on
your
release,
especially
in
the
case
of
security
releases
of
the
GDK.
C
That
would
have
been
a
reason,
a
compelling
reason
to
switch
from
our
AC
multi-stage
from
the
official
parent
image
to
a
multi-stage
like
you
implemented,
given
the
status,
and
there
is
no
clear
consensus
and
the
effort
on
that
part.
We
first
need
to
update
the
base
Alpine
base
operating
systems,
The
Proposal
I'm,
making
here
I'm
chiming,
in
is
to
say,
let's
consider
that
an
experiment
close
it
for
now.
D
B
D
A
You
told
me
the
other
day
that
it
would
be
problematic
to
depend
on
the
existing
Tamarind
Docker
images
in
case
of
a
cve,
because
it
could
take
up
to
three
weeks
before
we
get
the
corrected
image.
So
that
makes
sense
in
that
case,
but
also
I,
don't
know
the
status
of
update
tli
for
these
images.
So
is
it
already
working
or
are
we,
depending
on
dependables,
dependable.
C
A
C
C
C
Yeah
yeah
exactly
being
sure
that
we
track
the
GDK
version
on
all.
The
images
is
a
good
first
step.
A
C
No
problem
getting
the
checksum
is
quite
easy.
We
do
that
on
the
infrastructure
and
we
already
experimented
it's
a
bit
of
scripting
on
update
CLI.
But
technically
there
is
no
problem
on
this.
One.
C
You
can
work
with
both
on
Parallel
if
you
are
stuck
on
the
regex
and
don't
get
help
or
frustrated
with
that,
because
I
kind
of
I
I
I
can
be
quickly
frustrated
by
regex
as
well.
But
in
that
case
the
checksum
Portis
gets
the
latest.
C
D
A
D
A
Cool
they
are
the
golang
version,
I
guess,
if
not,
that
I
don't
like
regular
I.
Do
love
rigots
I
use
regularly
emacs
with
rigots,
with
some
kind
of
success,
even
online
go
long
regex.
You
know
tester
tell
me
my
reg
apps
work.
C
A
Anyhow
or
maybe
I
can't
read
the
logs,
but
anyway
that's
not
the
subject.
Thanks,
that's
much
pure
to
me
now
and
there
are
other
operating
system
end
of
life
and.
A
That's
yeah,
thank
you.
Mark.
It
was
from
last
meeting
I
copied
paste
bad
boy.
Then,
frankly,
I
read
the
pull
request
to
you
know
your
proposal
to
switch
all
my
Linux
from
eight
to
nine
I
saw
that
you
closed
it
after
putting
a
hold
on
or
something
I
read
the
whole
discussion
and
to
be
totally
honest,
I
didn't
get
everything
there
were
lots
of
inputs
and
I,
don't
know
if
you
could
make
a
summary
of
what
happened
in
this
pull
request.
B
Yeah,
so
it
fits
exactly
with
the
question.
Kenneth
asked
last
time
why
Alma
Linux
instead
of
Ubi,
and
so
that
question
was
asked
and
Oliver
ganja,
who
maintains
the
Ubi
container
images,
said
yeah
you're
right.
However,
there
are
limitations
in
Ubi
that
are
not
there
in
the
in
the
alma
Linux
container,
in
terms
of
which
packages
you
can
use.
So
what
Oliver
suggests
was
hey
when
people
ask
for
an
upgrade,
we
should
Point
them
towards
the
Ubi
containers
and
see
if
that
works
for
them.
B
D
Yeah
and
I
think
there
was
a
confusion
from
one
of
the
users
that
you
needed
a
subscription
to
install
any
packages,
which
is
only
true
if
you
needed
to
extend
beyond
what
uvi
comes
with
in
its
worry
right
and
and
I
use
Ubi
all
the
time
and
find
that
it
has
the
packages
I
need
so
I'm,
not
quite
they
need
to
detail
what
what
are
these
packages?
They
need.
That's
outside
of
that,
and
maybe
that's
even
in
the
Apple
extended
repository
anyway.
B
B
D
I
mean
full
disclosure,
I
mean
I,
do
work
for
IBM,
so
I'm
going
to
be
a
little
biased
but
and
I've
been
in
a
red
hat
customer
for
almost
25
years,
maybe
longer,
but
so
I
have
a
lot
of
a
lot
of
experience
with
red
hat
in
general,
but
I
I
find
that
all
of
these
derivatives
that
are
building
rebuilding
the
source
there
is
a
lag
right.
You
know
it's
not
going
to
be
quite
as
up
to
date.
D
B
A
Yes,
thank
you
much
better
when
you
are
telling
me
the
truth,
except
of
me
now,
instead
of
me,
reading
the
whole
thread
and
not
getting
much
of
it
yeah.
Thank
you.
It's
much
pure
now,
next
subject
what
has
been
done?
A
few
updates
on
the
docker
images,
nothing
major
at
this
time!
No
breaking
change!
Let
me
know
Damian
if
I'm
wrong
of
that,
so
SSH
agent
5.3.0
just
a
few
dependency.
A
C
So
no
that's:
okay,
Docker
inbound
agent
should
have
update
CLI
request
today,
because
the
release
of
the
parent
was
done
yesterday.
So
another
example:
why?
Having
two
I
guess
there
there's
been
multiple
updates,
CLI
updates,
so
that's
might
be
failing.
We
need
to
check
why,
but
we
should
be
able
to
use
the
docker
region
parents
soon.
C
C
A
You
did
a
major
update,
upgrade
move
whatever
this
week.
So,
of
course
nothing
was
expected
on
this
side.
Thanks
a
lot
for
the
work
you
did
by
the
way
now
Damien
there's
another
other
subject
for
you:
we've
been
talking
about
Docker
help
stats
for
weeks
or
months
now,
and
you
have
created
a
shared
spreadsheet
with
a
lot
of
information.
Could
you
tell
us
a
few
things
about
it?.
C
Yes,
so
these
are
the
stats
directly
from
the
docker
Hub
for
each
month,
so
I
only
went
back
in
time
until
beginning
of
this
year.
We
can
go
back
in
time
on
previous
year
if
needed,
so
I,
don't
know
how
much
we
have
access
I'm,
not
sure
who
else
have
access
I'm
admin
on
the
organization.
C
With
due
to
my
infrastructure
hat,
we
might
have
the
possibility
to
open
that
access
for
other
person,
because,
if
me
being
is
of
this
Factor,
that's
not
really
healthy,
right
now,
I've
added
to
my
monthly
billing
reporting
of
the
infrastructure,
the
task
of
also
reporting
the
download
stats
here,
that's
short
term
on
the
content.
For
each
month
you
have
two
two
chats
one
which
is
rip
a
summary
pair
repository
so
per
image,
and
one
which
is
detailed
with
spare
tag
and
perjection.
C
C
C
We
should
think
about,
oh
to
be
sure
that
these
images
generate
a
big
red
message
on
Jenkins
console
that
say,
I
see
you
are
using
an
unmaintained
image
with
which
is
a
full
Hull
of
CVS
and
stuff.
Something
really
scary
right.
A
B
B
These
two:
we,
we
supplied
the
new
images
long
ago
and
they
should
have
switched
long
ago
right,
because
these
two
are
really
this
one
right,
they're
these
these
right
here.
So
so
it's
the
at
least
for
those
two,
the
Legacy
there
is
people
just
aren't
paying
attention
to
their
system.
It
works
and
that's
good
enough
for
them.
Yep.
C
C
If
they
are,
we
have
another
problem
which
is
on
our
side,
but
if
they
aren't
on
that
hypothesis,
they
will
use
all
the
operating
system
version
so
that
at
the
moment
in
time,
the
old,
alpines
and
Os
Debian
version
will
be
mentioned
as
out
of
date.
So
in
any
case
that
will
have
an
impact.
A
B
Idea,
the
idea
that's
still
still
evolving
is
that
the
controller
should
somehow
see
that
it
was
asked
to
launch
a
container
image.
That's
labeled
is
Jenkins
colon
jnlp-slave
and
it
should
say
in
some
place,
you're
using
an
outdated,
can
you're
using
a
container
image
that
we
know
you're
not
supposed
to
be
using.
B
C
C
C
Thank
you
so
yeah,
that's
all
for
the
statistics.
Now,
eventually,
the
detailed
statistics
can
helps
us
about
the
operating
system,
but
that
need
to.
We
need
to
create
dashboards
or
spreadsheet,
with.
C
D
A
Okay,
I,
don't
want
to
name
names,
but
John
Mark
loves
to
do
that
kind
of
spreadsheet,
graphics
and
so
on.
Never
know
good
help
with
that.
The
last
question
I
have
about
that.
Is
that
a
manual
Shore
or
is
it
automated
in
some
way.
C
No
I
don't
know
how
we
could
automate
it
right
now,
because
that
will
require
highly
privileged
credential,
even
if
we
restrict
to
this
one.
So
that
name
in
a
token
that
we
need
to
rotate
with
2fa
enabled
okay
same
for
adding
I
mean
it's
it's
a
matter
of
credential,
so
yeah
and
the
time
for
Automation
and
tests.
Clearly
doesn't:
doesn't
it's
not
worth
it
compared
to
five
minute
per
month
to
updating
it?
C
D
B
Sure
you
can
well
to
deciding
I,
see
one
right
here.
There's
this
project
called
Evergreen.
That
was
a
long
ago
project
that
we
we
switched
off.
There's
another
one
called
Jenkins
file
Runner,
and
these
are
both
indicators
that
they
are
really
switched
off
right,
the
very
small
numbers.
There
are
good
measures
for
US.
Okay,
we
have.
We
do
not
have
many
active
users
who
are
running
those
things
that
were
switched
off
so
that
kind
of
that
kind
of
data
helps
me
a
bunch
in
deciding.
D
A
D
B
But
well
and
it
for
me,
it's
the
the
ratio
between
this
number
114
000,
unique,
IPS
and
21.,
given
that
Ratio
or
or
even
the
agents
ratio,
which
is
let's
see
where's
the
the
inbound
agent
inbound
agent,
is
here
and
it's
towards
the
top
yeah.
Ninety
eight
thousand
so
100
000
to
21
three
orders
of
magnitude
is
more
than
good
enough
to
to
say
that
we've
succeeded
in
not
having
that
running
widely.
B
C
I
know
that
Docker
as
an
Integrity
garbage
collector,
which
delete
images
that
hasn't
been
pulled
since
years,
so
the
image
is
automatically
deleted.
The
thing
is
I'm,
not
sure
for
the
low
level
image.
What
is
the
rear
threshold?
Is
it
an
absolute
zero
pool
at
all
or
if
there
are
few
pools
here
that
are
an
internal
Docker
bot
that
check?
That
could
be
something
or
the
update
version.
C
I,
don't
know
the
detail,
but
I
saw
some
of
my
personal
images
that
already
hold
since
the
first
years
of
Docker
app
that
disappeared,
so
the
process
is
already
working
since
at
least
2020.
That's
why
they
added
the
API
rate
limit
as
well.
So
some
of
our
images
might
disappear
at
the
moment
in
time.
That's
a
good
question.
My
personal
opinion
is
yes.
We
should
remove
these
images,
but
that
could
be
a
problem
to
send
to
the
product
manager
at
Docker,
because
that's
a
problem
they
could
help
us.
C
Is
it
possible
to
have
still
have
a
page
on
the
docker
Hub
while
the
image
is
removed
from
their
registry?
That
would
help
saying:
okay,
we
keep
an
image,
a
valid
URL
on
the
docker
herb,
it's
not
indexed
by
the
research.
So
you
cannot
search
for
that
image
anymore.
But
if
someone
has
another
link
pointing
to
that
image
or
know
how
to
directly
reach
the
page,
then
we
could
say:
oh
that
slave
image
has
been
depressed
since
five
six
years
and
now
you
have
to
go,
there
I
think
it's
worth
asking
Docker
product
management.
C
They
might
have
already
tools
for
that
and
that
question
spans
to
the
official
Jenkins
image
which
you
already
have
deprecated
thing:
I'm,
not
sure.
What's
the
status
I'm
almost
sure
you
cannot
find
it
by
searching
it
now,
but
I
might
be
wrong.
So
could
be
interesting
to
see
directly,
because
these
are
specific
action,
one-time
action
to
be
taken
by
docker.
A
Thank
you,
Demi
and
I'm
afraid.
This
is
all
we
had
we're
already
late,
because
we
started
late
because
of
me
so
I
guess
this
one
will
keep
it
for
next
time,
thanks
a
lot
for
your
time.
Folks,
thanks
a
lot
for
your
help,
thanks
rod
for
coming,
we
do
appreciate
it.
The
video
should
be
available
on
YouTube
from
24
to
48
hours
from
now
have
a
good
rest
of
your
day.