►
From YouTube: 2020 06 01 Jenkins Docs Office Hours
Description
Jenkins documentation office hours Jun 1, 2020.
A
This
computer
and
you
should
each
have
seen
a
prompt
that
says
that
we're
being
recorded
thanks
for
joining
Jenkins
Doc's
office
hours,
we're
governed
by
the
Jenkins
code
of
conduct,
so
be
nice
to
each
other.
If
someone
were
to
interrupt
the
session
or
become
aggressive,
etc,
we'll
just
end
it
it's
it's
very
simple
for
for
this
particular
meeting.
If
someone
zoom
bombs
us
or
something
like
that,
would
just
stop
the
meeting
and
it'll
end.
C
C
C
A
Yes,
I
think
it's
good,
it's
good
for
people
to
see
what
how
how
project
plans
are
evolving,
how
people
are
developing
ideas,
what
techniques
they're
using!
We
should
probably
also
look
at
the
google
season
of
docs
documentation
that
says
how
things
should
be
formatted
it's
or
how
they
should
be
structured,
etc.
C
A
A
A
C
So
this
is
agenda
that
I
proposed
about
talking
about
application
process
for
google
season
of
dogs
and
also
just
a
precaution
to
discuss
well
the
process.
How
different
applicants
should
go
about
this?
What
they
should
do
in
case
they're
interested
in
participating
in
this
program?
Who
is
sponsoring
this,
and
also
they
do
have
some
time
for
Q&A
session
in
case.
B
B
A
C
B
C
A
A
C
So
I
highlighted
just
I'm
commenting
if
it's
okay
with
everybody
about
my
ideas,
I
proposed
in
this
English
document.
This
is
what
how
everybody
who
is
interested
in
this
product
or
project
what
they
should
do
explore
Google
sees
no
dockside.
This
site
is
provided,
and
here
is
there
a
reference
to
this.
To
this
side,
the
site
is
managed
and
proposed
by
Google
themselves.
C
A
C
This
is
a
sponsor
of
our
google,
seasonal
dogs
and
I
am
proposing
and
like
every
participant
to
review
project
ideas
here,
of
course,
and
see
how
they
fit
in
this
project
ideas
or
if
they
want
to
add
to
these
ideas,
and
also
there
is
one
issue
that
I'm
proposing
but
I'm,
not
sure.
If
this
is,
we
should
include
this.
The
new
participation
and
this
in
this
dog,
seek
there
is
list
of
participants
are
all
the
people
listed
here
should
be
eligible
to
participate
in
the
google
seasonal
dogs.
Or,
should
we
update
this
list?
A
I
I,
don't
think
it
matters
those
participants.
Probably
none
of
them
are
actually
eligible
to
participate
in
google
season
of
Docs,
because
those
participants
are
all
already
active
participants
in
the
Jenkins
project
and
they're
already
there
they're,
not
in
the
sense
of
professional
technical
writers
who
would
be
getting
a
new
experience
by
doing
open
source.
Most
of
them
are
either
somehow
involved
in
the
Jenkins
project
or
somehow
involved
with
companies
that
are
actively
selling
products
based
on
Jenkins
I.
C
Okay,
so
I'm
just
replacing
this
very
high
participation,
just
by
exploring
this
page,
which
tells
about
the
process
and
also
after
that,
explore
this
getting
started
page.
What
to
do,
which
describes
the
process,
basically
how
to
apply
for
this
I
selected
for
myself
well
kind
of
proposing
the
projects
that
I
would
be
interested
in
working
and
just
trying
to
get
feedback
from
the
panel
and
I
can
just
share
my
interests.
I'm
interested
in
working
on.
C
Well,
integration
between
Jenkins
and
rocker.
There
are
so
many
different
ways
to
integrate
to
integrate
this,
and
it
looks
that
it
may
be
part
of
solution.
Page
I
started
modifying
this
page
also.
There
is
some
documentation
about
installing
Jenkins,
docker
and
sorry
and
different
platforms
on
which
it
can
be
installed.
Also,
you
just
probably
need
to
clarify
how,
on
which
platforms,
which
exactly
solution
we
need
to
concentrate
I
need
to
concentrate
in
case
if
I
would
be
allowed
to
work
on.
C
Solution
page
I
would
like
to
well
create
some
project
in
github
previous
documentation.
Readme
file
do
oedema
and
document
this
in
tutorial
and
administration
is
like
in
case.
If
we
need
to
do
some
more
stuff,
it
is
a
very
large
topic,
of
course,
so
we
need
to
focus,
that's
and
just
share
in
my
my
own
interest
and
how
I
would
like
to
address
all
different
like.
C
C
A
D
Okay,
okay,
yeah,
oh
actually,
I
had
a
question
like
if
I
found
find
any
interesting
area
of
plugin,
then
I
work
on
that
specific
plugin
working
closely
with
the
maintainer
of
the
second.
So
should
I
contact
that
maintainer
personally
or
like
in
so
that
context
that
maintainer
of
the
second
or
like
how
to
get
started
with
working
with
maintainer
of
the
second.
A
D
I
basically,
the
second
reason
and
the
question
okay,
so
the
project
which
is
needs
to
be
bring
up
should
be
like
in
focus
on
a
single
section
of
the
plugin
documentation.
Letters
should
be
focused
on
an
specific
area
or
the
specific
plugin
like.
Oh,
you
should
be
documenting
on
a
single
looking
or
it
could
be
my
different
plugins
that
would
be
and
documented
as
a
part
of
the
project.
A
Okay,
so
so
I'm
not
sure
I
was
quite
understanding.
There
I
have
personal
biases,
making
assumptions
about
what
I
think
you
were
saying,
I,
for
instance,
for
me,
Thea
one
of
those
project.
Ideas
might
be
something
like
better
describe
how
to
use
Jenkins
very,
very
well
with
github
how
to
use
Jenkins
very,
very
well
with
bitbucket,
which
is
a
those
two
are
stories
that
require
a
a
collection
of
plugins,
not
a
single
plug-in,
but
they
have
an
entire
use
case
associated
with
them.
A
D
A
A
It
is
perfectly
reason
we
have
a
github
solution
page
and
then
looked
at
ways
to
expand
and
broaden
that
you
would
probably
also
look
for
places
in
the
Jenkins
documentation
set
the
handbook
where
you
could
insert
a
description
of
the
entire
github
experience,
how
to
use
application
authentication
how
to
use
the
organization
folders
how
to
use
pipeline
well
and
multi
branch
pipelines
those
those
kinds
of
things
how
to
use
web
hooks.
So
those
sorts
of
things
would
all
be
very
good
candidates
to
propose
in
that
kind
of
a
project
plan.
D
A
A
B
A
And
if,
as
I
understand
it,
they
intentionally
give
us
one
month,
because
the
idea
is
you
will
you
will
begin
drafting
your
plan
and
you
will
share
it
with
the
Kijang
khun's
community
and
community
participants
will
give
you
feedback
on
your
plan
so
that
you
can
use
it
to
use
their
feedback
to
improve
and
refine
your
plan.
So
and
yes,
you,
if
you
instead
say
oh
no
I'm,
going
to
keep
my
plan
to
myself
and
I'll,
submit
it
to
Google
and
that
I
am
confident.
A
B
Right
I
I
was
thinking
security
and
propose
about
create
a
beginning
section
section
of
content
to
people's
like
me
to
person
like
to
me
that
are
starting
to
help
communities
like
Jenks
and
where
I
can
show
how
construct
the
environment,
for
example.
Why
intervals
to
use
the
may
current
comment
inside
the
windows?
So
I
can
make
videos
and
the
tutorial
stays
in
the
inside
a
web
page
to
help
someone
to
start
right,
and
it's
a
a
one
section
in
there.
Other
section
I
think
about.
B
A
A
Many
pages
are
wrong.
This
is
it's
an
embarrassment,
but
but
we
had
one
that
that
daniel
beck
noted
just
today,
hey,
look
here's
this
page
that
just
has
completely
wrong
information
in
it.
We
we
migrated
it,
but
it's
no
longer
remotely
accurate,
so
so
so
that
it's
an
interesting
complication
of
these
migration
migrating,
something
that
may
have
been
accurate
ten
years
ago
or
five
years
ago
when
it
was
created,
but
the
product
has
evolved
and
it's
no
longer
accurate.
So
that's
a
good
one.
Okay,
yeah.
B
E
A
C
A
So,
let's,
if
we
could,
if
you
could
bring
project
ideas
to
the
top
of
the
page
so
that
we
can,
we
could
just
be
sure
that
we
talk
through
that
one
so
proc
are
I,
think
had
talked
to
plug
in
documentation,
migration
and
update
and
that
that's
we've.
We've
got
lots
of
work
to
do
there
right
because
we
have.
We
have
migrated
the
documentation
for
about
420
plugins,
so
there
are
only
about
1200
plugins
yet
to
migrate.
A
A
So
this
might
be
a
place
where
proc
are,
you
might
say,
I'm
interested
in
software
configuration
management,
plugins
and
getting
them,
and
you
will
find
from
20
to
50
or
more
plugins
that
are
related
to
suffer
configuration
management.
There'll,
be
the
the
get
plugin
the
github
branch
source
plug-in
the
github,
the
branch
strategy,
branch
strategies
plug-in
all
sorts
of
different
plugins
and
in
that
area
improving
their
documentation.
A
One
plug-in
at
a
time
would
be
a
very
viable
project
yeah,
so
so
that
that
makes
that
one
interesting
yeah,
that's
the
next
one
down
document
Jenkins
on
kubernetes.
That
one
has
a
has
a
challenge
that
you'd
probably
need
access
to
a
communities
cluster.
If
you
don't
already
have
access
to
a
kubernetes
cluster,
as
provided
by
an
employer.
You
probably
need
to,
in
your
project
plan
proposed
that
the
Jenkins
project
or
someone
else,
funds
you
access
to
a
kubernetes
cluster,
and
this
one
is
certainly
very
popular
right
now.
A
C
A
Well,
so
so,
both
because
I
can't
predict
where
the
sponsorship
will
be
will
arrive
and
I,
don't
pretty
I
can't
predict
who
will
provide
it.
I
would
assume
that
you
need
sponsorship
somewhere,
because
telling
telling
a
technical
writer,
oh
google
season
of
Docs,
is
going
to
pay
you
the
equivalent
of
up
to
six
thousand
US
dollars
and
they've
got
a
calculation
method,
but
you're
going
to
have
to
use
one
thousand
or
two
thousand
dollars
of
that
for
your
kubernetes
cluster
during
the
development
period.
That's
probably
not
what
Google
intends
and
so
I
would
guess.
A
D
B
A
And
that
I
know
that
they
gave
me
and
that's
that's
a
place
where
it's
probably
worth
contacting
them
to
ask
saying:
hey
I
am
I,
am
proposing
a
project
to
Google
season
of
Docs.
I
would
like
to
ask
for
your
sponsorship
to
provide
cloud
compute
resources
so
that
I
could
do
kubernetes
based
documentation.
A
A
So
then,
the
next
topic
down
the
Jenkins
user,
documentation,
organization,
reorganization
and
update.
This
is
right.
Now
we
have,
we
have
a
single
large
document,
which
is
the
Jenkins
handbook
and
what
we've
realized
as
we
look
at
it
is.
There
are
some
large-scale
themes
which
might
justify
two
different
things
there
we
might
have
a
using
and
an
administering
the
other,
that's
highlighted.
So
one
project
idea
might
be
split.
This
thing,
which
is
very
large
into
two
smaller
things.
A
The
the
other
might
be
to
say,
oh
I'm,
going
to
dramatically
improve
move
areas
of
intense
interest,
and
if
we
look
at
the
feedback
from
the
jenkin
from
the
Jenkins
I/o
site,
we
have
feedback
pages
that
come
in
to
a
spreadsheet
in
large
volume,
and
we've
gathered
that
feedback
now
for
multiple
years
and
in
that
feedback,
page
you'll
see
all
sorts
of
interesting
comments.
Some
of
them,
rather
rather
direct
very
pointed
some
of
them
laced
with
profanity,
but
by
people
who
say
hey
I
would
like
something
different
than
what
the
current
documentation
is.
A
Going
to
I'll
paste
a
hyperlink
to
the
sheet
into
our
our
notes
here.
So,
let's
see
I
had
it
somewhere
here
mentioned
it
was
others,
documentation,
feedback,
page
and-
and
there
are
times
it's
quite
painful-
to
read
this
page
as
a
plug-in
maintainer,
because
this
is
where
I
learned
repeatedly
that
people
wanted
more
examples,
more
examples
and
more
examples,
and
they
just
they
repeatedly
hammer
and
and
I
thought,
come
on.
It
can't
be
that
hard,
but
obviously
they
were
they
were
telling
how
what
their
experience
was.
A
It
is
that
hard
they
needed
those
examples,
yeah
so
Vlad.
This
page
is
the
hang
your
head
in
shame
page,
sometimes
for
me,
because
there
are
places
where
it
tells
me.
The
documentation
is
not
adequate
here
or
not
adequate
here
and
if
you
scroll
to
the
bottom
of
it,
you'll
see
that
there
are
over
800
items
of
feedback
collected
across
two
and
a
half
years.
B
F
F
A
That
that
might
be
one
project
plan
idea
is
I
want
to
the
the
concept
I
would
have
it
is.
You
would
read
the
documentation,
feedback
and
use
your
reading
of
feedback
to
create
for
you
an
idea
of
what
the
readers
have
most
wanted,
and
then
you
propose
in
your
project
plan
based
on
the
feedback
from
readers.
The
project
plan
says
we
should
do
this
and
you
choose
your
theme
that
way
and
propose
your
plan
that
we
will
improve
this.
So
my
observation
was
the
thing
that
most
stuck
was
most
visible
to
me.
A
A
Okay,
so
so
we've
now
talked
about
Jenkins
user
documentation,
reorganization
and
update.
Another
would
be
create
new
solution
pages
and
Vlad
if
you'll
click
the
solution,
pages
link,
that's
in
the
right
hand,
column
of
that
of
that
row.
It'll.
Take
us
to
this
solution
pages
highlights
that
there
are
many
many
different
ways
that
people
use
Jenkins
to
do
interesting,
work
embedded,
for
instance,
lots
of
people
use
it
and
we'll
have
an
upcoming
webinar
actually
on
people
using
for
field
programmable
grid,
arrays,
FPGAs
and
other
hardware
based
solutions.
A
Yeah
there
we
go,
we've
got
a
tutorial
on
how
you
might
use
it
with
National
Instruments
LabVIEW,
so
people
use
Jenkins
for
all
sorts
of
automation,
not
just
pure
Java
software
developer.
You
know
suffered
creation
they've,
they
use
it
for
C.
They
use
it
for
C++.
The
Eclipse
Foundation
uses
it
to
develop
IDs.
A
Now
those
are
just
ideas,
that's
that's
the
list.
That's
there
and
more
could
be
added
there.
Your
plan
take
something
should
take
something
that
is
important
to
you,
that
you
feel
like
hey.
I
could
add
real
value
there,
and
you
propose
a
plan
which
describes
how
you
will
improve
that
area
or
that
thing
in
the
Jenkins
documentation.
A
D
A
A
I
think,
ultimately,
the
Jenkins
project
has
only
been
allocated.
One
google
season
of
Docs
lot
I
may
be
wrong.
There
may
be
one
also
for
Jenkins
X,
but
I
think
all
we've
been
allocated
is
one.
Let
me
double
check
and
read
the
announcement
that
we
had
I
think
it
was
that
we
were
granted
one
now
they,
you
should
be
aware,
Google
season
of
Docs.
This
is
only
its
second
year
and
they
are
only
accepting
50
writers
worldwide
into
the
program.
A
A
A
A
Yeah,
actually
it
doesn't
state
it
so
Vlad
I
may
be
wrong.
It
might
be
that
there
are
two
I
was
aware
of
one
here.
Is
our
google
season
of
docs
application
and
oh
no,
no,
it's!
Okay!
It
is
one
right.
Okay,
so
I
can
I
could
share
it
or,
if
you'll,
open
Vlad.
If
you'll
open
up
the
Google
season
of
Doc's
page.
C
A
This
one
on
this
page
down
at
the
bottom
is
our
google
season
of
Doc's
2020
application
under
the
technical
writers
heading
the
very
bottom
link
under
the
technical
writers
heading
this
one.
Yes,
that
would,
if
you
click
that
one
and
jump
to
the
very
bottom
of
that
page
you'll
see
it
says
how
many
technical
writers
does
your
organization
want
to
mentor
this
year
and
the
answer
is
one.
F
B
A
A
G
A
And
that's
that's
part
of
the
part
of
the
motivation
for
these
office
hours.
Discussing
google
season
of
Docs
is
in
fact
exactly
that
there
are
some
some
details
of
the
google
season
of
Doc's
program
that
it's
important,
that
you
as
potential
writers
need
to
review
that
in
in
quite
a
bit
of
detail
and
after
having
reviewed
it
in
detail,
then
you
can
say
all
right
now
that
I've
heard
read
this.
What
does
that
mean
and
talk
to
the
the
project
about
what
that
means?
In
our
context,
all.
C
C
A
And
the
guides
the
guides
are
the
ones
that
you
should
read
and
it
would
I
would
counsel
you
to
read
them
carefully,
particularly
for
the
for
technical
writers
section,
so
the
technical
writer
guide
and
the
creating
your
application.
Those
things
describe
the
expectations,
the
form,
the
content
of
the
rough
size
of
the
thing,
because
what
their,
what
their,
what
their
goal
here
is
to
create.
Have
you
create
something
that
created?
A
That
is
a
significant
value
to
the
project
that
you're
helping
and
therefore
they
want
it
to
be
at
least
three
months
of
work
and
they're,
assuming
that
you'll
be
on
it
for
from
10
to
20
hours
a
week
for
those
three
months?
Now
it's
not
assuming
that
you're
on
at
40
hours
a
week.
So
so
they
don't
assume
that
you
are
full-time
on
this.
They
assume
that
you're
probably
employed
doing
something
else,
but
you're
contributing
your
time
to
help
mm-hmm.
A
A
A
The
very
good
question,
one
of
the
the
creator
of
the
plugins
Jenkins
thought,
IO
site,
asked
and
received
permission
to
capture
the
Apache
access
logs
on
the
wiki
site.
He
captures
them
and
he
counts
the
access
by
page
by
day,
and
he
writes
a
report
with
those
I've
captured.
Those
reports
I
captured
him
at
the
time
of
this
thing,
was
generated
for
over
80
days
and
so
that
the
access
count
column
that
you
see.
There
is
the
number
of
times
that
page
was
accessed
in
the
in
that
80
day.
A
Sample
window,
so
hottest
pages
went
to
the
top
of
the
list.
Coldest
pages
went
to
the
bottom
of
the
list
pages
that
got
no
access
in
those
80
days
and
I'm.
Sure
there
are
there
are.
Those
kind
of
pages
did
not
appear
on
this
list,
so
there
are
still
some
pages
that
won't
be
that
aren't
on
the
list
to
be
translated.
A
A
So
if
you're
interested
in
this
theme
in
this
as
a
possible
project
idea,
you
could
begin
reviewing
these
kind
of
these
issues
and
are
these
wiki
pages
look
at
the
Jenkins
documentation
and
propose
where
you
think
this
wiki
page
should
go
in
the
Jenkins
documentation?
It's
very
much
a
learn
enough
about
the
Jenkins
documentation
structure,
to
propose
where
a
page
you
found
here
should
go
there
and-
and
there
are
there
are
times
when
that
is
astonishingly
complicated.
A
So
as
an
example
on
the
page
that
Vlad
has
visible
right
now,
look
highlight
row
number
23,
Vlad
Jenkins
behind
an
engine,
X
reverse
proxy
wow,
that's
a
pretty
technical
thing!
Okay,
that
nginx
is
a
web
server,
but
there
are
five
or
six,
or
maybe
seven
or
eight
pages
that
are
related
to
that
topic.
That,
ultimately,
have
all
been
added
into
a
single
github
issue.
A
So
if
you
click
that
github
issue
it'll
take
us
to
issue
three,
two
zero
four
and
three
two
zero
four
is
is
already
being
worked,
but
this
one
has
one
of
my
former
colleagues
as
a
major
contributor,
because
he's
worked
in
reverse
proxies
for
a
significant
portion
of
his
professional
career.
So
this
kind
of
thing
is
an
example
of
one
of
the
more
complicated
topics
around
a
meg
for
your
info.
It's
Damien
who's
working
on
this,
these
assisting
as
a
reviewer.
A
You
should
the
triage
sheet.
You
probably
only
have
read
access,
but
you
should
have
read
access.
Jonathan
could
I
make
a
copy
to
me:
okay,
yeah
I,
just
what
you
do
is
if
you'll,
if
you
will
propose
changes,
if
you
start
triaging,
something
and
say,
hey
I
then
propose
your
change
right
into
that
sheet.
So
then
I
know
not
to
triage
something
you've
already
triaged.
C
A
Sure,
well,
and
and
and
I
would
even
propose
we
let's
put
that
one
Eve
at
the
top
of
next
week's
agenda,
so
that
we
can
discuss
it
in
more
detail,
because
it's
one
where
we're
I
think
you
as
writers
need
to
be
aware.
Oh
here
are
these
details
that
need
to
happen
and
I
need
to
I
need
to
propose
this
and
I
need
to
tell
this
about
myself
and
I
need
to
describe
this.
C
A
A
A
It
is
right
there
documentation
so
plug
in
Doc's
migration
to
github
Doc's
migration
to
Jenkins
that
I,
oh
yeah,
so
those
links
will
take
you
to
pages
that
describe
other
pieces
of
them,
Jenkins
on
kubernetes
Administrator,
guy
user
guide,
improvements
and
solution
pages.
So
the
topics
that
we've
discussed
today
are
actually
already
on
the
roadmap.
I.
C
C
Time,
but
it
was
like
referring
to
this
section
documentation
we
share
first
to
this,
and
also
we
have
under
Jenkins
is
the
way
we
have
google
seasonal
Doc's
here
so
kind
of
where
should
would
be
like.
Should
every
person
interested
in
this
program
should
look
under
this
or
under
the
condition?
Well,
this
is
something
we
can
discuss
next
time,
great.
A
You
thank
you
very
very
much.
We
will
meet
again
next
Monday
at
this
same
time.
If
you
would
like
to,
if
you
have
questions,
you
are
welcome
to
ask
them.
In
the
Gitter
channel,
the
the
git
er
Jenkins
/
Doc's
channel
you're,
welcome
to
ask
them
on
the
Jenkins
Doc's
mailing
list.
You're
welcome
to
ask
them
all
sorts
of
well.
Those
are
the
two
best
places
and
let's
prefer
those.
A
If
you've
got
questions
about
a
specific
platform
topic,
you
could
ask
in
the
platform
sig,
but
the
Jenkins
Doc's
get
her
Channel
and
the
Jenkins
docs
mailing
list
don't
be
shy.
Larry
and
I
had
a
great
session
on
Saturday,
going
through
a
tutorial
on
ways
to
interact
with
git
and
make
your
documentation
development
more
effective.