►
From YouTube: 2022 03 11 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
it's
jenkins
documentation,
office
hours,
it's
the
11th
of
march
2022,
we're
on
the
asia
documentation
office
hours
time,
thanks
very
much
for
being
here.
Topics
on
the
agenda
news,
installer
switch
from
system
5
to
system
d.
A
She
code
africa,
contributon
a
troubleshooting
section
for
the
user
handbook
and
open
prs
any
other
topics.
Meg.
A
Okay,
so
delighted
wednesday,
we
released
the
latest
lts
and
darren
pope
and
I
did
a
live
stream
today.
90
minute
live
stream.
A
On
the
changes
with
the
key
things
for
the
the
upcoming
ones
are
likely
the
red
hat
red
hat
systemd
update
and
the
debian
slash
systemd
update.
B
A
So
darin
was
a
was,
did,
went
through
it
and
hit
some
bumps,
and
so
he
he
he
noted
the
same
way.
I
did
that
there
are
managing
a
system.
D
based
environment
is
new.
It's
different
right
system,
five
in
it
we're
all
familiar
with
it.
We
looked
in
the
source
code
and
the
the
original
linux
installer
code
was
from
2008.,
so
we've
been
using
for
almost
the
full
life
of
jenkins,
this
other
form
of
init
system,
and
so
this
change
will
probably
bump
into
a
number
of
surprises.
B
Yes,
now
that
you
and
darren
do
these
seem
to
do
these
live
streams
on
every
new
major
release?
Is
there
a
reason
that
we
don't
put
a
link
to
that
like
in
the
change
log
or
something.
A
A
Well,
we
could:
how
about
is
a
different
angle.
We
could
add
a
page
to
community.jenkins.io
with
the
live
stream.
A
A
So
next
topic,
then,
was
linux,
installers,
and
so
we've
got
on
the
switch
from
system.
Five
to
system
d,
we've
had
two
two
bug
reports
coming,
it
came
have
come
in,
neither
was
a
particularly
what
I'd
call
a
a
really
bad
one,
but
one
was
that
they
had
to
do
had
to
explicitly
enable
enable
the
service
after
upgrade.
A
B
B
A
So
one
of
the
things
that
basil
crowe,
who
has
created
it,
who
did
the
development
work
for
it,
is
that
we
need
more
troubleshooting
guidance
and
we
need
a
more
specific
description
of
the
information
that
makes
a
good
bug
report
for
this
type
of
bug
right.
So
this
is
this
needs
more
data
than
other
bug.
Reports
need.
A
A
C
C
A
A
A
A
B
B
B
A
Now,
z,
knob,
I
did
submit
three
project
ideas:
okay
for
them
and
the
three
project
ideas
I
thought
were
reasonable.
They
were
I've
noted
them
somewhere,
but
there
is
one
that
I
did
not
submit
and
I've
I've
double
checked
with
xenab
and
she
says
nope,
please
submit
it
mark
so
I'll,
submit
one
suggesting
that
they'll
that
we'll
put
a
project
manager
on
on
it
and
mentor
that
project
manager
and
have
that
project
manager
then
help
us.
A
B
A
Okay,
so
so
what
she's
done?
This
is
the
troubleshooting
jenkins
section
that
we
had
discussed
earlier
and
what
she's
done
is
she's
added
it
to
the
top
toolbar
and
added
a
new
section
into
the
book
for
troubleshooting
all
right
and
then
moved
two
of
the
pages,
diagnosing
errors
and
obtaining
a
thread
dump
to
the
new
location
good.
So
it's
got
some
content
already
and
now.
A
The
question
is,
I
think,
one
of
the
things
we
need
to
be
sure
of
is:
are
we
okay
with
having
separate
pages
for
each
of
the
troubleshooting
interesting
troubleshooting
categories,
and
I
think
we
are
because
we've
been
using
that
before,
but
let's,
let's
look
at
this
and
then
let's
explore
it
a
little
bit
together
to
see
how
the
navigation
feels
etc.
Okay,.
A
Exactly
yeah,
so
by
by
partitioning
it
that
way.
So
now,
if
we
look
at
the,
where
are
the
environments?
Here's
the
environment,
okay,
so
view
the
deployment
diraj
thanks
for
joining
us,
we're
we're
reviewing
a
the
troubleshooting
section
that
was
just
proposed
by
by
xenob,
okay,
so
troubleshooting
jenkins,
there,
it
is
oh,
I
should
make
the
screen
bigger
so
that
it's
readable,
okay,
so
troubleshooting
jenkins,
right
there,
okay,
so
resolving
issues
you
might
encounter
while
running
jenkins.
A
A
A
A
A
So
this
is
the
old
location
and
it
should
automatically
redirect
us.
It
did
good.
Okay,
all
right.
So
did
you.
I
don't
know
if
you
saw
the
the
flash
there,
I'm
not
sure
that
zoom
carries
the
flash
forward.
What
happens
is,
is
the
page
the
page
will
temporarily
go
to
the
location.
I
gave
doc
book
system
administration,
it
flashes
up
the
url
it's
going
to,
and
then
it
takes
us
there
cool
all
right,
so
that
worked
for
thread
dump
and
the
other
one
was
is
the
other
one.
She
moved,
oh,
diagnosing,
errors.
A
B
An
interesting
suggestion:
okay
and
then
because
what
I'm
thinking
on
the
for
the
index.a
dot
page
for
this
section,
it
would
be
nice
if
that
had
an
introduction,
say
you
know
that
some
you,
I
don't
know
how,
how
literary
we
want
to
be
but
trouble
shooting
is
an
art
and
there's
a
lot
of
things
and
what
we're
the
section
that's
called
diagnosing
errors.
I
might
make
that
be
common
errors
or
something
that's
not.
A
B
You
know
look
at
your
logs
and
they
may
give
you
a
hint
and
if
you
look
at
your
logs
frequently
enough
you'll
see
when
something
is
there
that
isn't
usually
there
and
that
may
be
your
hint
and
then
you
may
need
a
thread
dump
and
why
you
know
a
word
or
two
about
why
a
thread
dump
is
useful
and
then
whatever
we
call
that
section
say
these
are
some
things
that
frequently
happen,
and
this
is,
you
might
look
through
this
to
see.
B
But
just
to
give
you
know
so
it
because
I
like
having
this
in
all
the
little
pieces
for
maintainability
but
troubleshooting
is
such
a
you
know
it's
a
difficult
subject,
because
every
trouble
is
different.
So
I'd
like
something
that
leads
me
into
it
says:
how
are
we
gonna
and
we're
not
gonna
solve
everybody's
problems
with
this
section
at
least
not
now,
right.
C
B
A
B
A
B
B
But
that's
another
thing
with
troubleshooting
is
we
might
end
up
with
links
to
other
docs
that
we
leave
where
there
are
right
some
of
these
other
subjects?
There
might
be
a
trouble.
There
might
be
troubleshooting
information
in
them.
Then
we
want
it
to
stay
where
it
is,
but
we
might
add
that
so
you
go
like
daniel
was
saying
for
security
that
he
wants
one
place
that
he
can
go
to
and
see
everything
that's
out
there
right.
B
A
And
I
think
I
think
that
makes
sense
right
there.
There
are
themes
that
are
so
compelling
securing
jenkins
managing
jenkins.
I
think
those
those
fit
as
as
really
they
should
be
their
own
section.
Okay,
good,
all
right!
Well!
So
then,
given
that
now
I
haven't
reviewed
the
text,
but
I
think
the
text
she
created
the
only
text
that
was
brand
new
of
what
she
created
was
actually
the
little
bit
of
a
section
intro
that
looked
fine
to
me,
so
I'm
prone
to
say:
let's
migrate,
let's
merge
it.
B
B
C
Yes,
I
nothing
important
just
one
topic
I
got
a
mention
from.
I
don't
know
how
to
pronounce
his
name,
so
he
tagged
you
and
me
on
the
viewing
the
changelog
preview.
If
you
go
to
your
github,
you
will
be
able
to
see
it
as
well.
So
I
wanted
to
discuss
more
on
that,
like
what
it
means.
A
So
viewing
the
change
log
preview.
Okay,
so
is
this
a
pull
require?
This
was
part
of
the
pull
request
on
oh
on
this.
Oh
very
nice.
Thank
you.
Thank
you.
Thank
you,
okay,
okay.
So
what
was
your
question.
C
Gavin
worked
on
the
previous
site
and
he
is
making
it
possible
for
us
to
make
the
changelog
also
viewable
on
that
deployed
site.
Is
that
what
he
means.
A
A
A
A
A
A
A
A
A
A
C
Yes,
but
it's
not
for
users
right
it's
for
only
for
reviewers.
A
A
A
B
I'm
no
I'm
not
talking
about
quality
at
all,
I'm
just
talking
about
what
they
are
supposed
to
be.
B
They
are,
I
mean
they're
supposed
to
be
as
good
as
we
can
make
them,
but
but
part
of
that
process
is
having
to
be
screwed
up,
sometimes
so
that
we
find
the
problems
before
they
deploy
into.
I
mean
if,
if
I
ever
found
anybody
who
would
produ
had
deployed
a
weekly
release
into
a
production
environment,
I
have
no
sympathy
for
them
about
anything
that
could
happen.
A
Anyone
who
chooses
to
use
a
weekly
release
is
also
choosing
to
upgrade
every
week
and
if
you
are
not
upgrading
every
week,
you
are
for
some
period
until
you
next
upgrade
to
a
weekly.
You
are
running
unsupported
because
the
community
does
not
take
care
of
anything
other
than
the
most
recent
recent
weekly
release
right.
So
so,
for
me,
the
choice,
the
choice,
weekly
or
lts
is
driven
mostly
by
how
often
do
you
want
to
upgrade
and
if
you're
not
willing
to
upgrade
every
week,
your
only
other
choice
is
upgrade
upgrade
monthly.
A
B
I
mean
if
I
run
one
of
these
large
organizations,
and
there
are
features
coming
that
I'm
very
anxious,
for
I
might
be
putting
this
onto
a
test
system
and
really
beating
on
it.
While
it's
a
weekly
release,
that
would
be
good,
but
again,
that's
not
for
your
grandmother.
You
know
that's
something
that
your
grandmother
doesn't
do.
That's
somebody
who's
pretty
sophisticated,
knows
what
they're
doing,
and
they
know
that
what
they're
running
has
a
high
probability
of
failing.
That's.
Why
they're
doing
it.
C
A
B
B
B
A
B
A
B
A
Right
that
it's
just
we
don't
want
it,
we
don't
want
to
make
pejorative
comments
towards
the
the
weeklies
they
are.
They
are
not
as
heavily
vetted
as
lts,
but
yeah
dan.
I,
like
daniels
and
oleg,
gave
me
the
same
feedback.
He
said,
look,
don't
don't
you
dare
be
saying
bad
things
about
weekly.
We
intend
for
it
to
be
good.
A
A
A
A
A
A
B
Yeah
well,
let's
go
back!
Does
the
preview
change
long
for
the
upcoming
release.
A
A
A
A
B
A
Do
oh
for
the
upcoming?
It
is.
Yes,
that's
correct,
weekly
you're
right,
because
this
will
this
I
I
don't
see
us
using
this
for
lts,
I
guess,
or
if
we
do,
it
would
have
to
be
a
different
url.
It
would
be
right
change,
log
dash,
pre,
stable
dash
preview
or
something
okay,
so
for
public,
for
we
don't
need
to
say
publicly
available.
It's
just
a
weekly
release
right.
B
Long-Term
support
doesn't
because
long-term
support
is
long-term
support.
Oh
it's
just.
A
B
A
A
A
I'm
fair
enough!
Okay!
So
now
I
don't
I
and
I
have
not
so
so-
discussed
minor
phrasing
change
as
our
suggestion
to
link.
A
A
A
B
A
A
A
You're
going
to
read
the
text
for
the
for
the
diagnosing
errors,
this
the
page
that
was
removed.
Let's.
A
B
A
A
Okay,
so
is
this
text
big
enough
for
you
to
read
it.
B
B
A
Yeah
so
so,
how
would
you
like
to
phrase
it.
B
B
B
How
did
I
was
gonna
say,
occur
regularly,
but
that's
got
a
problem.
Okay
out
of
memory
errors
may
happen
for
yeah
one
of
four.
B
A
B
I
got
another
when
I
take
one
away
could
say
moldable
since
several
is
supposed
to
oh.
C
A
B
B
A
B
A
A
A
B
B
A
B
Okay,
go
back
to
your
minutes.
Do
you
want
to
note
that
we'd
like
to
see
index
dot
a
dot,
to
have
an
introduction
to
this.
A
A
A
A
B
A
A
and
so
yeah
they're
fine.
You
know
they're
gonna
be
great,
but
but
it's
just
a
you
know:
it's
been
an
adventure
trying
to
find
out
where
the
grandparents
going
to
go
to
see
their
grandchildren.
The
answer
right
now
is
they're
not
going
anywhere
and.