►
From YouTube: 2020 05 18 Jenkins Docs Office Hours
Description
Jenkins Docs office hours May 18, 2020
A
Hi
everybody
I'm
mother,
wait:
oh,
go
ahead,
John,
okay!
No!
No!
Just!
Okay!
Sorry
great
I'm
mark
wait!
This
is
the
Jenkins
documentation
office
hours.
It's
a
question
and
answer
session,
where
we'd
like
to
be
able
to
ask,
allow
anyone
to
ask
questions
and
get
answers
about
how
to
create
Jenkins
documentation,
how
to
deliver
it,
how
to
help
it
we'll
be
doing
these
as
long
as
there's
a
need
right
now.
The
plan
is
about
once
a
week
and
delighted
to
host
them
whenever
we
do
adhere
to
the
Jenkins
code
of
conduct.
A
The
Jenkins
code
of
conduct
means
that
we
are
expected
to
be
respectful
kind
and
considerate
to
one
another.
Violations
of
the
code
of
conduct
are
brought
to
the
Jenkins
board
and
handled
there.
So
please,
if
you
feel
uncomfortable
or
uneasy
about
something,
let
me
know
and
we'll
worry
about
it
and
take
care
of
it.
A
So
this
is
being
recorded
thanks
very
much.
First
off
I
was
going
to
give
an
overview
of
materials
of
what
I
had
envisioned
for
office
hours,
and
then
we
can
talk
about.
Is
that
what
you
want
to
do?
Or
would
you
like
to
do
something
different
for
today,
so
I'm
going
to
share
my
screen
and
let's
look
at
what
I've
got
for
a
draft
outline,
so
here's
what
what
I'd
proposed
is:
let's
put
down
who's
attending.
A
There
we
go
so
my
thought
is.
This
is
a
question
and
answer
session.
That's
our
first
and
foremost
objective
here.
Whatever
questions
you
have
of
any
sort,
you're
welcome
to
ask
them,
you
can
ask
them
either
verbally,
you
could
submit
them
as
changes
in
this
document
or
you
could
ask
them
in
chat
in
the
session
one
way
or
the
other.
We
want
to
collect
them
and
and
after
collecting
them
we'll
try
to
answer
them.
I
like
to
do
examples
and
demonstrations
so
that
you
can
see
things
and
get
a
hint.
A
Any
questions
so
far
sounds
no.
No!
No!
So
it's
good
to
meet
you,
alright,
okay!
So
one
question
is:
how
do
I
build
the
Jenkins,
build
the
Jenkins
site
docks
from
source
right?
It's
a
valid
question.
Another
question
might
be:
can
we
have
meetings
at
a
different
time?
I
suspect
there
are
some
contributors
who
may
be
in
Asia
others
who
may
be
in
Eastern
Europe
or
in
Western
Europe,
and
we've
got
people
who
are
willing
to
host
office
hours
during
European
morning
hours.
Olegmon
asha
or
during
the
european
afternoon
noon
or
the
u.s.
A
morning
or
in
u.s.
afternoon
and
even
into
the
evening.
We
don't
right
now
have
anybody
who
is
explicitly
in
what
I
might
call
prime
Asia
like
Beijing
or
Australia
who's
willing
to
host
an
office
hour
there,
but
we've
gotten
most
of
the
24
hours
covered
some
way
right
now
we're
going
to
do
them
at
this
time
and
will
will
adjust
times
as
we
see
a
need
or
cancel
them.
If
we
don't
have
a
lot
of
interest.
A
Another
question
that,
let's
see
other
questions,
what's
google
season
of
Docs
and
that
I
assume
is
an
interesting
one,
because
it's
one
way
to
contribute
to
the
project.
Another
might
be.
How
do
I
get
involved?
Another
might
be
one
of
the
tools
that
I
get
involved
with,
yet
another
might
be.
What
are
the
current
projects
that
the
Jenkins
project
is
working
on?
What
are
the
current
documentation
projects.
A
A
B
Here
is
just
one
of
the
use
cases
which
emerged
just
today.
I
was
working
on
the
Queen
station
for
monitoring
plugins.
Well,
updating
my
current
page,
which
is
hosted
by
Jenkins
IO
and
when
I
am
referring
to
those
plugins
documentation
for
plugins
is
hosted
by
Jenkins
CI
as
I
understand
when
we
change
the
community,
who
is
going
to
change
the
condition
for
specific
plugins
and
how
we.
C
A
A
A
A
A
B
A
A
A
Let's
put
that
one
very
first,
just
as
it
was
because
one
of
the
key
decisions
is
in
choosing
which
who
the
technical
writer
is,
that
would
be
selected
for
google
season
of
dogs
is
how
are
they
interacting
with
the
community
already
so,
let's
talk
about,
how
can
new
contributors
help
first
and
then
we'll
go
into
others?
So
new
contributors
can
help
in
the
with
what
we'd
call
friendly
issues.
A
A
D
B
B
A
A
Okay,
in
addition,
we've
got
the
google
season
of
docs
project
ideas.
A
project
ideas
are
an
important
concept
of
the
google
season
of
docs
process.
They
are
not
a
project
plan.
Yet
a
project
idea
is
a
concept
that
someone
in
the
community
proposes
that
then
a
technical
writer
will
refine
that
that
idea
or
their
own
idea
and
submit
it,
submit
something
that
becomes
their
proposed
plan
and
that's
the
thing
that
Google
season
of
Docs
will
then
evaluate
is
the
plan.
The
ideas
are
just
concepts
or
topics
that
might
be
considered.
A
So
don't
don't
mistake
that,
oh
because
there's
this
this
idea
out
there
that
oh
there
there's
a
whole
bunch
on
it
or
that
I
have
to
do
exactly
that.
No
you're
welcome
to
explore
further
you're
welcome
to
do
propose
something
different.
All
all
are
valid,
so
here's
the
link
to
the
google
season
of
docs
page
and
you
see
the
the
project
ideas.
They
include
things
like
migrating
from
the
wiki
document,
Jenkins
on
kubernetes
lots
and
lots
of
interest
for
Jenkins
on
kubernetes,
but
not
nearly
enough
documentation
on
Jenkins
on
kubernetes
reorganize.
D
Yeah
go
ahead
so
basically,
for
me,
I
mean
I
mean
you
combine
two
one
source
contribution
so
getting
started
for
me
is
kind
of
challenging,
though
I've
been
able
to
clone.
The
document
on
the
web
for
also
status
has
been
kind
of
issue
from
the
adventure
able
to
document.
But
you
know
we'll
explain
for
me
to
get
started
so
I
don't
know.
If
there's
any
help,
anyone
can
bring
that.
D
A
So
that's
the
Jenkins
Jenkins
dogs,
getter
channel
as
people
that
listen
that
watch
it
periodically
and
try
to
help
out.
So
let's
go
there
and
we're
going
to
grab
a
link
to
that
and
I'll
just
paste
it
there.
You
can
ask
questions
directly
in
this,
get
ur
channel
and
to
about
once
a
day
at
least
at
least
once
a
day
I'll
be
on
there.
Others
are
on
there
off
and
on
and
that's
a
great
place
to
ask
a
question.
A
A
Okay,
so
we've
talked
through
how
can
new
contributors
help
if
you've
got
no
other
questions
on
that?
Let's
talk
some
other
topics
like
how
will
technical
writers
be
selected
for
google
season
of
Docs
and
in
order
to
get
to
that
when
I
think
we've
got
to
go
to
the
overview
and
timeline
and
talk
about
the
the
what
things
are
happening
and
when
they
are
happening.
So
what
I'd
say
is
let's
open
up
overview
here
and
make
it
bigger
so
that
I
can
read
it.
A
A
The
ideas
you'll
spend
a
few
months
working
closely
with
a
community
to
bring
your
skills
to
help
the
projects
documentation
and,
at
the
same
time
you
learn
about
that
open
source
project
and
about
some
new
technologies.
So
the
technologies
we're
using
for
documentation
in
our
case
are
centered
around
the
github
workflow,
pull
requests,
asciidoc
and
a
site.
That's
generated
programmatically.
A
So
now,
in
terms
of
what
happens,
the
the
season
of
Doc's
program
organizations
like
Jenkins
apply
to
be
mentor
organizations
with
project
ideas.
We've
done
that
we've
been
accepted
as
a
mentor
organization.
Then
technical
writers
explore
the
organizations
and
choose
projects
that
interest
them,
and
then
you
write
up
a
project
proposal
and
submit
it
to
Google
season
of
Docs
notice
that
this
is
not
me.
Writing
it
up.
It's
you!
So
the
writers
who
want
to
be
in
Google
season
of
Docs
submit
their
proposal
and.
A
C
I
have
a
question
about
this:
top
of
it.
I
can
speak
her,
yes,
yeah
all
right,
so
the
main
idea
is
I'm.
As
a
technical
writer
I
build
a
plan
proposed
a
project
proposed
sent
to
you
and
if
it's
selected
and
we
start
to
work
with
right
but
I,
don't
know
about
the
Jenkins
necessity.
So,
for
example,
include
Google
Seasons
website
I
see
there.
We
have
a
a
plugin
documentation
and
update
necessity
to
be
great,
a
from
the
old
wiki,
I
I,
know,
I,
guess
and
fry
the
new
one
in
Quechua
right.
C
A
D
A
C
A
Embedded
in
the
timeline,
so
so
that's
very,
very
good!
You
hit
you
hit
it
very
well.
The
timeline
will
take
us
through
how
we
get
you
to
that
knowledge
before
you
submit
your
plan,
nice,
okay.
So
what
we
do
is
we're
now
at
May
the
18th.
So
we
are
in
this
period
here
where
we're
in
what's
called
Technical
Writer
exploration.
A
A
It
won't
help
anyone
to
say
that
say
that
so
so
the
idea
is
you
in
this
period
between
now
and
the
8th
of
June
enter
into
discussions,
and
the
discussions
are
typically
done
by
proposing
changes.
You
pick
a
wiki
page
and
you
transform
it
into
Jenkins
dot
IO
or
you
help
with
some
project
on
a
change
of
one
sort
or
another.
A
You
pick
a
bug
report
and
fix
that
bug
and
the
process
of
you
doing
that
work
will
give
you
the
experience
you
need
so
that
you
can
enter
into
this
Technical
Writer
application
period
and
be
ready
to
then
let's
see
some
nets,
so
technical
writer
applique.
Oh
yes,
a
June
8th
to
June
9.
So
if
so
beginning
June
9
starts
the
application
period.
You
have
then,
one
month
to
prepare
your
proposal
in
that
month.
You
continue
contributing
you
continue
exploring.
A
You
continue
looking
at
different
aspects
of
the
project
plan
that
you're
going
to
propose
and
as
you
do,
that
your
abilities
increase
and
you're
able
to
give
a
better
plan
so
that
when
we
get
to
this
July
9
deadline
for
applications,
you've
got
a
good
plan
that
you're
ready
to
submit
for
as
an
application.
I.
C
Get
the
idea,
but
it's
possible.
For
example,
you
were
everyone
that
have
more
experience
with
Jenkins
and
make
a
banner
or
a
collection
of
beginning
stacks
that
desks
for
sample
I
saw
in
the
github.
There
is
a
label
called
newcomers,
issues
for
sample,
but
I
don't
know
what
I
can
pick
or
not,
because
I
know
how
to
use
Esther,
Docs,
Mac
Dao,
a
github
work
process.
Work
show,
but
I
need
to
want
to
start,
because
there
is
a
lot
of
links.
C
D
Yeah,
look
yes,
yeah
like
what
mr.
do
not
Donna,
she
be
said:
the
spy
when
I
actually
clean
the
projects,
I
it
and
I,
have
the
rep
on
my
own
accounts.
So
I
went
through
the
talk,
so
I
was
kind
of
lost,
I,
don't
even
know
where
to
get
started
from
so
now.
Let's
go
back
to
get
all
going
about
to
get
oh
I
went
through
issues,
so
I
see
a
lot
of
issues
on
the
air,
but
why
you
don't
know?
D
Okay,
the
way
am
I
going
to
start
from
even
punitive
the
issues
I
see
a
so
I
think
what
that's
one
of
the
things
we
need
to
break
down
so
that,
as
a
newcomer,
even
coming
for
the
first
time,
I
shouldn't
be
able
to
know
that.
Okay,
the
first
step
is
for
me
to
get
the
a
report
on
me
on
my
own.
Look
how
my
and
she
then,
from
there
I,
proceeded
from
the
okay
right
any
proposed
that
our
entire,
the
next
thing
to
do
and
leave
that
is
not
a
nice
thing
to
do.
A
D
A
Turn
that
key
on
you,
sticky,
cool
all
and
then
here
under
late,
so
you're
the
first
issue
and
you
could
choose
one
of
these
and
the
technique
you
use
is
you've.
Read
it
and
say:
hey.
Is
this,
inter?
Is
this
top
in
topic
interesting
to
me?
If
it
is
interesting
to
you,
you
could
assign
it
to
yourself
by
clicking
this,
assign
yourself
link
that
I'm
hovered
over
that's
saying,
I'm
going
to
assign
myself.
If
you
then
choose
not
to
assign
it,
you
could
give
it
back.
So
it's
okay.
D
A
C
A
C
A
And
and
this
the
good
first
issue
label
is
still
evolving.
We've
got
the
six
right
now
that
are
open
by
the
time.
We
start
the
heck
fix
fest
next
week.
I
expect
to
have
double
or
triple
that
number
available
this.
These
issues
that
you
see
here
have
been
created
by
my
looking
at
the
wiki
pages
to
see
which
ones
need
to
be
translated,
and
many
of
these
are
related
to
that
or
some
other
piece
of
the
projects
needs.
A
A
There
are
many
different
places
you
can
contribute
and
any
one
of
them
will
give
you
experience
in
the
work
flow
and
cause
you
helped.
You
discover
problems
or
things
that
should
be
better
described
or
should
be
help
you
you
should
be
yeah
should
be
described
better
so
that
you
can
contribute
more
effectively.
C
C
A
And
wait
patiently
it
takes
forever
to
load.
So
you
bet
you
see,
here's
the
look,
the
old
thing
where
it
says
this
is
how
I
install
configure
with
some
important
notes
that
are
glaringly
absent
this
the
install
instructions.
I've
migrated
myself,
but
this
piece
is
missing.
So
it's
one
of
those,
oh
okay.
How
would
we
say
that
so
that's
the
from
now
here's
the
so
this
is
the
destination,
and
here
you
see
the
destination.
Is
this
page
on
Jenkins
dot
IO?
A
Where
we're
trying
to
put
it
I,
guess
you
know
now
as
the
as
the
really
cool
secret
where,
but
where
is
this
page
in
the
source
code
right?
Because
it's
it's
all
lovely
but
I
can
see
it
on
Jenkins
that
I,
oh,
but
I,
can't
edit
it
right
on
Jenkins
that
I,
oh
I,
have
to
find
the
source
code
if
I
jump
to
the
bottom
of
this
page,
all
the
way
scroll
down
to
the
bottom.
A
C
A
A
Okay,
so
so
the
the
the
power
of
that
technique
is
there.
There
are
already
tools
that
will.
Let
me
find
this
now
if,
while
you're
reading
and
certainly
you'll
be
reading,
you
may
realize-
oh
here's,
this
mistake
on
this
page
well
notice
here
this
hyperlink
report
a
problem
if
I
click
on
any
page.
So
let's,
let's
choose
a
different
page,
this
time
we're
going
to
choose
the
using
Jenkins
page
on
credentials
and
I
found
a
problem
here.
A
C
All
right
just
anot
another
question
about
the
stock.
Yet,
for
example,
we
are
migrating
all
the
data
from
total
destiny
when
there
is
a
a
step
of
stations
right,
we
need
to
reply
and
reproduce
all
steps,
steps
by
steps
and
but
screenshots
for
sample
will
make
some
videos-
oh
not
just
text
one
well,
so
we.
A
Are
delighted
to
have
screenshots,
we
have
a
few
videos.
We
typically
tend
to
host
our
videos
on
YouTube
and
right
at
a
reference
to
the
video
in
to
our
pages,
the
the
its
most
common
you'll
find
that
most
of
the
documentation
is
very
heavy
on
words,
with
relatively
few
screenshots
and
even
fewer
videos.
A
C
A
D
D
I'm
just
thinking
a
long
way
explaining
every
of
these
things-
okay,
let's
say,
for
instance,
the
process
we
have
on
the
wiki
page,
which
is
the
old
fashioned
of
the
documentation
right
so
and
we
are
trying
to
migrate
it
to
the
jackings
Docs
Isle,
which
is
the
current
one.
We
are
walking
on
so
I'm
thinking.
Well,
the
processor
is
in
the
old
fashion,
which
is
in
the
wiki
page.
There
is
a
kind
of
breakage
like
something
breaks,
maybe
the
installation,
the
only
lovin
we
keep
eat
is
the
old-fashioned
package.
A
So
one
way
is
to
assume
that
what's
written
on,
the
wiki
is
correct
and
place
it
into
the
new
page
and
then
allow
the
code
review
process
to
tell
you
that.
Oh
that's
not
not
right.
That's
that's!
Certainly
one
way
to
do
it.
The
other
is
try
it
yourself.
If
you
have
access
to
a
to
the
the
right
computer,
you
should
by
all
means
try
to
do
what
the
thing
is
that
you're
documenting.
A
You
can
also
be
comfortable
and
confident
that
there
are
others
who
will
review
the
documentation
that
you're
proposing
and
we'll
give
you
some
back
on
it
now
if,
at
least
for
me,
I
find
it
I
find
it
I
would
like
the
original
submitter
to
have
done
the
work.
They'd
I
think
they
could
do
so.
For
instance,
if
you
write
something
and
it's
clear
that
you
you
had
access
to
something
that
could
test
it
and
you
never
tested
it
I
find
that
not
as
helpful.
If
you
can
test
it,
you
should
test
it.
B
First
of
all,
there
is
the
communication
on
Jenkins
dot
IO
about
the
projects
which
are
part
of
hacker
fest,
which
will
start
in
one
week
are
those
projects
or
ideas,
and
this
is
the
question
related
to
time
frame,
because
when
we
looked
at
Google
Doc
about
GES
OD,
the
time
frame
for
selecting
projects
and
the
mountain
projects
was
middle
of
August,
and
our
page
tells
that
this
project
are
already.
We
have
several
projects
for
recommendation,
so
are
those
projects
or
ideas,
and
just
so.
A
Is
correct
so
these
and
and
I
like
that
phrasing,
that's
a
very
good
way
to
phrase
it.
Let's
drop
the
word
project.
These
are
just
ideas
or
concepts
that
have
been
tossed
out
as
clear
needs
by
people
who
are
participants
in
the
Jenkins
project
and
in
Jenkins,
but
they
are
not
staffed.
They
are
not
in
any
condition
of
permanent
ongoing
effort.
People
in
the
pod
in
the
Jen
Jenkins
make
progress
on
them
when
they
feel
like
it,
and
they
don't
make
progress
on
them
when
they
don't
feel
like
it
and.
B
A
Money
compensation,
good
good
question,
so
the
the
I
believe
Google
season
of
dogs
has
a
compensation
portion,
although
I
have
not
done
the
research
on
it.
So
let's
take
a
quick
look
at
it
and
see
if
we
can
find
that
just
a
moment,
because
I
know
Google
Summer
of
Code
with
the
university
students
that
runs
just
over
the
summer
time
does
in
fact
compensate
the
contributors.
It
compensates
the
students.
Let
me
double-check,
this
I
think
that
let's
see
Google
season
of
docs
google
season
of
dogs.
A
A
B
A
B
On
mentoring,
I
know
that
Jenkins
project
Jenkins
project
organization
can
be
selected
as
mentor
organization,
but
individual
matters
are
those
maybe
not
necessary
technical
writers.
They
may
be
as
I
understand
software
engineers,
programmers
or
just
regular
people
willing
to
help.
You
have
some
experience
and
is
there
any
kind
of
compensation
for
people
for.
A
Mentors
I
don't
believe
there
is
I'm
not
aware
of
any
compensation
for
mentors.
It's
it's
as
far
as
I
know
entirely
part
of
the
it's
just
assumed
that
they're
part
of
the
project
and
therefore
Google
season
of
Docs
definitely
has
no
contribution.
Konk
no
payment
to
mentors
and
I
see
nothing
here
on
season
of
Docs
either
so
mentors
are
not
compensated
and
to
just
for
precision
the
mentors
in
general
will
not
be
technical
writers,
because
we
don't
have
many.
A
We
don't
have
any
dedicated
technical
writers
that
that's
all
they
do
on
the
project.
What
we
have
are
people,
like
me,
let's
see
15
years
as
a
manager
in
technology,
some
years
as
a
programmer,
etc,
but
and
I
speak
English.
But
that's
about
the
limits
right.
Calling
me
a
technical
writer
is
I've
created,
training,
I've,
presented
training,
but
I'm,
not
a
technical
writer
I'm
happy
to
write
I
write
because
it
helps
so
did
that
answer
your
question,
but
absolutely
yes,.
B
B
A
Amazon
provides
funds,
provides
credits
or
a
portion
for
the
three
years
prior
to
up
until
December
of
2019,
Microsoft
Azure
provided
credits
through
December
2019
and
so
those
those
donors,
and
we
have
hoped
that
someday
Google
will
provide
or
maybe
IBM
cloud
so
donors
provide
the
infrastructure.
Currently
Azure
is
the
host
or
Jenkins
Aveo
at
the
moment,
and
for
CI
that
Jenkins
that
IO,
the
master,
AWS
hosts
CI
de
Jenkins,
that
IO
agents
and
we
may
move
things
around
based
on
who's
willing
to
fund
us
and
how
they're
willing
to
fund
us.
B
And
thank
you
very
much
for
answering
and
also
related
to
this
question
about
creating
accounts
on
those
public
providers.
Those
accounts
donated
by
those
crystalline
organizations
and
in
case,
if
contributors
or
mantras
or
technical
red
well,
some
people
contributing
to
the
Jenkins
project
would
like
to
test
our
hosting
deployment
oldest
recommendation
on
specific
our
cloud
provider.
How
can
they
proceed
without
having
an
account
or
what
should
be
helicoptered.
A
B
A
Without
becoming
an
infrastructure
administrator
and
I'm
hesitant
to
give
anybody
in
for
admin
capabilities
that
doesn't
absolutely
require
it,
we've
had
we've
had
one
too
many
places
where
people
used
some
unsecure
Jenkins
instance
on
the
public
Internet
to
crypto
mine,
to
go-go
computing
Bitcoin,
or
something
and
we'd
rather
not
have
that
our
infrastructure
used
that
way.
Yeah.
A
Yeah
so
immediately
its
you
should
expect
that.
Well,
in
fact,
I
had
it
just
today,
Jenkins
to
237
was
released
this
morning
and
the
Jenkins
changelog
for
that
release
had
not
yet
been
published.
I
published
it
and
30
or
45
minutes
later
or
I
I
merged
the
pull
request
on
Jenkins
that
IO
30
or
45
minutes
later
it
was
visible
on
the
actual
production
site.
A
B
C
B
Just
a
related
question:
maybe
if
nobody
else
question
just
to
continue
discussion?
Oh,
when
we
can
control,
we
contribute
to
the
code
to
the
commutation
its
merged.
In
this
result,
we
can
see
on
Jenkins
I,
oh,
how
it
is
related
to
and
Jenkins
dot.
Io
I
guess
is
the
part
of
their
product.
Documentation
goes
with
the
product,
I
guess
right
how
it
is
related
with
their.
B
A
A
A
So
so
the
example
for
me
is
if
I
look
at
my
my
J
conserver,
that's
here
on
in
my
environment,
when
I
look
here
at,
let's
pick
something
that
needs
help.
How
about
I've
got
a
failing
test,
a
failing
job
on
the
Jenkins
gif
client?
Oh
I,
don't
how
about
an
unstable
one?
Here's
one!
This
thing
is:
has
some
tests
that
are
failing
and
if
I
want
to
know
something
about
it,
I
can
find
when
I
click,
how
I
need
to
pick
a
different
job.
A
Let's
pick
this
one
I
click
this
one
when
I
click
configure
it's
going
to
bring
up
a
panel
with
a
bunch
of
question
marks
on
it
for
help
like
this
little
question,
bar
I
just
went
off
screen
now
we
have
to
shrink
the
Jenkins
user
interface
is
getting
work,
and
this
is
a
hint.
Why
see
this
question
mark
over
here
on
the
right?
A
Yes,
absolutely
all
right,
so
we
will
do
this
again
next
week.
I
will
stop
the
session
now
and
post
a
copy
of
the
recording
thanks
very
much
for
your
time.
Look
forward
to
see
you
on
the
git
er
Channel.
Remember
that
the
git
er
channel
is
here,
it's
called
Jenkins
CI,
slash,
Docs
and
I'll
send
each
of
you
a
copy
of
the
notes
so
that
you've
got
a
link
to
them.