►
From YouTube: 2021 10 18 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
Here
we
go
all
right.
Welcome
everyone.
It's
jenkins
documentation,
office
hours
today
is
the
18th
of
october
19th
of
october
india
standard
time
and
remind
everyone.
We
abide
by
the
jenkins
code
of
conduct
so
be
nice
to
each
other.
A
Let's
see
I
haven't
seen
kristen,
okay,
so
topics
I
had
on
the
agenda
adopt
a
plug-in
tutorial
and
blog
post
for
diraj
and
me.
Then
I've
got
a
topic
on
plug-in
docs
migration
that
the
oktoberfest
contributor
has
launched
and
we'll
talk.
Briefly,
then
meg
had
a
question
about
security
chapter.
She
had
a
conversation
with
daniel
beck
and
I'd
like
to
capture
what
she
learned
from
that
conversation
and
then
source
structure,
standards
for
jenkins.io
with
meg
and
then
classifying
wiki
pages
for
migration.
A
All
right
so
adopt
a
plug-in
the
tutorial
and
blog
post,
so
the
the
first
recorded
session
with
darren
pope
went
well.
The
second
session
starts
in
less
than
24
hours
and
a
third
session.
C
A
A
C
A
C
A
A
Okay,
so
in
terms
of
the
so
the
the
the
way
the
first
recorded
session
worked,
it
covers
the
first
three
four
three
of
the
first
four
topics
in
the
in
the
contributing
to
open
source
workshop
notes,
we'll
probably
cover
another
three
or
four,
maybe
five
in
the
next
session,
and
then
maybe
three
or
four
more
with
discussion
in
the
third
session.
And
then
the
idea
is
each
of
those
chunks
of
a
session
will
embed
the
video
into
that
page.
A
The
page
will
describe
how
to
do
it
and
the
person
can
watch
the
video
to
get
a
live
demonstration
of
how
to
do
it
and
I'm
pleased
to
note
we
had
our
first
person
matt
jacobson,
actually
offered
to
adopt
a
plugin
based
on
having
taken
the
steps
in
the
workshop
whoa,
so
so
big
win.
Now,
we've
confirmed
that
so
the
skeleton
of
the
submission
for
jenkins
that
I
owe
is
on
on
my
branch
and
we've
confirmed
that
dhiraj
can
also
push
to
that
branch.
A
So
so
that's
that's
a
big
win
as
well.
So
what
we
see
here
is
if
we
scan
down
a
little
bit.
Where
is
it?
We
have
to
go.
Oh
yes,
here
we
go
so
here's
dhiraj,
making
a
change
and
making
another
channel,
and-
and
here
we
are
with
me,
interspersed
all
along
this
branch,
so
he
and
I
can
contribute
together.
A
I
had
originally
dreamt
that
we
would
have
it
ready
within
a
few
days.
My
time
is
not
going
to
allow
that
I'll
feel
very
lucky
if
we
get
it
done
before
the
end
of
october
dhiraj.
Are
you
critically
dependent
on
this
as
part
of
your
hacktoberfest
contributions?
Or
will
you
be
okay?
If
we,
if
we're
not
able
to
get
this
finished
before
end
of
october,.
D
Well,
I've
thinking
I
was
thinking
about
finishing
it
before
october
now
I
do
think
that
it's
a
little
bit
difficult.
So
it's
okay.
A
A
A
Well,
and
and
meg
you
are
welcome
to,
let's
see
how
could
I
yeah
I
may
I
may
send
you
a
pointer
to
something
meg
after
I've
had
a
little
more
time
to
to
work
it.
I
may
send
you
a
pointer
and
ask
for
a
review,
I'm
I'm
not
yet
ready
to
submit
a
poll
request
to
jenkins.io,
because
I
think
I
think
we've
got
enough
material
in
the
in
the
contributing
to
open
source
document
that
we
should
rather
have
you
review
their
first
meg
and
I
think
you've
actually
already
done
that.
A
C
A
He
and
I
are
doing
these
and
we
refer
to
the
document
and
say:
okay,
let's
read
this
and
and
then
we
discuss
it
and
between
the
reading
and
the
discussing,
if
there's
an
error
in
the
document,
we'll
we'll
detect
it.
So
so
I'm
not
overly
worried
about
that.
But
before
I
submit
a
poll
request
to
jenkins
that
would
like
to
have
at
least
75
percent
of
these
topics
covered
in
the
in
the
steps,
so
that
there's
a
step
for
each
of
them
to
say:
hey,
do
this
and
then
do
this
and
then
do
this.
E
A
Okay,
so
that's
it
for
for
that
topic,
dhiraj!
You
are
welcome
to
step
away
and
get
some
rest
before
you
have
to
start
a
new
working
day,
even
if
you
can
only
take
a
30
minute
nap
that
may
help
you
be
functional
at
work
today.
D
Yeah,
that's
not
a
problem
sure,
so
I
want
to
discuss
a
little
bit
more
on
the
topic
and
the
thing
is
I,
after
our
previous
meeting
where
you
helped
me
set
up
the
environment
on
my
work
laptop,
I
ran
some
command
to
like
su
sudo
make
run
and
I
realized.
I
realized
that
I
don't
have
suitable
permissions,
so
the
commands
were
not
running
many
other
commands
as
well.
So.
B
D
B
You
shouldn't
have
to
do
sudo
what
what
made
you
think
you
needed
to
do
sudo.
Actually,
there
were
some
other.
A
D
Yes,
because
then
I
started
reading
a
blog
which
describes
how
to
download
docker
and
that
had
a
pseudo
command.
So
I
realized
oh,
it's
a
loop,
but
I'm
stuck
so
I
followed
the
same
procedure
that
you
showed
me
and
I
set
up
my
personal
laptop
with
everything
and
it
runs
the
site.
It
generates
the
site
locally,
but
the
thing
is:
if
I
go
to
I,
my
aim
was
to
get
like
to
see
the
changes
that
you've.
C
A
A
And
it
might
be
this,
it
depends
on
what
you
name
my
the
upstream.
So
what
that
does
is
check
out
the
correct
branch.
First.
A
A
So
generating
the
site,
localhost
4242
and
then
in
my
case,
because
I'm
I'm
running
this
on
a
linux
computer,
but
I
use
windows
as
my
primary
machine
I'll
switch
over
here
and
open
up
bat
computers,
port
4242,
and
this
is
the
generated
site.
Now
it's
developer
guide
and
you
should
see
it
right
there.
So,
let's
put
this
way.
A
A
A
A
No,
I
don't
see
a
lot
of
difference
there.
Okay,
so
oh,
oh!
Yes,
I
do
see
differences
there.
Oh
look
at
this.
What
a
foolish
mistake!
A
A
D
D
F
D
Not
not
a
problem
at
all,
so
if
I
just
want
to
submit
like
do
some
changes
from
my
side
just
to
see
whether
I'm
able
to
push
or
not
so
what
do
you
suggest
to
do
on.
B
A
very
quickly
basis.
A
Add
add
a
tech,
add
a
line
to
add
a
line
to
one
of
these.
For
instance,
I
stop
the
list
at
convert
common
api
dependencies.
But
now,
if
you
look
in
this
in
this
list,
after
convert
common
api
dependencies,
there's
improved
pipeline
documentation,
add
a
link
to
report,
an
issue
that
I
just
added.
I
think
today,
because
I
discovered
oh
there's
a
better
way
to
do
things.
Assign
repository,
add
one
of
those
and
commit
it.
A
A
A
So
git
log
minus
minus
numstat
master,
dot,
dot
head
so
from
the
master
branch
to
the
place
where
I'm
working
now
and
then
there
is
the
file
name
and
the
benefit
of
this
is
now.
You
can
go
backwards
and
see.
Oh
and
here's
also
this
one
and
this
one
and
you
can
see
that
I'm
not
up
to
date
with
the
real
master.
Yet.
A
F
A
Great
yeah,
well
and
and
one
of
the
tricks
that
darren
pope
taught
me
just
during
the
session
he
and
I
were
having
was
this
one
where
I
need
to
remember
periodically
to
go
into
well,
let's
go
here
to
my
github
repository
for
jenkins.io
and
every
so
often
it's
just
good
to
hit
the
see
what's
a
good
choice.
Let's
pick
another
branch
like
this
one
and
then
there
will
be.
Where
is
the
button
that
says
fetch
from
upstream?
Oh,
it's!
A
A
F
A
B
D
Diraj,
not
no,
no,
nothing
on
this
topic
I'll
be
sending
a
pr
just
to
see
if
I'm
able
to
push
or
not
in
this
at
the
same
time,
so
we
can
move
on
to
the
next
one.
A
All
right,
so
next
one
is,
and
I
was
hoping
to
have
other
participants.
The
person
who
is
hoping
for
did
not
actually
arrive,
and
so
we,
let's
discuss
it
briefly.
Anyway,
there
is
a
plug-in
there's.
A
series
of
plugins
called
publish
over
publish
over
ssh,
publish
over
ftp,
publish
over
cfs
cifs
that
are
all
based
on
a
core
technology.
Plugin
called
publish
over
x
and
the
publish
over
x,
plugin.
A
This
one
doesn't
have
its
documentation
here
and
yet
on
the
wiki,
it's
got
pages
and
pages
of
very
useful,
very
valuable
documentation.
That
applies
to
every
one
of
those
other
plugins,
and
so
this
is
a
case
where
we
really
need
a
transition
from
from
wiki
to
this
to
this
github
repository
and
it
has
74
000
installs
exactly
so.
It's
also
a
very,
very
popular
plug-in
right.
So
this
is.
A
A
A
It
well
it's
yeah,
it's
a
it's
a
base,
it's
an
exercise
in
converting
from
from
this
layout
to
ascii,
doc
or
markdown,
and
I
did
get
a
commitment
from
let's
see
so
I
did
get
a
commitment
from
alex
earl.
E
A
Where
was
plugins.jenkins.io,
I
don't
remember
it's
here
to
fix
that.
A
C
Right
and
we've
got
daniel,
I
mean
there's
a
lot
of
security
they're,
getting
the
basic
stuff
done
to
reclaim
what
we've
got
we'll
get
that
done,
and
then
the
security
will
be
ongoing,
but
exactly
yeah.
When
you
mess
with
when
you
mess
with
structure,
you
kind
of
gotta
dig
in
and
get
it
all
done
fast
right,
yep
when
you
release
stuff
around
but.
A
A
A
A
C
A
A
A
A
A
A
A
D
A
A
A
A
A
C
D
So
I
had
a
question
about,
though
that
pulled
request
which
will
be
converted
into
two
separate
change.
Log
entries
so
in
this
one,
as
you
can
see,
the
procedure
is
something
like
this.
That
will
be
waiting
for
the
changelog
to
get
published
on
the
website
and
then
we'll
be
editing.
The
automated
automatically
generated
change
log
and
creating
the
two
entries
because
since
it
has
been
released,
so
bot
will
not
be
you
know
enforcing
its
changes
again.
That's
why
other
changes
will
be
holding
right,
correct.
A
A
B
A
A
D
A
So
so,
and
and
we've
the
the
other
re,
the
other
reviewers
on
jenkins
side,
io,
even
skipping
daniel
will
will
advise.
Please
give
me
sentence
per
line.
A
Is
yeah
ugly?
Well,
actually
I
confess
it's
been
very
helpful
for
me
because
it
it
is
an
immediate
detector
of
run-on
sentences.
I
I
look
at
I
look
at.
I
got
it.
I've
got
a
relatively
wide
screen
and
if
I
ever
rap
on
my
wide
screen,
I
know
that
I'm
clearly
run
on
and
most
of
the
time,
I'll
think
very
carefully.
If
I'm
much
beyond
80
or
90
characters
am
I
running
on.
Have
I
put
three
ands
and
several
several
commas
in
this
thing
that
I
shouldn't
have.
C
A
F
C
Let's
do
the
classify
and
then
I'll,
I
just
copied
you
on
the
incomplete
document
where
I'm
summarizing
what
we're
going
to
do
for
this
structure.
Oh.
C
Later
but
I
got
okay,
those
we
ran
into
we've
got
a
bunch
of
referenced
in
this
stuff
and
daniel's
going
through.
It
says.
Well
that
was
never
here,
that's
a
python
thing.
Do
it
like
you
do
in
python
and
jenkins
will
recognize
it
we
shouldn't
have.
We
shouldn't
have
anything
on
that
in
jenkins,
io
other
a
couple
of
others
said:
that's
a
really
really
narrow
band
of
users
that
use
it.
C
It
shouldn't
be
in
think
his
I
o,
but
I
got
and
then
he
said
well,
you
know
I'll
go
through
him
and
tell
you
what
you
know
well,
there's
a
he
doesn't
know
how
many
there
are
he's
not
going
to
get,
but
I
got
the
let's
say
that
he
starts
going
through.
C
What
is
the
mechanism
for
that
and
the
best
idea
that
I
had
was
to
put
a
little
checklist
at
the
front
of
each
at
the
top
of
each
file
for
each
wiki.
That's
in
that
list
where
so
it
would
be.
You
know
the
dispensations
it
could
be.
You
know
this
is
worth
converting.
As
is
this
is
a
good
topic,
but
the
content
needs
to
be
rewritten.
C
This
doesn't
belong,
you
know
a
couple
of
those
that
and
that
somebody
could
go
through
it
in
the
market
and
then
have
a
comment
and
they
and
put
the
author.
Who
did
it
so
we
could
look
at
it
and
say
daniel
beck
says
this
shouldn't
go
and
a
place
for
a
comment.
C
So
then
somebody
could
say
this
was
incorporated
into
the
user
guide
and
pr
such
and
such
or
you
know
or
whatever
you
know
comments
are
always
handy,
but
would
it
is
there
any
way
to
do
something
like
that
easily
so
that
then,
when
you
generate
your
list,
you
could
search
on
that
and
it
would
knock
out
anything
that
had
you
know
that
somebody
had
marked
as
don't
do
this.
Let
it
die.
A
A
Their
statement
on
the
disposition
of
it
right,
it's
wiki.jenkins.io.
A
Is
flawed
but
worth
keeping
but
worth
rework
or
it
might
be.
C
A
A
C
A
C
A
E
C
Another
thing
what
I
can
see
is
even
if
daniel
hadn't
made
this
offer,
which
I
know
he's
not
going
to
be
able
to
completely
come
through
in,
but
in
doing
this
we're
hitting.
Actually
this
one
we've
got
eight
or
ten
links
that
we
look
at
those,
and
there
might
be
a
couple
of
them
that
I
would
mark
and
say
this
was
incorporated
into
jenkins
io
with
this
pr,
because
it.
C
A
C
A
C
A
Okay,
so,
and
that
that
would
also
work
if
we're
doing
that
annotate
the
the
source
repositories,
the
annotate,
the
confluence
data
files
with
the
same
type
of
info.
That
would
be
great,
but
that's
that's
almost
3
000
files.
C
A
C
No
so.
C
A
C
Yep
well.
C
A
Then
isn't
it
that
we,
we
probably
don't
even
want
it
as
a
classification
comment
in
that
case,
we
probably
want
it
because
right
now,
those
that
confluence
data
is
is
for
me
largely
unusable,
because
it's
rendered
as
raw
html
right,
I'm
not
seeing
those
files
as
their
actual
content.
I'm
seeing
this
html
markup
that
I
just
really
struggle
to
read.
C
C
A
A
A
This
is
how
it
actually
looks
right.
I
think
if
we
wanted
a
comment
here
that
somebody
had
visited
this,
it
should
probably
be
visible
in
this
view
of
the
file,
not
just
in
the
pure
html.
So
rather
than
a
comment,
it
would
actually
be
some.
You
know
a
heading
down
at
the
bottom
that
says
classified
by
so
and
so
or
un
not
yet
not
yet
reviewed.
A
C
Yeah,
so
how
did
we?
Because,
let's
okay-
let's
say
that
one
of
these,
the
information's
good,
it's
a
good
topic,
and
I
say
you
know
and
it
yeah
I
was
linking
to
it
here,
but
I'll
just
move
it
over
to
jenkins
io
to
me,
it
looks
easier
to
take
the
rendered
and
copy
and
paste
the
text
and
just
put
the
ascii
doc
stuff
in.
A
I
agree
for
me
right
now:
that's
now
there
is.
There
is
the
wiki
exporter,
so
there's
the
jenkins
wiki
exporter
here,
which
may
be
able
to
help
us
because
I
think
it
has
whoops.
I
think
it
has
a
facility
to
take
general
a
general
purpose
web
page
to
do
the
wiki
export.
Let
me
see,
though,
okay,
this
is
export.
A
A
No
yeah,
it
doesn't
so
so
it's
it's
got
sanity
checks
in
it,
so
we
don't
have
anything
that
will
do
the
markdown
conversion
for
us
right
now,
but
I
think
if
we
ask
nicely,
we
could
probably
persuade
gavin
mogan
to
help
us
with
that.
If
we
need
it,
if
we
get
lots
of
requests
for
the
short
term.
For
me,
it's
easiest
just
to
read
this
html
and
paste
it
into
ascii
doc.
C
C
C
A
A
C
A
D
Yes
thanks,
so
I
noticed
that
even
after
having
hacktoberfest
label
on
the
pr,
it's
it's
not
still
being
counted,
and
then
I
went
to
the
page
and
read
the
rules,
and
I
think
it
says
that
if
the
project
is
not
participating
and
you
want
your
pr
to
be
counted,
you
need
to
have
the
label
called
hacktoberfest
dash
accepted.
A
D
So
should
I
message
on
the
pr
to.
B
D
A
A
D
That's
a
good
idea,
I'll
check
with
them
today
and
we'll
comment
accordingly.
Thank
you.
C
Just
that
daniel
and
I
are
at
peace,
yeah
and
I
just
copied
you,
the
the
google
doc-
is
not
complete
and
it's
it's
not
being
written
really
for
public
consumption.
It's
kind
of
high
level
to
keep
us
online.
But
if
you
want
to
see
what
we're
up
to.
C
C
C
I
love
working
with
you
know
we
had
this
little
thing,
we
should
talk,
and
so
I
kind
of
written
to
him
I
said:
well,
I
can
do
it
any
morning
this
week,
your
time
and
you
know
about
11
30.
Last
night
I
was
fixing
dinner
and
I
get
you
want
to
do
it
now.
So
I
turned
off
the
stove
and
we
did
it
so
all
right,
but.