►
From YouTube: 2021 06 21 Docs Office Hours
Description
Jenkins documentation office hours June 21, 2021 with topics including weekly changelog generation and LTS changelog generation
A
A
A
B
A
B
C
A
B
And
after
that,
one
more
question
about
how
the
docker
tool
change,
lock
tool
extracts
the
pull
request
from
jenkins
repository
to
the
the
changelog.aml
file
for
us.
So
I
wanted
to
know
which
pull
request
goes
to
the
comment
section
and
which
does
not.
So
there
are
some
tags
right.
So
I
have
to
wanted
to
have
some
discussion
on
that
as
well.
A
A
Here
and
that
will
cause
it
to
be
written
into
the
change
log
as
a
comment,
whereas
this
one
does
not
have
skip
dash
change
log,
so
it
would,
by
default,
tend
to
be
written
into
it.
Now
I'm
going
to
actually
label
it
skip
change
log,
because
this
particular
one
I
don't
think
justifies
an
entry
for
the.
A
B
A
That's
correct,
certainly
only
the
ones
that
have
been
closed
and
or
are
merged.
Actually,
I
guess
is
the
is
the
more
precise
term
and
if
they've
been
merged
and
have
skip
change,
log
then
they'll
be
in
the
comment:
if
they've,
if
they
don't
have
skip
change
log,
I
don't
know
if
I
can
do
that,
no
it
doesn't
do
negation.
A
And
somehow,
I
think
that
oh,
this
was
just
closed.
Okay,
that's
why
that's
not
a
problem!
This
was
not
merged.
We
wanted
one
that
was
merged
so,
like
this
one
nope,
it's
also
got
skip
many
many
of
them.
Okay,
here
we
go
implement
intercepting
executor
surface
without
java
without
guala
this
one
has
been
merged
and
should
be
in
a
in
one
of
the
change
logs.
B
A
B
A
Yeah,
so
I
think
yeah
that
that's
an
interesting
one,
because
this
is
this
particular
library.
Guava
has
been
filled
with
challenges
for
us
and
we
we
want
to
decrease
our
usage
of
guava
wherever
we
can,
but
in
this
case
the
class
hierarchy
includes
guava
guava
objects
in
the
signatures
and
therefore
doing
it
without
guava
really
does
mean
making
changes
to
the
class
hierarchy,
and-
and
so
that's
that's-
the
worry
there
that
this
is
a.
This
is
a
very
a
very
cool
change.
Yep.
B
A
A
A
A
Let's
see
it
needs
to
be
closed
back
porting
for
2.289.,
so
we
should
see
65
766,
which
we
do
and
65
751
and
65
657,
which
we
do
and
6
24,
which
we
do
and
okay
good.
So
so
this
and
this
match
seem
to
match
each
other
showing
us
which
things
have
been
backported
from
2.289
or
from
later
releases
than
2.289
into
289.2.
B
B
B
A
A
Okay,
is
that
correct?
I
think
that's
correct.
Okay,
and
now
we
don't
have
the
horizontal
scroll
bar
and
we've
got
the
information.
So
this
column
here
shows
us
which
version
included
the
fix
first
included
the
fix
this
one,
I'm
not
sure
what
to
think
about
that
extra
2.289.1
we'll
have
to
investigate
that
further,
and
this
one
I
don't
know
which
version
included
those
two.
So
let's
do
some
quick
checking
here:
64
347.
A
A
A
A
A
A
A
A
A
A
A
A
A
C
C
A
A
A
A
B
A
A
A
A
B
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
B
A
A
A
A
B
A
A
A
A
A
A
A
A
A
A
A
A
A
A
A
B
A
A
A
A
A
A
A
B
A
B
A
B
Yes,
so
there
are
some
changes
which
I
have
to
add
in
the
weekly
change
log
and
there
are
some
changes
that
are
added
into
the
lt's
change
logs.
So
I
I
was
thinking
that
all
the
weekly
change
log
that
fall
in
the
four
week
timeline
will
go
into
the
lts
change
logs,
but
that
is
not
the
case.
So
how
do
we
do.
A
A
A
A
A
B
A
A
A
A
A
A
A
A
B
A
B
A
A
A
B
Okay-
and
I
also
went
to
another
website
of
someone
another
thing-
so
they
have,
they
have
changed
logs
and
I
clicked
on
it
and
they
redirect
me
to
the
github
repository
having
all
the
changes,
but
in
case
we
have
a
dedicated
place
where
they
can.
The
developers
can
view
the
change
logs
and
it
is
for
their
convenience
and
specific
order.
Style
guides
is
followed,
so
this
is
just
to
help
the
developers
right
so
that
less
time
is
spent
from
their
site.
A
Well,
so
so
the
jenkins
also
likes
the
the
github
releases
concept
right,
so
we
use.
We
also
are
quite
happy
to
use.
I
think
what
you're
referring
to-
and
it
is
something
like
this
where,
when
I
look
at
this
through
github,
it
tells
me
oh
here
are
the
new
features,
and
improvements
in
298
here
are
the
dependency
updates.
Is
that
what
you
were
referring
to.
B
A
B
A
C
A
A
If
I
had
an
issue,
I
experienced
notable
issues.
I
can
click
this
one
and
it
will
prompt
me
for
the
issue
number
from
jira.
Now
I
didn't
so
and
likewise
for
this
one.
If
I
had
to
roll
back,
I
can
enter
that
and
then
it
will
remember
those
issue
numbers
here
so
that
others
can
see.
Oh
here
are
the
things
that
the
community
reported
were
problems.
B
A
I
I
don't
know,
that's
a
good
question.
Let's
go,
all
I
can
do
is
make
guesses
on
that
one.
That's
a
very,
very
good
one,
because,
because
what
we've,
what
we
have
here
is
I
can
open
it
up
and
show
you.
We've
got,
let's
switch
I'll
switch
to
the
jenkins
account
and
now
we're
going
to
look
at
the
playlists
jenkins,
playlists,
okay,.
A
Not
shared
something
that
I
should
not
be
sharing
on
screen,
oh
well,
and
and
and
that's
that's
okay
right.
If,
if
you
have
you,
let
me
let
me
know
and
we'll
delete
that
video.
If
you
discover
oh,
there
was
something
sensitive
that
I
had
shown.
Then
then
we
delete
that
video.
That
there's
no
shame
in
us
saying
oops.
We
didn't
intend
to
show
that.
A
A
A
How
we
write
change
logs,
I
don't
know,
apparently
I
I
I
don't
have
any
answer
as
to
why
why
that
one
would
have
been
so
popular
any
are
the
any
of
the
others
as
popular
as
that.
No
10
views.
Okay.
So
that's
that's
very
interesting.
I
I
I
wonder
what
well,
let's
maybe
there's
something
to
be
learned
from
that?
A
B
B
A
A
A
A
It
is
so
well,
it's.
The
contributor
summit
is
friday
or
saturday
saturday
morning,
your
time
and
and
so
it
will
be,
it
will
be.
We've
got,
we've
got
a
few
days
still
that
we
can
meet
together
to
talk
further
right.
That
would
be
great
all
right.
Thanks
very
much
I'll,
stop
our
recording.
You
have
a
great
day.
Good
luck!
Thank
you.