►
From YouTube: 2023 01 20 Docs Office Hours
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
this
is
Jenkins
documentation,
office
hours.
It
is
the
20th
of
February
Asia
time,
thanks
for
being
here,
topics
for
today
action
items,
Debian,
12
and
jdk
17.
reminder
on
handling
regressions,
detached
plug-in
documentation,
an
update
to
describe
that
and
then
pull
requests
of
note
and
Gavin.
Mogan
has
added
one
very
good.
Okay,.
B
A
Get
everything
else
done,
so
we
can
get
to
pull
requests
of
note
very
quickly.
Okay,
all
right!
So,
first
item,
no
action,
no
open,
Action
items
win
second
item
Debian
12
bookworm,
so
the
next
release
of
Debian
is
planned
for
release
in
2023
likely
either
April
or
May
or
June
right.
So
they
freeze
in
March
and
final
freeze
is
expected,
probably
a
month
or
two
later.
Okay,.
C
A
A
C
A
A
In
fact,
many
many
places
are
using,
so
that's
the
next
one
containers
for
containers
we're
using.
We
use
Eclipse
tamarin.
A
C
A
Challenge
is
for
people
who
install
it
directly
with
a
Linux
package
for
them.
They'll
see
they
won't
be
able
to
use
the
instructions
that
say,
do
job
11,
because
job
11
won't
be
available
right,
and
so
what
we'll
do
is
we
will
just
describe
Java
17
and
if
they
want
to
use
Java
11,
they
can
but
we'll
describe
Java
17..
Now,
there's
an
additional
Twist
on
this
red
hat
has
proposed
Oliver
ganja
of
red
hat
and
one
of
his
colleagues
have
proposed
to
add
a
universal
base,
image
nine.
C
A
So
Oliver
ganja
here
has
has
proposed
that
they'll
create
they
would,
we
would
add,
a
Docker
container
using
ubi9.
We've
already
got
one
that
uses
ubi8,
and
so
it
makes
sense
and
the
question
to
to
them
was
they
proposed
initially
Java
11
and
our
question
back
was:
could
we
please
just
do
Java
17,
and
that
way
this
is
already
moving
towards
the
notion.
Let's
do
Java
17
rather
than
Java
11.
right.
C
A
A
C
A
Next
topic
was
handling
regressions
on
the
jenkins.io
site,
so
we've
had
some
episodes
in
the
past,
where
we
we
made
some
change
to
jenkins.io,
to
improve
the
look
and
feel
or
to
improve
some
part
of
the
site
and
inadvertently
that
change
also
caused
a
loss
of
functionality.
So
what
we're
doing
is
discussing
and
proposing
a
formal?
How
do
we
handle
regressions
policy
as
one
example
of
a
regression?
We
had
this
one
where
it's
kind
of
embarrassing.
A
B
A
A
A
A
It
was
upgrading
from
an
older
version
of
the
bootstrap
JavaScript
library
and
replacing
an
unmaintained
library
with
a
maintained
library
that
does
some
important
functions.
This
popper
JS,
Library,
okay,
so
the
the
upgrade
was
valuable.
It
really
was
the
change
that
made.
This
was
valuable
and
truly
useful,
but
it
had
this
undesired
side
effect
right.
What
jabinic
was
able
to
do,
though,
was
he
was
able
to
fix
the
the
pro
the
root
problem
and
not
have
to
revert
the
change.
A
So
so
the
idea
is
significant.
Regressions
that
aren't
resolved
promptly,
we
revert
them
minor
regressions
will
take,
will
allow
more
time
now.
What
we've
done
is.
We've
added
two
issue
labels,
one
for
regression
and
one
for
major
regression.
That
way
if
something
is
flagged
as
a
regression,
we
know
we
need
to
take
action
on
this
and
the
idea
was
discuss
it
any
concern
from
umag
about
that
kind
of
a
policy.
Well,.
A
C
C
A
C
A
C
A
C
A
Well
and
and
the
human
element
is
there
no
matter
what
there
are
all
sorts
of
examples
in
the
Jenkins
documentation
of
things
that
have
have
become
outdated
and
are
no
longer
relevant
because
the
world
has
moved
around
it
right
it
was.
It
may
have
been
exactly
perfect
when
it
was
first
written,
but
nowadays
it's
no
longer
accurate
and
and
therefore
so,
for
instance,
the
Linux
install
instructions
talk
about
red
hat
and
Centos,
but
sentos
as
an
operating
system.
A
Now
that
Centos
Centos
7
is
the
last
viable
operating
system
of
Centos
and
it
will
end
its
life
in
2024.
So
there's
not
a
lot
of
value
to
us
actually
talking
about
Centos,
seven
right:
it's
yes,
it
exists.
No,
we
really
don't
want
it.
So
those
kinds
of
things
they
become
dated
or
not
less
less
valuable
as
time
goes
on
exactly
all
right,
so
that
one's
covered.
Anything
else
on
the
regressions
topic
looks.
C
A
A
Okay,
so
this
this
thing
was
split
from
Jenkins
core
many
many
years
ago,
so
it
used
to
be
part
of
Jenkins
core
and
not
even
a
plug-in.
It
was
made
a
plug-in
and
when
it
was
made
a
plug-in
there's
a
risk
that
other
plugins
might
depend
on
the
apis
that
it
had
been
contributing
to
core
and
is
was,
is
no
longer
contributing
to
core,
and
that's
what
this
list
of
implied
dependencies
means,
and
if
you
look
at
the
size
of
the
scroll
bar,
you
can
see
that
it's.
A
For
this
example,
quite
a
large
number
of
plugins
that
have
an
implied
dependency
on
this
particular
this
particular
plugin.
Well,
the
problem
is:
if
someone
wants
to
remove
this
plug-in
from
their
installation
and
they
have
one
or
more
of
these
plugins
already
installed,
they
cannot
remove
this.
If
they
attempt
to
remove
it,
the
removal
will
be
attempted
and
Jenkins
will
then
re-inject
a
copy
of
the
plug-in
back
into
the
system
for
its
own
safety.
Okay,.
C
A
Now
that
concept
of
implied
plugins
is
described
here
and
I
like
the
description,
it's
actually
quite
good
talking
about
what
an
implied
plug-in
an
implied,
plug-in
dependency
means,
but
this
becomes
more
complicated
if
we
instead
take
a
different
plug-in.
That's
now
been
deprecated,
so
this
plugin
called
the
wmi
windows
agents.
Plugin
is
not
just
split,
but
it
was
split
from
Jenkins
core
and
is
now
deprecated,
meaning
users
get
another
message
that
says:
hey
this
thing
is
should
is
deprecated
should
be
removed,
but
then,
when
they
try
to
remove
it,
it
would
tell
them
sorry.
A
A
A
B
A
It's
used
very
widely.
Why
well,
because
it's
dependency
of
blue
ocean
right
and
oh
I,
take
it
back
and
it's
it's
a
dependency
of
pipeline
promotion.
My
mistake
so
pipeline
is
depends
on
it
and
and
so
that
that
challenge
means
everybody
with
pipeline.
Has
this
installed,
therefore,
they
can't
remove
the
jdk,
the
jdk,
the
Oracle
jdk
tool,
without
this
warning
message
that
says:
hey
we're
going
to
give
it
back
to
you
that,
so
this
all
this
complication.
A
All
this
long
story
means
we
think
we
need
to
do
some
do
some
more
documentation
to
describe
it
and
the
first
one
here
on
the
list
is
actually
resolved
in
Jenkins
2.386
and
later
so
we
we
fixed
it
and
the
next
one
we
made
we
may
someday
want
to
resolve
the
others.
Well,
for
instance,
you
might
say:
hey
I
want
to
get
rid
of
subversion.
I
never
use
it.
Well,
if
you
have
any
one
of
those
old
plugins,
you
can't
get
rid
of
subversion.
A
So
that's
the
kind
of
story
for
this
now
really
right.
Now,
it's
mostly
a.
How
do
we
document
this
so
that
we
can
point
people
who
have
a
question
to
this
thing
and
say
Here's
a
long
term,
there's
probably
a
way
in
code
to
make
this
much
better,
but
that'll
have
to
be
seen
any
questions.
Nope
all
right
next
topic,
then,
was
that
let's
get
to
the
fun
part,
all
right,
okay,
so
pull
requests
of
note.
A
B
B
B
A
A
C
A
A
Oh,
oh,
got
it:
okay,
okay!
Here
it
is
the
default
here
if
it
has
a
source
path,
no
Source
path,
good.
Okay,
so
if
we
know
the
location
of
the
pages
source
code,
for
instance,
we
know
it's
an
adoc
file
or
it's
backed
by
some
some
other
a
markdown
file.
Then
this
is
what
appears
with
this
improve
this
page
link.
Okay,
if
we
don't
know
the
source
path
we
can.
We
can
still
have
the
report,
a
problem
link,
because
that
will
let
them
go
to
jenkins.io's
issue
GitHub
issues,
page.
A
A
I,
don't
see
any
difference,
but
for
me
they
look
great
now.
I
want
one
of
the
things
they
did
was
they.
They
changed
the
size
of
these
things,
so,
for
instance,
what
if
we
are
down
here
on
a
on
a
cell
phone
like
this,
that
still
looks
pretty
good
to
me,
yep
and
if
I
get
even
smaller,
it
still
looks
good.
C
B
A
B
C
A
A
B
B
A
B
A
This
is
and
I'm
I'm
quite
impressed
by
vandit
Singh's
work
on
in
the
documentation,
because
vandit
has
accepted,
has
taken
on
quite
challenging
topics
and
done
very
well
with
them
in
this
one
and
updating
section
so,
just
like
we
have
installing
Jenkins.
Yes,
we
noted
that
we
really
need
an
updating,
Jenkins
section
as
well.
The
discussion.
A
When
we
look
at
installing
Jenkins
we're
reminded
that
installing
Jenkins
is
not
just
one
page,
it's
let's
get
it
here.
Installing
Jenkins
is
one
two
three
four
five
six
seven
pages,
eight
pages,
so
eight
distinct
ways
of
doing
the
install
plus
offline
yet
another.
So
so
we've
got
eight
or
nine,
depending
how
you
count
them.
Ways
to
do
installation
and
upgrade
is
different
in
each
of
them
right
so
so
upgrade
is,
is
likely
to
be
every
bit
as
complicated
as
initial
install.
So
let's
take
a
look
at
the
the
Prototype
deployment.
A
Okay,
so
documentation
and
it
intentionally
is
not
in
the
initial
table
of
contents
in
the
at
the
top
level
menu.
Here's
installing
and
updating
is
here.
Okay,
so
first,
let's
remind
ourselves
which
things
are
here
so
Docker,
kubernetes,
Linux,
Mac,
Windows
other
and
War
Linux,
Mac
Windows
other,
so
we're
missing,
docker,
okay.
But
let's
look
at
at
Linux
at
least
and
see
what
what
it
tells
us
here.
A
A
Oh,
except
that
will
work
okay,
good,
there's
a
reason
we
read:
Man
pages.
Okay,
so
here
service
runs
a
system
five
in
its
script,
in
as
predictable
environment
as
possible.
So
the
problem
is
Jenkins
know
you'll
no
longer
uses
system,
five
in
it
right.
We
use
systemd
now,
and
so
it
needs
to
use
system
control
rather
than
than
service.
C
A
Okay,
so
see
it
was.
It
was
service.
A
It's
for
all
variants
of
Linux,
so
the
Ubuntu
2020
2204.
A
B
A
C
A
A
A
Replace
with
a
link
to
the
backup
page,
because
there
there
are
many
different
ways
to
perform
a
backup
and
they
depend
on
the
environment.
A
Not
a
tar
file
right
right,
they're,
just
they're
faster,
likewise
with
open,
Susie,
15.4.
A
Or
is
it
that
oh
no,
no
I,
take
it
back?
It's
not
btrfs
and
CFS.
Likewise,
Open
studio,
15
4
with
btrfs,
it's
open
Susie
that
does
better
file
system
ZFS
from
the
BSD
people
is,
is
on
Ubuntu.
A
B
B
C
Seems
reasonable
should
we
does
that
chapter
have
verification,
should
we
say
back
up
and
verify
or.
C
A
B
C
A
B
A
B
A
B
D
A
A
A
A
A
A
Okay,
so
Meg,
my
apologies,
major
major
changes
here
and
I
think
this
will
best
be
done
by
by
me
or
somebody
else
going
through
and
reworking
this
pull
request.
Yes,.
B
A
A
B
B
B
A
B
B
A
Okay,
the
next
one.
This
is
a
fun
one,
because
you'll
recognize
it
from
previous
experience,
update
the
controller
with
apt-get
install
update
operations
center
with
some
other
command,
and
so
the
answer
here
is
Jenkins
does
not
have
anything
called
Operation
Center.
A
A
A
B
D
D
A
B
B
B
A
B
C
C
A
B
C
C
A
B
A
A
Did
yes,
40
plus
minutes
of
review
of
the
pull
request
in
the
office
hours?
Great
all
right
thanks.
C
C
A
C
C
A
And
in
order
to
do
the
install,
it
will
take
much
more
than
two
minutes
to
do.
The
install
right,
I
mean
I,
love,
I,
love
that
they
did
it
light.
Httpd
is
a
really
nice
reverse
proxy,
and
so
just
like
nginx
and
Squid
and
Apache
we've
got
one
more
way
to
do:
reverse,
proxying,
and-
and
so
it's
it's
very
nice
that
they
they
did
the
writing.
But
this
particular
example.