►
From YouTube: 2022 02 25 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
it's
the
jenkins
platform
special
interest
group.
It's
the
25th
of
february
2022.
topics
for
today
include
open
action
items
require
java,
11
or
newer
for
jenkins
core
linux
operating
system
support
policy,
the
switch
from
system
5
in
it
to
system
d
in
jenkins,
linux,
linux,
packaging,
and
we
won't
cover
exit
lifecycle
change.
We
need
to
carry
that.
A
One
forward
need
some
discussion
with
basel
and
with
tim
jacom
before
we
have
more
to
talk
about
any
other
topics
that
need
to
be
on
today's
agenda,
not
that
I
know
all
right,
then,
let's
go
ahead,
so
I
still
have
one
open
action
item:
plugin,
installation
manager,
docs.
We
have
a
pull
request
that
we
closed,
that
was
deep
and
covering,
but
filled
with
a
number
of
mistakes.
A
The
action
item
we
decided
in
doc's
office
hours
was
we'll
describe
a
simple
use
case
on
jenkins
on
www.jenkins.io
and
the
more
detailed
cases
in
the
plug-in
installation
manager
tool
repository
still
open
there.
That
will
need
some
work,
java,
11
or
newer
requirement
for
jenkins
core,
but
jenkins
enhancement
proposal
has
been
merged.
A
It
does
not
yet
have
a
timeline,
so
the
the
timeline
in
order
to
determine
it.
We've
got
help
from
basel
crow
he'll
be
doing
some
more
detailed
checks
and
looking
for
problems
or
issues
that
might
be
might
be
getting
in
our
way
tim
jacom
asked
if
we
could
fit
that
into
a
upcoming
weekly
very
soon,
with
the
intent
that
we
would
release
it
in
june,
and
I've
asked
for
an
additional
two
weeks
to
do
deeper
evaluation.
A
A
Others,
I'm
less
concerned
about
there's
work
that
must
be
done,
but
he's
worried
that
this
one
is
a
real
blocker
as
a
bug,
so
the
the
one
you're
pointing
at
correct.
Yes,
this
five
nine
nine
one
zero.
This
one
is
he's
worried
that
this
looks
very
serious
and
we
haven't
done
enough
nearly
enough
investigation
yet
to
understand.
Is
it
a
real
problem
or
not?
A
A
A
So
they're,
not
all
yes,
we
must
fix
them,
but
there
are
some
that
that
have
that
need
to
be
looked
at,
and
that's
then
there's
some
old
ones
in
this
epic
that
we
had
where
this
epic
mostly
contains
things
that
are
resolved
because
it
was
used
for
two
years
ago
when
we
did
java
11.,
but
there
are
still
some
that
aren't
resolved
here.
That
may
need
to
be
considered
need
thought
any
questions
there
on
the
java,
11
or
newer
approach,
no,
okay,
let's
work
ahead,
and
there
is
a
lot
of
work
ahead
on
that
one.
A
Absolutely
next
was
a
linux
operating
system
support
policy
we
have
had
for
a
year
or
more
a
windows,
support
policy,
because
we
needed
a
way
to
express
which
windows
versions
we
were
testing
in
which
we
were
not
this
linux
support
policy
started
with
that
idea
and
then
basel
stepped
in
and
said
hey.
You
know
what
we
should
describe
this
more
accurately,
based
on
what
we
actually
test.
A
He
has
since
added
many
many
tests
of
the
installers
from
many
different
linux
operating
systems,
and
so
there
is
still
work
to
be
done
on
this
pull
request
in
terms
of
assuring
that
people
agree
with
it.
But
for
me
I
think
it's
very
close
to
describing
what
it
should.
We've
got
three
levels
of
support.
A
A
Then
the
next
hot
topic
is
switching
linux
packages
from
system
5
in
it
to
system
d.
So
this
is
a
change
to
the
internals
of
the
linux
installers
rpm
deb
rpm,
for
both
susie
and
for
for
red
hat,
and
it's
been
proposed
to
include
in
jenkins
2.332.1
lts
march.
9..
A
B
Probably
trying
to
smash
an
open
door,
the
upgrade
part
so
people
that
have
an
existing
installation
using
the
old
methods
or
have
rests
of
that.
If
they
apply
the
new
installer
or
or
I
don't
know
how
to
express
it.
But
they
take
a
newer
generation
of
the
installer.
It
will
not
break.
A
That's
correct,
so
what
what
basel
did
is
he
created
an
upgrade
path
that
takes
their
existing
settings
and
brings
them
into
system
d,
and
it
now
makes
it
actually
quite
a
bit
easier
to
edit
settings,
whereas
before
I
had
to
have
platform
specific
descriptions
of
in
order
to
edit
settings
on
red
hat
I'd
do
this
or
in
order
to
edit
settings
on
debian.
I
do
this
other
thing.
That's
different!
A
It's
really
very,
very
elegant
and
systemd
has
some
some
capabilities
that
are
just
very
attractive,
no
more
use
of
separate
scripts
to
manage
the
start
and
stop
of
jenkins
system
d.
Does
it
directly
systemd
will
automatically
restart
if
there's
a
failure,
so
no
need
to
do
special
configurations
based
on
your
operating
system
in
case
of
crashes
or
failures
it.
It
really
is
an
improvement
it.
This
change
fixed,
like
10,
bugs
and
very
nice
improvement.