►
From YouTube: 2021 05 31 Docs Office Hours
Description
Jenkins documentation office hours generating the weekly changelog for the Jenkins 2.297 release.
A
A
A
B
B
A
A
A
D
A
A
A
A
B
A
B
E
A
And
this
would
have
worked
just
fine
as
well,
if
you
had
initially
cloned
the
the
jenkins,
the
upstream
repository
instead
of
your
fork,
but
because
you,
your
first
clone,
was
of
your
fork.
It
only
brought
in
the
tags
that
existed
at
the
time
that
you
created
the
fork.
So
tags
don't
get.
Don't
get
magically
copied
from
the
upstream
to
the
fork
on
each
update
of
the
of
the
upstream.
D
E
C
E
A
Okay,
now,
why
would
it
say
the
29th
today
is
that's
interesting
because
today
is
june,
1
right
for
you
in
your
time
zone.
Your
today
is
but
but
you
can
correct
it
or
or
that's.
That's
fine!
That's
just
a
proposal.
So
let
me
look
at
my
changelog.yaml
just
to
see
yeah
mine
also
says:
oh
okay,
mine
also
says
the
29th
and
I
think
that's
because
that's
probably
the
last
time
there
was
a
change
merged.
A
So
so
that's
not
not
unreasonable.
It's
just
saying,
then
the
newest
commit
is
from
the
29th
okay
good.
Oh
that's,
fine,
okay!
So
I'll
change
it
to
six
well
and
it
actually,
it's
okay!
You
can
just
leave
it,
as
is
that
file
at
the
top
is
intentionally
read
only
because
we
don't
want
you
to
change
the
file
at
the
top,
we'll
you'll
paste.
A
B
A
B
D
A
B
A
D
D
A
A
A
A
That's
okay,
so
here
the
you
you,
this
is
great.
Visual
studio
did
a
wonderful
job
of
showing
you
where
the
conflict
is,
let's
go
ahead
and
resolve
that
conflict
and
the
way
you
resolve
it
here
is.
We
want
to
keep
the
version
that
is
on
the
bottom,
half
of
that
and
delete
the
top
half
so
so
delete
lines,
one
one:
zero,
nine,
eight,
nine,
nine
and
one
one
one:
zero,
zero,
okay
and
then.
A
A
Okay,
because
really
we
don't,
we
don't
want
your
copy
of
the
branch
to
get
out
of
date
with
what's
on
the
master,
I
assume
there's
nothing
on
your
log
dash
2.294,
oh
whoops
whoops!
This
is
the
wrong
branch
name.
Isn't
it
right?
Let's
so
we
need
a
new
branch.
We
don't.
Okay,
so
get
get
space
merge
space,
minus
minus
abort.
A
A
Space
upstream,
slash
master,
so
what
that
command
says
is
create
me,
a
new
branch
name.
It
change
log
dash,
2.296
based
on
upstream
master,
and
now,
if
you
look
in
your
weekly
gaml
that
just
changed
in
visual
studio,
visual
studio
code
you'll
see
that
it's
got
a
2.295
below
the
place
where
we're
at
right
now.
D
A
A
C
D
A
D
A
A
A
A
A
A
A
D
D
A
A
No,
no,
actually,
you
are
in
the
right
place.
We
want
not
jenkins
that
io.
We
need
to
go
to
jenkins
core,
but
we
want
to
go
to
the
version
you
forked
from
so
we
want
to
go
to
the
upstream
so
right
below
your
username
jenkins.
There
is
the
the
repository
exactly
we
want
to
go
there
and
now
look
at
the
pull
request.
There.
D
A
A
Oh,
oh,
oh
look,
I
think
it
may
already
be
in
the
top.
Very
first
line
says
see
the
jenkins
bug
report
and
the
earlier
pull
request
so
open
that
pull
request
in
a
new
tab
and
let's
go
look
at
it.
Oh
that's
great
same
tab
is
also
fine.
Okay,
yes,
okay.
This
will
now
tell
us
which
version
first
included
this
okay.
A
A
A
A
A
D
A
A
Put
it
on
the
same
line,
I
don't
know
that
there's
any
mandatory
for
me.
It's
always
been
easier
to
have
it
on
the
same
line
yeah,
and
there
are
two
brackets
side
by
side.
Is
that
good
and-
and
I
think
we
should
remove
the
first
set,
so
it
would
say
without
yeah,
exactly
it's
fixed
regressions
and
form
submissions
from
unwanted
form,
validation
in
any
browser
yeah
that
for
me,
yes,
this
looks
good.
B
D
B
A
B
A
A
E
A
Okay,
so
fix
the
wording
in
the
message
all
right,
so
maybe
okay,
maybe
we
need
to
look
at
the
actual
commit
so
dear
azure
you're
getting
the
experience
here
of
the
same
thing
I
do.
Sometimes
I
have
to
read
the
source
code
to
decide.
What's
the
best
way
to
say
it
so
so
show
the
commits,
and
let's
see
what
the
message
is,
that
it's
going
to
give
to
the
user
sure
so
show
the
second
one.
It
says,
fix
the
wording
in
the
message
yeah
that
one
okay,
there
are
still
okay
got
it.
A
A
A
A
A
A
D
A
A
You'll
see
otherwise
detached
many
dependents,
okay,
so
so
what
this
is
doing
is
it's
being
smart.
It
says
if
there
are
less
than
15
dependents
show
every
one
of
them.
If
there
are
more
just
say
that
there
are
a
lot
that
there
are
very
many
okay
now
we
have
to
go
back
to
visual
studio
code
and
decide
how
we
say
this.
A
Show
and
it
that
that
now
makes
more
sense
to
me
this,
the
notion
of
an
implied,
plug-in
dependency
says
the
reason
it's
an
implied.
Dependency
is
because
the
plug-in
was
originally
inside
jenkins
core
and
has
now
been
split
into
a
plug-in,
and
therefore
the
dependency
is
implied,
not
direct.
So
so
this
there's
the
okay.
So
now,
how
do
we?
What
if
we
said.
A
A
But
is
that
really
accurate
show
implied?
Show
it's
plug?
Okay,
now,
thinking
about
its
show,
which
plug-ins
keep
a
plug-in
and
split
okay
back
to
the
pull
request,
because
I
think
I
may
have
just
said
it
exactly
the
wrong
way:
okay,
okay,
so-
and
you
know
now
go
to
the
back
to
the
comment
because
back
to
the
the
the
conversation
around
this,
so
the
yes,
okay
and
toby,
says.
A
A
D
A
B
D
B
B
D
A
B
A
Yes,
so
I
would
this
one,
I
think
is,
is
well
phrased,
but
we
need
to
use
a
a
specific,
let's
use
a
specific
format
earlier
in
the
file
to
insert
a
reference
to
a
link
so
take.
I
think
we
should
take
everything.
That's
online
one,
one,
one,
nine
three:
we
can
we
can
click
yeah
so
that
the
developer
colon
that
is
intentionally
there.
This
is
this
is
a
change
that
is
relevant
to
developers
and
not
to
typical
end
users.
So
what
we
do
is
we
keep.
We
delete
line,
89,
90,
91
and
92.
A
And
now
now
there's:
okay,
it's
it's
making
a
reference,
and
I've
preferred
to
do
one
sentence
per
line
so
on
line
89
after
the
first
hard
stop
put
in
a
new
line
right
and
now,
there's
a
this.
Has
a
hyperlink
in
it
to
the
nis
notification
lamp
right.
That's
a
hyperlink!
There's
a
way
to
embed
hyperlinks.
A
A
Okay,
so
now
the
first
on
line
89,
we
say
pull
instead
of
issues
so
on
yeah
there
it
should
be
pull
and
then
the
pull
request
is
5521
and
you'll
see
that
on
line
85
right
exactly
okay
and
then
the
issue
is
there
isn't
an
issue,
but
now
we're
going
to
do
a
now.
We
need
the
url
syntax,
and
so
for
that
we
need
to
find
an
example
in
this
file
of
somebody.
A
A
B
A
A
A
A
A
D
A
A
Okay,
let's
go
with
the
oh.
No,
that
was
perfect.
Look
the
terminal,
prompt
appeared,
don't
be
shy.
The
terminal
prompt
appeared,
it's
a
it's
a
great
way
to
learn
to
explore
something
so
do
a
pwd
there.
Let's
see
what
directory
it's
in.
That's
my
home
action.
Okay!
So
go
to
your
jenkins.io
directory.
A
B
B
A
A
A
B
A
B
A
A
A
A
B
A
That's
the
idea
we
would
love
to
have
a
rotation
of
multiple
people
doing
this,
but
it
would
be
great
if
you're
willing
to
do
it
at
a
minimum.
This
is
a
great
win
that
we'll
have
you
and
I
will
work
together
so
that
you
can
submit
what
you've
done
for
this
week,
so
that
yours
will
be
your.
You
will
have
written
the
the
changelog
for
jenkins
2.296
that
will
release
in
about
10
hours.
B
A
That's
and-
and
that
is
great-
I
am
very,
very
grateful
for
your
willingness
to
do
that.
Thank
you,
your
the
time
that
you're
at
in
india
is
perfect,
because
you
could
do
it
tuesday
morning.
Your
time
and
most
of
the
people
in
europe
haven't
haven't,
started
work
yet,
and
most
of
the
changes
that
will
occur
in
the
in
the
weekly
release
are
already
in
so
you've
got
a
big
benefit
for
us.
If
you're
willing
to
do
this,
it's
a
great
win.
D
A
A
A
A
E
A
There
it
is
so
line
93
right,
so
save
that
and
you
notice,
when
you
did,
that
in
the
window
below
in
the
terminal
below
it
says,
change
detected
for
files
such
and
such
and
it
rebuilt
the
site.
So
the
nice
thing
about
doing
this
inside
studios,
you
can
change
it
in
studio.
It
will
detect
it
and
give
you
a
better
view
of
the
site.
A
A
A
A
A
So
so
what
you
were
doing
is
you
were
using
a
facility
of
the
of
the
bash
shell,
and
many
linux
shells
have
the
same
thing
where
you
have
the
option
to
put
something
in
the
background
in
case
you
want
to
come
back
to
it
later,
but
most
of
us,
just
like
you,
use
our
window
manager
to
do
things
and
keep
everything
in
the
foreground
makes
sense.
Yes,
all
right,
so
so
now
we're
ready
to
you've
done
the
git
diff.
So
it's
time
to
do
the
get
add
and
the
git.
A
A
A
Okay,
no
gh
command,
so
so
now
there
there
you
could.
We
could
go
ahead
and
do
the
and
I
don't
know
what
that
snap
command
would
do.
I
would
use
a
different
command
to
install
gh
than
the
one
they're
recommending,
but
but
let
me
suggest
to
you
what
it
is
and
then
you
can
decide
if
we
should
spend
the
time
to
do
it.
You
and
I
can
go
through
and
submit
this
pull
request
using
just
get
commands
and
the
github
web
pages.
So
that's
very
easy
to
do.