►
From YouTube: 2023 08 29 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
A
Bruno
verachten:,
we
have
some
ongoing
work
at
the
minute,
they're
cool,,
because
it
has
a
lot
of
things
to
tell
us
about
what
is
going
on..
We
have
oh,
a
new
subject.
thank
you,
mark,
about
java,
1117
and
21
with
jenkins..
If
we
have
time
to,
we'll
talk
about
what
has
been
done
recently
on
the
docker
images,
and
we'll
finish
with
new
topics.,
maybe
you
should
put
the
new
topics
before
this
one,
anyhow,.
Let's
get
started.
A
Bruno
verachten:
on
the
open
action
items,
as
always
so.
the
jenkins
bluishian
image,
is
still
deprecated
and
will
always
be..
I
guess
we
haven't,
announced
yet,
officially,,
the
deprecation
of
the
image,,
and
even
if
we
don't
build
it,
anymore.
correct
me.
If
I'm
wrong.,
the
plugins
still
leave
and
get
updated
by
updated..
I
guess
it's
only
bug
fixes,,
but
they
are
still
there
and
updated.
A
B
B
B
B
Damien
duportal
(jenkins):.
We
saw
that
because
some
users
upon
issues
saying,
hey,,
the
latest
lts
or
weekly
releases-
have
alpine
3
dot,
9
version,,
which
is
word.
and
we
realized,
oh,.
My
some
of
the
images,
for
these
tags
were
rebuilt
and
pushed,
and
some
were
not..
That
was
a
mess,
and
it
was
really
hard..
So
we
decided
to
publish.
B
B
Damien
duportal
(jenkins):.
We
announced
that
in
the
blog
post
last
week,,
if
I
am
not
mistaken,
because
for
people
that
are
checking
carefully
the
digest
of
the
images
for
people
that
are
really
sensitive
on
these
kind
of
changes.,
we
had
to
let
them
know
that
a
change
was
there,
and
they
weren't
being
attacked
by
the
man
in
a
middle
attack..
B
B
B
B
A
C
Mark
waite:,
it
didn't
just
publish
the
3
that
we
then
fixed,
or
the
4
that
we
fixed
right..
We
did
last
3
lts.
and
the
most
recent
weekly
or
2
most
recent..
So
so
there
are
outdated
contain..
There
are
inc,
well
incorrect
container
images
that
are
still
out
there,
and
we're
not
going
to
go
through
the
effort
of
those
older
container
images,,
because
we
don't
support
with
security
fixes.
C
C
C
B
B
B
C
A
A
A
mark
waite:
now,
the
next
subject
to
do
21
mark..
Would
you
like
to
move
that
later
on?,
because
you
have
a
whole
section
about
what
you've
got
here
is
perfect,
this
other
thing..
The
other
thing
is
much
broader
than
this..
I
like
this
one..
Let's
talk
to
this
one.,
so
we
have
just
started
with
stefan
working
on
updating
the
jiddika
21
version
on
ci
jenkins,
I/o,.
A
B
A
Bruno
verachten:
cool.
bruno
verachten:
thank
you.,
and
then
I
had
a
surprise
last
week,
because
it
looks
like
jenkins.
2,,
4,,
1
9
is
already
working
with
gdk
21
it,
except
when
you're,
using
a
jdk,
21
on
your
machine..
Of
course,
I
had
a
good
look
at
all
the
pr.
and
all
the
issues,
and
so
on.
I
should
have
known.,
but
just
as
a
end
user,
I
got
surprised..
I
didn't
have
to
use
the
minus
enable.
A
C
C
C
A
Bruno
verachten:
yeah,,
it
perfectly
makes
sense..
I
was
just
turning
the
problem,
the
wrong
way.,
that's
okay.,
and
then
we
so
change
into
the
packaging
repo,,
because
jenkins,
core
now,
checks,.
If
you're
running
in
a
supported
version
of
jdk,-
and
we
also
had
a
couple
of
script,
2,
in
fact,
script,,
one
for
system
d
and
one
for
debian.,
I
guess.
A
A
A
B
Damien
duportal
(jenkins):
92.,
so
we
were
lying
to
ourselves
and
to
the
users.
If
you
use
the
jenkins
agents
only
agents.
that
are
tagged
with
windows.
lts.
2,019.
in
fact,,
you
have
windows.
1809.
technically,.
These
are
binary,
compatible,
and
you
have
the
same
distribution
channels..
But
on
one
case
you
have
the
lts
distribution,
and
on
one
case.
B
B
B
Damien
duportal
(jenkins):.
So
that's
why
a
lot
of
projects
are
sticking
to
8,
18
9..
So
the
goal
is
to
fix
that..
So
we
don't
lie
to
user..
We
already
are
publishing
explicit,
1809,
tags.
and
now
the
breaking
chain
will
be
for
some
one
sticking
to
windows.
server.
Lts
2,019,,
the
content
of
the
inbound
agent
and
the
sesh
agent
will
change.
B
B
C
Mark
waite:
well,,
it's
it's
the
same.,
it's
the
same
kind
of
scenario
as
what
we
just
saw
with
debian,
that
upgrade
from
debian
11
to
debian
12
on
the
controller.
right?
we've
got
a
user
reporting,
hey?.
I
was
running
something
that
had
behaved.
One
way
on
debian
11.,
you
switch
to
debian
12.,
it's
it
behaves
differently
and
says,
yep,,
sometimes
operating
systems
do
that.
B
Damien
duportal
(jenkins):
absolutely.,
but
we
have
to
be
careful
on
advertising
that
as
a
breaking
change
within
the
change
log
with
the
explanation,,
because
the
ideas
for
user
facing
that
issue.,
the
question
is,.
Is
it
something
I
did
recently?
or
is
it
something
that
broke
on
the
upstream,
and
the
answer?
Is,?
Something
breaking
happened
on
the
upstream,
and
you
have
to
fix
it
now,
or
pin
to
the
old
version.
B
A
A
Bruno
verachten:
jenkins
control,
docker
image
change
log.
It
looks
like
it
is
in
the
official
jenkins
core
change.
Log,,
you
know,,
you
modified
thanks
to
the
user
feedback,
your
change
log
in
the
version
in
the
repo,
you
know,,
but
it
was
already
part
of
the
official
change
log..
So
had
you
looked
at
the
official
changelog,,
it
could
have
had
a
hint
that
something
was.
A
B
B
B
Damien
duportal
(jenkins):
this,
and
the
docker
compose
file
defined
as
the
same
goal
as
the
bake
file..
We
we
haven't,
studied
the
new
docker
compose
feature
that
allows
also
listing
all
the
tags
for
each
image,,
which
is
the
initial
reason
why
we
looked
into
docker
bake..
That
would
allow
us
to
remove.
B
B
Damien
duportal
(jenkins):
for
the
end
users,
damien
duportal,
(jenkins):,
absolutely
no
change.
Visible..
We
didn't
break
anything,
as
far
as
we
can
tell,.
We
might,,
I
hope
not,,
but
the
good
news
is
that
it
allowed
irvine
to
quickly
ship
windows.
2,022
supports
during
the
summer,
and
catch
the
windows.
error!.
We
see
here,
another.,
let's
say,,
ongoing
topic!
here
is.
B
Damien
duportal
(jenkins):,
then
we
are
going
to,
and
we
are
searching
on
test
issues..
But
now
I'm
not
the
only
one
person
to
have
a
deep
knowledge
of
each
of
these
elements.
survey
is
as
well,.
So
that
allows
us
to
improve
the
quality
of
code
here
and
merge
should
be,.
We
should
be
able
to
do
it
during
the
during
before
end
of
year..
A
B
Damien
duportal
(jenkins):,
I
believe
I
don't
know
the
complexity
of
building
our
own
git.,
I'm
not
afraid
of
that,,
and
I
will
prefer
having
this
so
weeks.
Finally,
control
to
get,,
because
git
has
a
lot
of
easy
bindings..
I
did
it
for
years
with
linux
from
scratch.,
so
I'm
not
afraid
of
doing
this,
for
with
ubuntu
debian.
A
B
A
damien,
duportal
(jenkins):,
except
for
ubuntu,.
We
have
one
of
the
git
maintainer,
maintaining
a
ppa,,
but
no
guarantee
on
the
fact
that
it
works
with
the
packages
you
have
on
your
operating
system..
We
use
it
on
the
infrastructure,,
but
we
don't
want
to
use
it
at
all.
On
user
facing
images
like
this
on
the
infrastructure
when
there
is
a
github.
B
Damien
duportal
(jenkins):
updates,.
I
personally
check
the
integrity
of
the
source
code
used
for
the
ppa
before
verifying
the
code..
So
I'm
sure
that
someone
is
not
doing
word
thing
on
the
ppa.
and
we
accept
the
risk
of
breaking
it
on
the
agent
because
we
can
test
it
really
soon
before
deploying
to
production.
A
C
C
C
C
C
C
C
Mark
waite:,
but
I've
got
enterprise
customers
who,
who
can't
move
that
quickly,
and
so
I'll,
probably
be
bringing
a
proposal
to
make
that
thing
be
java
17
as
the
required
minimum
version,,
not
joining
java
21,
and
then
propose
a
pattern
for
future
releases.
where,.
Given
that
java
does
a
new
lts.
every
2
years..
If
we
get
jenkins
on
the
cadence
of
supporting
the
the
lts.
java.
C
Mark
waite:,
we
then
can
say,
and
6
months,
later,
or
9
months
later
or
12
months,
later,
that
becomes
the
new
minimum
jenkins
version,
and
we
get
there..
But
not
this
time.,
that's
the
that's
the
current
thing.,
but
I've
gotta
get
some
pictures
together
to
show
java
releases
jenkins
releases
and
how
they
overlap
with
each
other.
C
C
A
Bruno
verachten:,
I
don't
have
concerns..
I
was
just
wondering
why
the
current
status
status
of
jenkins
support
for
jitica
21,,
not
the
official
one,,
but
I
mean,.
I
know
some
people
make
some
experiments..
I
think.
basel,
run
the
bomb.
build
with
jedi
kate.
21.
some
parts
of
the
infra
already
supplied.
21.,
but
I
don't
think
it's
running
on
tiddlykat
21.
A
A
Mark
waite:
a
chart
somewhere,
or
something
that
say,
oh,.
We
are
10%,
20%,
something
or
not
at
all.,
it's
not
yet..
I
think
I
think
basel
is
actually
tracking
a
sheet
somewhere
that
that
records
what
fraction
of
the
plugins
have
already
tested,
with,
or
already
actively
testing
on
ci.
jenkins,
I/o.
with
java
21..
I
know.
C
C
C
A
A
bruno
verachten:
now,,
if
you
don't
mind,,
we'll
switch
to
new
topics,,
because
I'm
not
so
sure
we'll
be
able
to
treat
the
recent
changes
and
already
told
about
the
most
breaking
chain
that
happened,
lately,,
which
is
move
to
bookworm..
That's
why
you
have..
The
title
is
bookworm
made
it
first
victim,
anyhow.,
so,
damien,.
I
think
here's,
the
one
that,
added
these
topics.
am.
I
right?.
C
Mark
waite:
descriptions
on
the
docker
hub
repositories
as
displayed
to
you.
To.
readers
are
outdated.,
they
aren't
perfectly
maintained.
and
the
idea
was,
hey,.
We
should
consider
updating
those
short
descriptions
to
declare
that
these
things
are
deprecated.
oh,.
I
know
this
was
alex
brandus..
I
know
where
this
came.
From..
Sorry,
it's
not
even
me..
Alex.
brandis
is
the
one
who
detected
this.
we're
using
these
old
terms.
Deprecated
terminology
slave
instead
of
the
correct
term,
agent.
A
Bruno
verachten:
yeah,
that
would
help.
but
do.
hub
is
already
showing
that
it
hasn't
been
updated
in
5
years
or
so.
correct.,
so
there,.
There
are
good
hints
that
it's
definitely,,
but
sometimes
it's
not
enough.
right?
right..
Every
chance
we
get
to
hint
to
people
is
is
one
more
chance
that
they'll
heed
the
hint.
A
Mark
waite:,
you're
right,
and
the
next
one,
that's
funny,,
because
I
think
that's
something.
We
talked
about
a
few
meetings
ago,
and
it's
not
me
that
work
that
wrote
that
down
windows,
arm
images
might
be
possible
windows,
on.,
oh,,
yeah,,
that's
you.,
that's
funny.!
You
happen
to
have
a
windows
arm,
machine,
right?.
I
do
right..
I
have
a
windows
arm
machine
because
microsoft
was
selling
them,
and-
and
I
was
interested
so.,
but
I
think
the
answer
right
now:
is,
no,,
it's
not.