►
From YouTube: 2022 05 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
Welcome
everyone.
This
is
jenkins
platform
special
interest
group.
It's
the
6th
of
may
2022
great
to
have
everyone
here:
topics
I've
got
open
action
items
require
java,
11,
java
or
so
agenda
items
java,
17
support,
docker
agent
support
edition's
under
consideration
and
damien
has
some
information
to
share
there
exit
and
restart
life
cycle
change
that
basel
since
you're.
A
Here
I
wanted
to
do
a
brief
question
and
answer
session
there
just
to
be
sure,
because
I
had
put
this
on
the
list
and
I'm
not
sure
that
what
I've
said
here
actually
is
needed,
given
how
long
we've
been
running
with
this.
So
those
were
the
topics
that
I
had.
Are
there
any
other
topics
that
should
be
added
to
the
agenda.
A
A
We
had
a
pull
request
submitted
to
jenkins.io
that
attempted
it,
but
had
a
number
of
factual
errors
in
it.
We
closed
that
finally
and
agreed
with
the
maintainers
of
the
plug-in
installation
manager
that
we
would
rather
put
the
documentation
on
the
github
site
in
detail
and
then
have
a
pointer
from
jenkins.io
to
the
github
repository,
so
that
maintenance
will
naturally
follow
with
documentation,
but
no
change
and
no
change
expected
because
I
just
don't
have
time
to
do
that.
A
A
A
A
D
Yeah
yeah,
what
that
implies.
Is
that
I'll
be
changing
the
banner
the
admin
monitor
in
the
weekly
branch?
That
is
the
master
branch
shortly
after
we
branch
for
the
next
lts
to
include
a
sooner
date
than
september,
since
those
users
of
the
weekly
line
will
need
to
be
notified,
that
we'll
be
dropping
support
for
java
8
sooner
for
their
line
than
we
would
for
the
lts
lane.
A
D
I
mean
we
still
have
to
resolve
the
remoting
issue
with
with
java,
with
java
11.
there's
still
one
one
blocker,
which
one
is
that.
D
D
A
Right,
okay,
I
see
what
you're
saying
here.
Is
this
one
says?
Oh
no,
but
then
karsten
says
he
did
try
websocket
and
still
saw
an
error.
A
A
B
But
I
I
I
don't
think
we
should
block
it
or
not.
It
does
have
quite
a
few
people
watching
it,
but
it's
not
terribly
active
as
it's
been
open
for
three
years,
but
I
guess
people
have
had
the
work
around
of
downgrading.
C
C
B
I
think
this,
so
this
area
is
especially
looking
at.
I
looked
through
the
code
of
this
didn't
understand
too
much
of
it,
but
the
code
is
a
specific
check
in
the
in
the
remote
ping
protocol,
whatever
it's
called
jlp
connect,
four
or
whatever
the
protocol
is
as
a
specific
condition
that
is
added.
There
is
a
check
saying
that
it
should
not
be
that
that
should
not
be
in
the
state,
and
I
don't
think
websocket
has
that
same.
The
websocket
protocol
is
different.
A
Okay,
so
made
the
request
feels
like
a
viable
request.
Let's
keep
it
on
our
list
and
and
keep
the
the
worry
we'll
go.
We'll
proceed
forward
I'll
submit
some
proposed
dates
for
the
transition
into
the
jeb.
That
proposal
probably
won't
come
until
next
week.
Today
is
kind
of
busy
for
me,
so
I
don't
think
I'm
going
to
have
capacity
to
do
it
today
that
work
for
everybody
else,
if
I'll
submit
it
and
make
reference
to
tim
to
you
to
basel
for
a
review
of
the
proposed
change
in
the
jet.
A
D
There
hasn't
really
been
an
update
since
last
time,
but
the
tooling
has
already
been
done
in
plug-in,
parent-pawn
4.40
so
and
we
are
testing
the
bill
of
materials
set
of
plugins
with
java
17.
As
of
a
recent
change,
so
we
we
should
be
fairly
confident
that
plug-ins
are
in
decent
shape.
There
still
are
some
interesting
tasks
that
are
open
in
phase
one
to
get
core
fully
supporting
java
17.
D
there's
one
very
interesting
issue
that
alex
discovered
with
jelly.
That
could
be
a
fun
bug
to
solve,
which
I've
included
in
that
epic,
but
there's
there's
basically
a
a
type,
a
type
resolution
subtlety
with
how
jelly
resolves
types
that
affect
certain
uses
of
jelly,
including
one
of
our
build
trend
pages,
and
I
actually
added
a
test
to
stapler
that
fails
on
java
17
but
passes
on
earlier
versions,
and
that
could
be
a
very
good
starting
point
for
someone
who
wants
to
work
on
that.
D
D
That's
right:
it's
only
it's
only
jelly
views
but
not
groovy
views
that
are
affected,
which
is
pretty
interesting.
So
that's
that's
one
of
the
core
issues.
That
remains,
I
mean
that's,
probably
the
biggest
open
issue
that
I
can
think
of.
I'm
I'm
not
seeing
the
epic
in
front
of
me
right
now,
but
I
think
that's
really
the
one
of
the
most
interesting
things
we've
discovered
so
far.
Yeah
I
mean
most
of
this
other
stuff
is
fairly
fairly
minor.
Like
you
know,
the
file
leak
detector
socket
support.
D
You
know
these
are
very
small
edge
cases
but
yeah
the
the
programming.
D
Yeah,
that's
that's
the
that's
the
one
that
I
was
talking
about,
so
I
mean
this
one.
If,
if
anyone
feels
like
tackling
this,
I've
got
a
unit
test
in
stapler,
you
can
execute
the
unit
test
in
half
a
second,
but
the
difficult
part
of
this
is
maybe
the
five
minutes
or
five
hours
or
five
days
or
whatever
it
takes
to
come
up
with
the
solution
to
this,
which
is
going
to
involve
kind
of
digging
into
the
depths
of
jelly
and
how
it
evaluates
expressions.
B
A
Well,
and
and
truly
java
java
17
support
we're
in
a
good.
For
me,
it
feels
like
we're
in
a
good
state
right,
the
tooling
improvements
and
the
amount
of
automated
testing
the
growth
of
plug-in
testing
that
many
many
plug-ins
are
now
testing
with
java
17,
in
addition
to
java,
11
and
8,
and
when
we
drop
support
for
java
8,
we
can
reduce
our
spend
on
infra
again
by
not
testing
plug-ins
with
java
8
anymore.
So
so
there's
a
win
coming
soon.
D
So
what
I
imagine
we'll
want
to
do
is
encourage
plug-in
maintainers
to
do
a
sweep
and
basically
remove
eight
and
add
seventeen,
and
I
mean
we
could
we
could
have
them.
Do
the
sweep
now
and
just
add
17
so
they'll.
They
could
have
three
right
now,
but
I
don't
really
see
a
big
push.
I
don't
see
a
big
reason
to
do
that,
since
we
we
feel
covered
enough
by
the
bill
of
materials
testing,
at
least
for
the
top
100
plug-ins
right.
There's
nothing
stopping
anyone
from
adding.
D
So
in
fact,
for
all
of
my
plug-ins
I've
done
that
just
to
see
what
happens,
but
we
by
september
I
think
we'd
want
to
we'd
want
to
give
the
very
clear
message
that
you
know
please
go
and
remove
eight
at
17,
and
we
want
you
to
do
this
now,
rather
than
to
wait.
A
B
D
I've
already
I've
already
I've
already
fixed
that
in
the
pull
request
that
drops
support
for
java
8..
If
you
look
at
that
pull
request,
they
did
a
couple
of
interesting
things.
I
first
of
all
I
fixed
that
to
demonstrate
that
requiring
java
11
will
allow
us
to
fix
that,
and
also
in
one
particular
source
file.
I
added
a
java
11
only
api
usage
to
also
demonstrate
that
we
can
now
do
that
which
we
couldn't
before,
so
that
there's
there's
those
two
parts
of
that
pull
request
are
just
demonstrating
that
well
and.
D
B
D
Bundle,
I
think,
yeah
whatever
it's
called,
there's
there's
already
a
class
for
this
in
java
8
which
we're
not
using
and
but
if
we
were
using
it,
it
just
so
happens
that
they've
changed
the
behavior
of
this
class
in
java,
9
plus,
so
that
it
so
the
behavior
of
it
in
java
8
is
to
only
open
the
properties
files
in
iso
88591
encoding
they've
changed
the
behavior
of
this
class
in
java
9,
plus
to
to
try
it
open
with
utf-8
and
fall
back
to
iso
8591.
D
Otherwise.
So
if
we
were
using
this
api,
we
would
just
get
this
improvement
for
free,
but
unfortunately
stapler
isn't
using
it.
It's
it's
rolling
its
own
implementation
of
this.
So
please.
B
I'm
just
going
to
say
there
was
an
effort
a
few
years
ago
to
introduce
xml
based
property
files
because
that
couldn't
that
could
add
utf-8,
because
some
contributors
got
so
frustrated
trying
to
edit
these
files.
But
other
contributors
didn't
want
to
have
to
use
xml,
so
it
didn't
get
accepted,
but
yeah.
This
would
be
huge,
there's.
So
many
encoding
problems.
D
D
This
utf-8
support
whenever
we
switch
our
runtime
to
java
9
or
later
so,
and
to
me
this
is
just
some
some
cleanup,
a
stapler,
the
fact
that
it's
it
it's
using
its
own
implementation
rather
than
the
standard
java
api
for
this.
A
A
B
E
A
Well,
actually-
and
I
think
we
actually
do
have
a
reason
to
keep
keep
the
two
images,
because
windows
has
the
lovely
behavior
with
docker
images
that
you
must
run
an
exactly
matching
kernel,
and
so,
if,
if
we're
going
to
continue
providing
ltsc
2019
images,
we've
got
to
have
a
place
to
build
them.
You
have
low
level
compatibility.
A
E
Yes,
but
you
can
execute
container
2019
on
the
kernel
2022..
I
can
you
I
I
had
understood.
You
cannot
just
tried
yesterday
on
the
check,
so,
okay,
but
okay,
given
what
you
said,
we
will
have
to
pay
more
attention
and
we
will
go
the
road
having
both
at
the
same
time
first
or
having
a
path
to
tests.
E
But
that's
a
good
thing
that
we
share
that
because
that
might
go
easily
for
that
pull
request.
However,
that
might
have
issues
on
the
release
process,
because
the
jenkins
weekly
or
core
process
package
using
a
windows
container.
So
we
have
to
be
careful
about
that
part,
but
I
want
that
part
is
managed
by
aka,
so
that
should
go
easily,
but
we
have
great.
B
I've
seen
I've
seen
a
link
in
the
chat
detailing
what
mark
it's
been
referring
to.
There's
some
they've
done
a
bunch
of
work
on
windows,
11
and
windows
server
2022,
to
make
this
a
bit
better,
because
some
scenarios
may
work
across
versions
now.
But
oh.
E
B
Yeah,
I
don't
fully
understand
it
for
a
quick
read.
You
need
to
read
it
but
understand
it.
A
A
All
right
next
topic,
this
one
was:
I
carried
this
over
from
last
meeting
because
we
hadn't
had
a
chance
to
talk
to
it.
There
was
a
change
made
in
2.344,
so
that's
now
three
weeks
ago
or
two
two
weeks
ago
that
changed
the
the
life
cycle
to
use
a
simpler
life
cycle
for
inside
docker
images
right.
So,
instead
of
basel,
if
I
remember
correctly,
instead
of
some
complicated
java
code
inside
jenkins,
that
was
doing
the
exit
and
attempt
to
restart
it.
Just
now
stops
and
lets
docker
restart
it
did.
I
describe
that
correctly.
A
Yes,
that's
right,
and
so
I
was
worried
when,
when
it
was
initially
proposed,
oh,
this
is
going
to
be
a
total
disaster.
Somebody's
going
to
be
surprised,
they're
going
to
be
very
angry
at
this
restart
behavior,
but
we've
had
no
reports,
no
noise
from
anybody
that
I've
heard
about
about
this.
This
new,
this
change
of
behavior.
So
I'm
not
sure
we
need
a
blog
post
or
any
documentation
changes.
I
didn't
detect
any
any
guidance
from.
D
D
You
know
maybe
not
for
local
development,
but
I
think
people
who
are
using
docker
compose
or
ansible
or
some
other
devops
tool
to
set
up
their
images.
They
might
have
been
using
that
option
already.
So
you
know,
maybe
that
change
just
wouldn't
affect
a
lot
of
people,
because
they
were
already
using
the
option.
D
F
I
may
have
totally
misunderstood
the
question,
but
since
I
upgraded
to
2.346
as
soon
as
I
install
new
plugins
and
click
on
restart
when
it's
installed,
my
docker
container
just
exits
and
never
restarts
so
it
may
not
link
at
all,
but
I'm
experiencing
some
issues
with
that.
These
days,
interesting.
D
F
D
F
D
For
the
yeah,
I
think,
that's
probably
the
main
use
case
where
people
would
hit.
This
is
local
development
right
when
you're,
just
spinning
up
jenkins
with
you
know,
docker
run
on
your
local
machine
to
try
something
out.
I
think
that's
the
scenario
where
people
would
forget
to
add
this
flag
and
be
affected
by
this,
the
most
rather
than,
for
example,
the
production
use
case,
where
they're,
probably
using
a
tool
like
docker
compose
or
some
some
other
tool
that
they
would
configure
and
check
every
setting
make
sure
every
setting
is
is
set
correctly.
D
You
know
that's
something
you
probably
wouldn't
do
just
on
a
local
machine
to
fire
something
up
quickly.
So,
okay,
yeah,
I'm
not
sure
how
we
advertise
that
better.
You
know
maybe
other
than
putting
an
upgrade
guide
entry.
F
Yep,
I
was
just
thinking
of
chicas.
If
you
can
mark,
and
maybe
we
should
tell
them
that
they
should
change
the
configuration
if
they
are
upgrading
the
latest
version
to
make
the
screenshots,
for
example,.
A
E
Insight,
thank
you
good
question.
Wouldn't
that
be
worth
a
minor
but
quick
blog
post
just
restating
what
basil
just
described
like
hello.
If
you
are
doing
developments
or
tests,
then,
if
the
contour
exits,
that's
the
standard
docker
feature
as
usual
points
to
docker
documentation
that
mention
the
restart
flag
and
then
say
we
have
updated
the
documentation
for
jenkins.
We
recommend
you
to
use
restart,
always
all
the
time,
so
your
container
will
restart.
F
D
Yeah,
there's
still
one
there's
still
one
more
bug
we
have
with
the
life
cycle,
which
is
that
on
m1
max
the
restart
after
plug-in
upgrade
doesn't
work
on
m1
and
I
actually
found
the
root
cause
of
that
bug,
but
I
just
haven't
found
any
time
to
fix
it.
It's
not
it's
not
a
terribly
complicated.
It's
a
medium
difficulty
fix
not
not
very
difficult,
but
also
not
very
simple,
but
I
think
once
once
that
bug
gets
fixed,
we'll
finally,
we'll
finally
be
over
all
of
these
exit
and
restart
issues.
D
For
the
m1
issue,
yeah
the
the
way
that
we're
invoking
the
system
called
from
java
is
encoding.
The
arguments
incorrectly,
basically.
B
A
B
I
tried
to
yeah,
I
got
very
lost.
I
spent
quite
a
while
debugging
it
bezel
did
manage
to
get
to
the
bottom
of
it,
but
the
main
problem
I
had
with
it
was
during
acceptance
test
harness
and
the
vincent's
re-implemented
the
restart
logic
in
ath
about
a
month
or
so
ago
to
use
exa
and
have
ath
manage
the
process.
So
it's
rather
than
relying
on
jenkins,
restarting
ath
managers
restarting
now
and
since
he
fixed
that
it
doesn't
really
affect
me
as
much.
A
B
I
was
working
around
it
by
grabbing
the
pro
from
grabbing
from
the
logs
the
process,
copying
it
out,
reformatting
it
and
then
starting
it
myself
manually,
which
would
allow
the
ts
to
continue.
That
was
my
work
around
which
did
work.
It
was
just
painful,
but
vincent
semi
recently
has
fixed
it.
So
I
don't
have
to
do
that
anymore.
D
Excellent
all
right,
the
ironic
part
about
this
bug
is,
I
found
a
way
to.
I
found
a
way
to
fix
it
easily
with
jnr,
which
I
had
almost
the
same
week.
Ripped
out
of
core
so
to
fix
it
with
jna
is,
is
slightly
harder
because
it
doesn't
give
you
any
convenient
rappers
to
encode
these
arguments.
You've
got
to
do
it
yourself,
and
I
did
a
google
search
on
how
to
do
this
with
jna
and
the
only
results
I
found
in
the
google
search
were
the
incorrect
logic
in
jenkins.