►
From YouTube: 2021 05 24 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
This
is
jenkins
documentation,
office
hours,
reminder
that
we
abide
by
the
jenkins
code
of
conduct,
be
nice
to
each
other,
and
thanks
for
being
here,
everyone
so
topics
that
I
had
on
the
agenda
included.
A
B
A
Meg
all
right
so
topics
that
were,
on
my
mind,
generating
the
change
log
for
jenkins
weekly
releases.
This
is
an
area
where
I
need
help
where
we,
it
would
be
a
real
benefit
for
us
to
have
multiple
people
able
to
do
this,
and
so
my
thought
was:
let's
use
today's
session
as
a
working
session,
and
what
I
would
like
to
do
is
go
through
it
once
myself
and
then
have
either
dira
dhiraj
or
meg
go
through
it
to
see.
Okay
can
somebody
else
do
the
same
thing
so
that
we're
confident
others
can
do
this?
A
A
A
C
A
All
right,
great,
okay!
Well,
so
then
meg
any
topics
that
you
want
to
add
nope.
This
looks
good
okay,
so
then,
let's
let's
get
started
on
this
one
and
dhiraj.
Are
you
based
on
a
linux
development,
environment,
windows
or
mac
os
linux,
okay,
good?
So
this
will
be.
This
will
be
second
nature
to
you
and
it
works.
It
works.
That's
the
natural
way
that
I
do
it.
So
this
should
be
a
perfect
thing.
I
propose:
are
you
interested
in
doing
being
the
changelog
generator
at
least
one
of
potentially
many?
A
Can
you
first
of
all
tell
me
what
it
is?
Actually
I
sure
can
you
bet
so
the
the
jenkins
change
log
is
that's
a
very
good
lead
in
excellent
question.
B
A
A
Yes,
I
was
just
I'm
I'm
able
to
understand
what
you're
saying
yes
super,
okay
and
and
this
change
log
that
we're
seeing
a
prototype
of
it
is
actually
generated
for
us
automatically
from
the
content
of
the
pull
requests
in
github.
A
C
Right,
I
understood
so
these
details
will
be
extracted
from
the
prs
that
have
been
words
in
past
right.
Correct,
yes,
exactly,
okay,
okay,
so,
and
what
about
this
community
reported
issues
the
like?
If
you
can
see
2.293
in
that
it
says
one
times
of
jenkins,
six:
five,
six,
six
five
one
times
of
this!
This
is
also
automatically
generated
right.
A
A
We
have
a
facility
that
allows
jenkins
users
who
are
running
a
particular
release
to
give
feedback
to
us
without
the
overhead
of
a
bug
report
without
all
the
work
of
other
things
to
say,
for
instance,
if
they
click
this
image
of
the
sunshine
you'll
see.
The
hover
text
tells
us
no
major
issue
with
this
issues
with
this
release.
So
when
I
click
that
it
pops
up
a
dialog
that
says
thanks
and
it
incremented
by
one
now,
if
I
click
this
one,
it
will
say:
oh
you
had
a
and
let's
first
cancel.
A
If
I
hover
over
it,
I
the
text
is
I
experienced
notable
issues,
and
so,
if
I
click
this,
it
asks.
Please
provide
the
issue
number
four
of
that's
causing
the
problem,
and
so
in
this
case,
if
I
would,
if
you
could
see
here,
that
there
were
13
users
on
2.292
that
that
entered
jenkins-65611,
this
thing
as
a
bug
report
and
that
that
set
of
this
problem
actually
is
what
caused
us
to
do
2.293.
A
A
If
I
open
that
you're
going
to
see
it
has
nothing
to
do
with
anything
on
this.
This
is
a
bug
that
was
fixed
15
years
ago,
so
people
can
and
do
spam
us,
and
we
have
intentionally
chosen
just
to
ignore
spam
in
the
rating
system.
It's
just
not
been
a
big
enough
problem
for
us
to
do
anything
other
than
just
ignore
it.
C
A
A
And
and
this
rating
system
that
we
see
is
available
not
just
for
weekly
releases
but
is
also
available
for
the
stable
long-term
support
releases.
So
when
I
look
at
the
long-term
support
release
change
log
here
we
see
oh
with
2.27.4,
there
were
38
38
reports
of
a
rollback
required
and
28
that
encountered
what
this
they
rate
notable
issues,
and
you
can
see
the
list
of
issues
here.
So
the
the
rating
system
is
quite
helpful
for
us
to
understand
without
the
overhead
of
making
someone
submit
a
fully
detailed
bug
report.
A
To
me,
so
so
that
we've
we've
seen
the
rating
system
now,
what
I
think
we
ought
to
do
is:
let's:
let's
look
at
generating
the
how
the
how
this
thing
is
generated,
so
it
is
generated
from
it's
generated
from
the
contents
of
the
jenkins
dot.
Oops
jenkins
helps
if
my
hyperlinks
are
working.
Doesn't
it
sorry
just
a
minute.
A
A
A
A
A
A
Okay,
so
the
the
crucial
instructions
are
actually
in
the
changelog
generators
readme
file
and
it's
easier
if
we,
if
we
look
at
this
from
a
web
browser,
so
let's
look
at
it
there.
So
here's
the
readme
and
what
it
tells
us
is.
This
tool
creates
core
change
log
drafts
and
we're
going
to
focus
on
weekly.
A
So
the
crucial
script
is
generate
jenkins
change
log
and
I
prefer
it
in
docker,
so
we're
going
to
focus
on
using
it
in
docker.
The
reason
I
prefer
it
in
docker
is
because
then
I
don't
have
to
worry
about
installing
specific
tool
versions
like
which
version
of
ruby
is
required
or
which
version
of
some
other
generator.
A
All
I
have
to
do.
Is
I
export
my
github
off,
which
I've
already
done
and
I'm
not
going
to
show
you
because
it's
secret
and
then
I
run
this
command
what's
happening
here.
Is
it's
saying?
Okay,
docker
run
set
an
environment
variable
github
off
with
the
value
of
the
github
auth
variable.
I
exported
mount
a
volume
for
my
current
working
directory
as
slash
github,
slash
workspace,
remove
things
when
I'm
done
this
minus
rm
and
run
the
program.
The
docker
image
jenkins
core
change
log
generator.
A
A
It
says:
oh
oops,
you
didn't
pass
a
version
number.
This
isn't
a
git
repository
and
therefore
something's
wrong.
Well,
I'm
in
the
wrong
place,
instead
of
being
in
core
changelog
generator
or
in
in
this
parent
directory.
I
need
to
cd
into
the
jenkins
directory
because
it's
going
to
use
the
contents
of
the
commits
here
to
help
it
understand
what
should
be
in
the
change
log.
So
now,
let's
try
that
same
command.
Again,
docker
run
minus
e
github
auth
equals
map.
A
So
what
it's
doing
now
is
it
says?
Oh
you
didn't
tell
me
a
version
number,
so
I'm
going
to
use
the
last
commit.
That
means
it's
going
from
jenkins
2.293
to
this
current
commit,
and
it's
telling
us
what
it's
doing
so.
It's
found
some
things.
It
found
something
from
angelique
and
now
it
wrote
a
draft
yaml
file
of
the
changelog,
and
if
we
edit
that
file
we'll
see
it
oops.
A
So
here's
the
draft
change
log-
and
this
thing
has-
is
a
yaml
file
with
data
so
the
date
this
would
be
the
date
of
the
release
and
only
be
set
to
tomorrow,
because
that's
when
we'll
release
it
and
then
one
entry
per
pull
request
so
ta
and
it
does
some
sorting
for
us,
so
it
puts
major
bugs
first
and
then
after
major
bugs
it
will
put
major
rfes
and
request
for
enhancement
and
then
bugs.
I
believe
then
rfe.
B
A
B
B
C
A
Yes,
good
question,
so
this
this
changelog.yaml
is
this
prototype
source
that
we
will
use
to
add
content
to
a
data
file
in
the
jenkins.io
repository
called
weekly.yaml
and
the
weekly.yaml
is:
is
the
data
file
that's
used
to
generate
this
html
page.
A
A
A
Okay,
so
that
step
is
something
like
this
so
notice
that
I'm
in
the
jenkins
directory
for
now,
so
I'm
in
the
jenkins
core,
I
need
to
change
to
the
documentation
directory
because
I'm
going
to
create
the
change
log
in
the
docs
directory
now,
and
in
this
case,
let's
see,
get
remote,
add:
let's
see
what
shall
we
call
it
get
remote,
rename
origin
upstream?
A
A
The
last
change
was
this
g
sock,
20,
20
2105
updates,
I'm
going
to
create
a
branch
change,
log
dash,
2.294,
and
now
I'm
ready
to
do
my
edits.
So
I'm
going
to
bring
up
my
editor
and
we're
going
to
edit
content
underscore
data
change
logs,
so
notice
that
it's
this
is
data
not
pages
and
then
we're
going
to
bring
up
weekly
and
I'm
going
to
bring
in
at
the
same
time,
jenkins,
slash
jenkins
or
slash
changelog.yaml.
A
A
C
A
A
A
A
Okay,
jenkins,
cli
unable
to
read
ssh
and
here's
what
we've
got
it
so
it
says
the
user
says
they
upgraded
from
2.280
to
2.285,
and
now
we
should
be
able
to
see
so
downgraded
to
283.
So
the
problem
is
likely
in
2.284
and
as
we
read
further
in
this,
we
would
just
see
the
description.
Oh
yes,
it
is
something
happened
in
2.284
and
here
is
the
problem.
So
the
regression
was
introduced
in
2.284.
A
A
Yeah
very
good
question,
so
let's
do
the
same
thing
again
this
time
with
the
next
one
on
the
list,
and
it
says
okay,
so
it's
says
another
major
bug,
bridge
methods
are
no
longer
present,
and
so
what
the
proposed
change
log
says:
restore
bridge
methods
used
to
retain
backwards,
compatibility-
and
now
I
don't
know
if
this
one
should
be
flagged
as
a
developer
issue
or
not,
because
it's
I'm
not
sure
how
users
will
see
this.
A
A
A
B
B
Reporting,
oh,
not
that
it's
not
just
reporting,
it's
actually
going
to
fail
right.
This
is
going
to
be.
A
A
B
B
B
B
A
B
A
A
A
A
A
A
B
A
So,
in
this
case,
latest
version
of
a
given
release
line,
there
are
two
release
lines:
weakly
and
stable.
The
stable
is
also
called
lts.
So
I
assume
that's
correct
usage.
Then.
B
A
A
C
A
A
A
B
A
A
A
A
A
A
Annotation,
so
the
reason
I
put
it
here
is
a
comment
it
won't
show
to
the
user,
but
I
put
it
as
a
comment
to
be
sure
that
if
others
ask
hey,
why
did
you
do
that
they
had?
They
can
see
that
I
at
least
thought
about
it.
Likewise,
I
need
to
do
the
same
thing
for
this
front-end
maven
plug-in
that
was
done
as
part
of
5490,
so
I
copy
that
line.
Call
it.
A
Both
included
now,
we've
got
one
more,
and
this
one
is
update,
x
stream
from
1.4.16
to
okay
and
this
one,
and
now
this
is
me
knowing
some
things
that
others
may
not
know.
Xstream
is
a
particularly
important
library,
so,
usually
when
we
update
it,
we
acknowledge
that
update
in
the
change
log
and
sorry.
I
don't
know
how
to
highlight
it
other
than
by
saying
yes,
it's
it's
important
enough
that
when
we
update
it,
we
we
note
that
so
here
is
the
example
that
I
used
before.
A
C
So,
as
you
said,
the
extreme
library
is
very
important
and
we
should
not
put
it
among
the
comments.
So
how
do
I
know
if
I'm
working
on
it
by
myself
that
this
is
the
one
that
is
important.
A
A
C
A
Thank
you,
yeah
you'll
find
I,
I
suspect,
you'll
find
the
vs
code,
yaml
editor
quite
comfortable
and
yes,
that
it
will
behave
the
way
you
expect
so
that
that
makes
it
really
great.
In
my
case,
I
I
haven't,
made
the
switch
to
vs
code
because
of
some
tools
in
this
particular
editor
that
make
my
life
much
easier,
but
but
vs
code
is
great
for
to
editing
yaml
files.
Use
it
by
all
means
awesome.
A
A
A
It
will
generate
a
subset
of
the
site
based
on
what
it
sees
and
then,
when
I
click
load
on
the
page,
it
will
generate
those
pages
as
necessary.
So
right
now
what
we're
seeing
is
the
the
site
builder
constructing
itself
on
this
on
this
machine
and
it'll
be
a
minute
or
two
here,
while
it's
working
through
that.
A
And
this
scripps
bundle
exec,
oh
yeah.
What
this
does
is
asks
for
what
is
the
current
version
of
jenkins
that's
being
delivered?
It
asks
a
question
to
the
the
jenkins
update
center
extracts,
the
current
version.
Then
it
will
use
that
later
so
now
it
is
pulling
in
the
npm
docker
image,
and
now
it's
running
awestruct.
This
thing
right
here,
which
is
the
site
generator
and
now
it's
generating
the
site.
A
A
A
The
site,
so
this
is
going
to
generate
instead
of
with
the
most
recent
jenkins
release
it's
going
to
generate
assuming
the
most
recent
release
is
this
number
that
I
told
that
it
is
so
back
to
this
site.
The
current
actual
release
is
2.293,
2.294
does
not
exist
yet,
and
so
in
order
for
me
to
see
something
that
does
not
exist.
Yet
I
had
to
update
this
this
file.
So
now,
let's
go
the
the
files
that
are
mentioned
in
that
script.
A
C
Yes,
so
just
to
check,
if
I
got
this
out
or
not
so
the
pull
request
that
we
have
all
the
issues
or
everything
that
we
have
mentioned
here.
Those
are
the
reason
why
we
introduced
2.294
and
on
the
icons
that
we
see
the
three
items.
Those
are
just
a
way
for
the
users
to
you
know
pitch
in
their
views
on
how
this
new
version
2.294
is
working
out
for
them
right,
correct.
A
A
A
A
Sizer
will
let
me
set
this
thing
to
that
width.
Okay.
Now
I
need
to
capture
a
copy
of
this,
because
readers
who
are
looking
at
this
pull
request
won't
find
it
easy
to
read
the
yaml
file
it's
much
easier
for
them.
If
I
give
them
a
picture
of
how
it
will
look
so
here,
I've
copied
that
into
this
image,
and
now
when
I
submit
the
pull
request
I'll
paste
this
image
in
so
that
they
can
see
how
it
looks
when
it's
rendered.
A
And
now
I'm
ready
to
push
and
for
me
it's
easier,
if
I
do
this
now
with
github
with
the
ghpr
command,
because
it
does
an
awful
lot
of
things
for
me.
So
gh
is
the
command
line,
git
interface
and
I'm
going
to
do
ghpr
create,
and
it's
going
to
ask
me
some
questions
so
which
should
be
the
base
repository
the
base
repository
the
one
that
is
the
the
ultimate
destination
for
everything.
The
base
should
be
jenkins,
slash
jenkins,
dot,
io
now,
which,
where
should
we
push
the
change
log
branch?
A
A
A
It
will
look
like
this
and
the
changed
files.
Look
like
this
as
the
yaml
file.
With
all
those
comments
now
reviewers,
it's
it's
not.
It
is
quite
common
for
reviewers
to
detect
a
mistake.
I
made
and
say:
hey,
could
you
fix
this?
Could
you
fix
this?
Don't
be
don't
be
intimidated
by
having
mistakes
detected
in
what
you're
creating
that's?
What
happens.
A
C
What
do
I
need
to
do?
Can
you
please.
A
A
A
So
dhiraj
this
changelog
generation
for
me
is
a
crucial
thing
that
needs
help
on
this
ideas
of
things
where
people
can
help.
There
were
some
other
suggestions,
let's
see
in,
for
instance,
so
generate
weekly
change.
Log
was
the
one
reviewing
documentation.
Pull
requests
is
certainly
another
place
where
you
could
be
helpful
if
you've
got
time
and
capacity.
A
The
other
is
preparing
docu
for
the
document
for
the
contributors
summit
and
this
one
I
think
zenob
abubakar,
is
wanting
to
take
it
on
if
she
can.
So,
if
you
don't
mind
not
being
the
leading
the
documentation
track,
but
just
being
a
participant,
I
think
she's
interested
in
leading
it
sure
that
works
for
me
great
all,
right,
meg,
anything
else.
We
need
to.