►
From YouTube: 2020 07 20 Jenkins Docs Office Hours
Description
Jenkins Docs office hours July 20, 2020 with topics including Google Season of Docs, a detailed review of alternatives for an introduction page, and more
A
A
B
B
A
C
There's
all
those
specific
things
but-
and
the
thing
I
see
coming
in
is
you
can
edit
the
config.xml
file
and
we
have
configuration
as
code
now
and
there
may
be
some
other
options
just
sort
of
a
high
level.
The
specifics
may
be
covered,
but
oh
that
could
be
yeah
so
good.
I
can't
tell
you
how
long
I
was
writing
about
jenkins
before
I
figured
out
about
the
config.xml
and
I
still
don't
know
all
about
it.
Well,.
C
Very
to
say
that
there
are
these
two
options
and
that
there's
some
things
you
can
do
in
one
that
you
can't
do
in
the
other
and
and
then
to
say
that
the
specifics
about
configuring,
each
individual
component
are
going
to
be
embedded
in
the
dock.
For
that
component
yeah.
I
think
it's
a
good
call,
sorry
mark.
A
No,
no,
that
I
think
you
make
a
good
point.
This
could
just
be
an
introduction,
I'm
not
sure
I
agree,
I'm
entirely
aligned
with
your
your
separation,
of
which
things
it
should
introduce.
I
think
it
would
introduce
the
concept
that
jenkins
is
a
profoundly
configurable
system
right.
It
can
be
configured
to
do
all
manner
of
things
and
in
in
many
different
ways,
and
it
can
be
configured,
and
so
this
might
this
page
might
introduce
the
concepts
that
are
involved
in
the
configuration
of
jen
jenkins,
where
those
concepts
are
can
be.
C
C
A
A
I
I
like
that,
that's
a
very
good
point
so
so
this
might
be
an
excellent
place
to
put,
and
several
a
few
say
three
or
four-
maybe,
but
not
more
than
that
introductory
paragraphs
that
introduce
the
various
configuration
concepts
and
then
then
jump
to
details
of
those
concepts.
So
what's
a
tool,
that's
an
important
concept.
Yes,
what's
a
plug-in,
that's
an
important
concept
might
jump
to
the
plug-ins.
A
How
do
you
configure
security
or
what's
what
is
security?
What
are
you
securing
in
the
context
of
jenkins?
So
I
think
I
think,
there's
some
what's
an
agent
or
a
node,
and
so
so
yeah.
I
guess
I
guess
this
could
be
an
intro
or
back
to
the
history
of
it
still
is:
there's
not
a
there's,
never
been
any
content
placed
here.
A
B
B
C
We're
looking
at
something
that's
more
high
level,
just
at
a
high
level.
What
does
it
mean
to
configure
jenkins
that
you
do
a
lot
from
the
ui?
You
do
some
from
cli
we've
now
got
configuration
as
code
that
it
is,
as
mark
said,
that
it
is
highly
configurable
that
there's
very
little
in
it
that
you
cannot
control
almost
sort
of
that
high
level.
There's
managing
the
system
and
configuring
jenkins
is
a
small-
is
a
subset
of
managing.
A
D
E
C
D
C
C
C
Oh
mark
the
fact
that
whatever
you
see
on
any
of
these
configuration
screens
may
change
depending
on
what
plug-ins
you
install
that
most
plug-ins
start
adding
stuff
to
your
config
screens,
and
that
was
to
me
that
was
shocking.
When
I
first
I
came
from
operation
systems,
you
know,
and
you
kind
of
had
your
operation
system
configuration
that
didn't
change
a
lot,
and
then
you
got
into
all
the
other
stuff
that
you
could
configure,
but.
A
B
C
C
Another
thing
just
to
mention
in
passing
the
authorizations
required
that,
like
not
everybody
who
wanders
by,
is
going
to
be
or
should
be
allowed
to
change
the
configuration,
but
some
people
might
be
able
to
change
some
part
of
it
and
not
all
of
it
or
I
don't
know
we
don't
want
to
get
into
real
information,
just
to
alert
them
to
that.
There
are
authorization
issues.
C
E
C
G
C
Tasks
that
are
mostly
research
and
learning
and
then
a
little
bit
of
writing
and
there's
other
things.
It's
really
just
writing
that
you
sit
back
and
you've
got
all
these
details
and
there's
like
there's.
No,
if
somebody
who's
starting
there's
no
way,
I
can't
see
the
forest
all
the
trees
are
here.
Tell
me
about
the
forest,
and
it's
really
just
a
writing
exercise
and
exactly
a
writer
spots.
It
as
you
did
so.
A
B
A
That's
yes,
yeah.
I
think
I
think
this
page
configuring
the
system
should
be.
I
like
I
like
meg's
suggestion
that
it
should
be
brief,
so
a
relatively
few
paragraphs
and
then
stop
and
and
inside
those
paragraphs,
it's
perfectly
fine
to
so
the
paragraph
should
introduce
a
few
key
concepts,
but
not
not
too
many.
You
know
one
or
two.
A
G
A
But
now
I
I
don't
know
how
good
or
bad
oh
okay,
so
there
is
content
behind
script,
console
and
cli
good
okay.
So
so
there
is,
there
is,
and
and
certainly
that,
intro
page
managing
plug-ins
it
seems
reasonable
that
it
would
have
a
paragraph
that
talks
about
what's
a
plug-in
and
how
or
maybe
that's
already
there
in
using
jenkins.
A
D
Yeah
and
also
my
advice
would
be,
of
course
we
can
make
things
very
complex
as
it
is
already
with
configuration
of
jenkins,
but
we
we
want
to
keep
in
mind
a
new
user
of
jenkins,
so
attract
new
customers.
Basically,
and
my
advice
would
be
to
keep
them
in
mind
while
suggesting
options
for
configuration,
so
they
will
not
be
lost
in
the
foresters.
C
C
I
look
at
the
ui,
I
sit
there
and
I
can
figure
and
it's
like
yeah
yeah,
but
I've
got
a
hundred
masters.
I
have
to
do
this
a
hundred
times.
I
wish
I
could
just
write
a
shell
script.
Why
don't
they
give
me
a
shell
script?
Well,
we
did.
We
just
didn't,
tell
you
about
it.
If
you,
you
dig
enough,
you'll
find
the
docs
that
are
good
about
how
to
do
that.
C
If
I
read
through
the
documentation
very
cautiously,
I
go
to
a
lot
of
work
and
I'm
running
my
pipelines
and
my
jobs
up
on
my
masters
and
then
somewhere
along
the
line.
It
says:
oh,
if
you
really
want
to
be
fancy,
you
don't
have
to
do
it
that
way,
whereas
we,
you
know,
but
the
subtleties
of
the
table
of
contents
that
stuff
that
still
lasts.
It
looks
to
me
like
an
add-on
feature
but
someday
in
my
spare
time.
C
A
B
Yeah,
it's
covered
just
on
our
question,
but
this
time
about
the
distribution
distribute
build
page:
okay,
yeah.
I
sent
the
immigration
pr
okay,
but
in
the
content
there
is
some
links
that
point
to
another
pages
from
week
two
week
week,
page
yeah,
because
that
pages
don't
do
migrator.
Yet
there
is
some
problem
with
this
links
or
or
no
we
can't
keep
them
quite
to
use.
A
A
B
A
A
B
A
B
C
A
C
A
Well
and
so
overview
kind
of
things,
you
can
certainly
look
at
the
doc
sig
the
documentation
special
interest
group,
and
it
gives
you
a
guidance
to
hey
here-
are
the
meetings
it's
it
talks
about
the
the
special
interest
group.
It
does
not,
however,
mention
office
hours.
So
it's
a
good
point
that
we
may
want
to
put
an
action
item
on
me
to
put
an
entry.
Oh
no,
it
does
mention
it.
Sorry,
it
does
okay,
each
monday
at
2200
utc.
D
A
Yeah,
so
so
there
are,
there
are
at
least
two
locations
where
it's
described.
I
I'm
I'm
not
yet
persuaded
that
we
could
ever
put
it
in
enough
locations
that
a
new
contributor
would
immediately
find
it.
But
that's
that's
not
a
big
deal.
The
reality
is
they
will
find
it
one
way
or
the
other,
either
by
a
question
to
the
getter
chat
or
a
question
to
the
doc's
mailing
list
or
by
somebody
just
telling
them
hey
here's
this
office
hours,
you
could
attend.
C
C
A
C
A
A
C
A
A
A
D
D
A
C
Right,
but
how
do
people
does
everybody?
Who
knows
that
there's
a
hack
fest
coming
up,
no,
I
mean,
would
be
interested
like
that
would
be
a
thing
for
github
to
send
everybody.
That's
contributed
anything
to
say
the
docs
in
the
last
year
might
get
I'm
getting
too
much
netflix
mail
right
now,
but
it's
starting
to
you
know
finished
watching
like
a
six
season
thing.
I
finally
finished
it
the
next
day.
It's
like,
we
hope
you
enjoyed
it.
C
A
A
C
C
B
B
C
Something
else
mark
you-
and
I
should
look
at
this
sometime
when
you
have
a
few
minutes
as
we
can
fix
it
fast
in
our
jenkins
fundamentals
class
that
we
offer
it's
paired
down.
It's
now
just
about
an
hour
class
we
took
rid
of,
and
but
we
do
have
one
section
there
about
contributing
to
jenkins
it's
pretty
short,
but
we
might
want
to
add
just
a
slide
or
two.
C
C
C
A
A
D
H
D
D
C
So
study
for
right
now
for
all
of
the
classes
is
free,
and
I
think
it's
probably
going
to
stay
that
way.
But
right
now
all
of
the
classes
are
free
to
take
for
self-study
separately
is
well
and
these
classes
actually
relate.
If
you
understand
the
material
in
a
set
of
these
classes,
that
pretty
much
qualifies
you
to
sit
for
certification
now,
the
certification
exam
itself
comes
with
a
cost,
and
it's
run
through
into
the
third-party
organization.
C
So
yeah,
if
you,
if
you
go
to
cloud
beach
university
page
there,
there
is
a
a
little
blurb.
It
looks
like
a
class,
but
that
tells
you
what
to
do.
If
you
want
to
get
certified
and
it
tells
you
what
the
classes
are
and
what
the
whole
process
is
so,
but
the
classes
themselves
are
free
to
you
at
any
time
for
self-study.
C
They
have
yes,
those
and
those
have
been
free
charge
no
charge
for
a
while.
The
one
class
for
which
there
was
a
charge
was
the
pipeline's
intermediate
class,
which
I
think
may
be
about
to
be
broken
up
into
smaller
modules.
Anyhow,
and
I
I
suspect
we
made
it,
we
made
everything
free
because
of
covet,
and
but
I
suspect
that
we
will
keep
it
that
way.
Cloud
b's
general
thought
is
that
we're
much
more
concerned
that
people
learn
how
to
do
this
stuff
and
do
it
right.
D
A
C
D
C
C
The
big
feature
that
you
get
is
something
called
an
operation
center
which
all
your
masters
are
attached
to.
So
you
can
sit
on
your
operation
center
and
connect
to
all
of
your
masters
and
download
stuff
and
sort
of
sort
of
not
as
much
as
I
wish,
but
sort
of
manage
all
your
masters
from
one
place.
Instead
of
running
around
the
place
trying
to
find
every
under
every
one
of
the
hundred
masters,
and
then
there
are
a
number
of
proprietary
plug-ins
that
are
offered
that
have
very
great
value.
C
And
theoretically
I
don't
know
if
it's
all
but
theoretically
things
that
you
need
in
an
enterprise
more
than
a
small.
You
know
a
lot
of
things,
for
I
don't
know
old
ones,
long-running
builds
and
there's
cross-team
collaboration,
a
much
nicer
feature.
For
instance,
if
you
have
a
plug-in
on
one
master,
that
you
want
to
trigger
a
plug-in
on
another
master,
a
very
nice
interface
for
that
and
a
few
things
like
that.
C
So
if,
if
you're,
really
small,
you
know
if
you're
a
little
shop
with
three
developers,
cloud
b's
probably
isn't
much
use
to
you.
But
if,
as
you
start
to
get
bigger,
cloudbeads
has
some
very
nice
features
in
it
more
sophisticated
authorization
through
roles
and
which
now
there's
an
open
source
roles.
But
it's
not
as
robust
as
the
one.
That's
in
cloudbees.
C
C
You
know
cloud
visa's
code,
so
you
get
the
interface
and
that-
and
it
includes
you-
can
do
plug-in
management
for
all
of
your
masters
through
configurationist
code
on
cloudbees,
so
that
sort
of
stuff.
But
it's
it's
mostly
features
that
extend
jenkins
in
ways
that
are
very
useful
if
you've
got
a
very
large.
C
Well,
frankly,
most
of
our
cloud
b's
customers
start
out
running
jenkins
at
the
day
that
their
top
it
comes
in
with
a
knife
pointed
at
his
heart
because
he's
so
tired
of
running
around
trying
to
find
all
100
masters
every
time
he
needs
to
do
an
upgrade.
They
start
talking
about
putting
in
cloud
b,
so
they
get
some
control
over
it.
But
in
fact,
when
you
boot
up
cloud
b's
core
or
it's
about
become
cloud
bci
we're
renaming
it.
C
But
when
you
boot
that
up
the
first
screen,
you
say
you
get
says,
welcome
to
jenkins,
so
we
so.
This
is
why
we
do
the
jenkins
classes
and
the
their
classes
are
clearly
marked
as
to
whether
they
are
a
jenkins
class
or
a
cloudbeast
core.
But
if
you
are
brand
new
to
all
of
it,
you
better
take
the
jenkins
classes
before
you
take
the
cloudbeast
core,
because
in
cloud
b's
core,
you
learn
a
lot
of
fancy
extra
stuff.
You
can
do
with
agents,
but
you
don't
learn
what
an
agent
in
a
node
is.
C
We
assume
you
know
that,
so
the
you
know
con
this
security
settings
a
whole
bunch
of
that
stuff
is
just
the
same,
although
slightly
different
ramifications,
because
you
have
you
even
have
the
option
you
can
have.
You
may
have
masters
attached
to
your
operation
center.
That
is
still
self-managing,
that
you
don't
control
from
the
operations
center
or
you
can
sit
on
your
operations
center.
Don't
let
any
masters
have
any
executors
and
nothing
you
do
on
any
of
those
masters
will
put
an
executor
on
any
of
them,
but
it's
a
highly
configurable.
Of
course.
B
A
A
A
As
an
example,
code
signing
certificates,
a
code,
signing
certificate
organization
does
not
want
to
issue
a
certificate
to
an
entity
which
does
not
exist
right.
It
would
be
far
too
easy
to
steal
or
to
to
mislead
people,
and
so
they
demand
that
there'll
be
a
legal
entity.
The
other
is
donate,
receiving
donations
processing
well,
in
our
case,
processing,
small
gifts
to
to
contributors.
C
C
It
was
like
something
needed
to
go
out
for
the
open
source
community
at
the
same
time
that
something
needed
to
go
out
to
cloudbee's
customers
and,
needless
to
say,
the
financial
people
were
saying
they're,
giving
us
money,
they
get
priority
and
the
community
is
saying,
but
but
so
it
was
a
nice,
it's
it's
an
argument
that
we
should
not
be
having
on
a
day-to-day
basis.
So
this
gave
us
an
organization
who
is
primarily
charged
with
the
care
and
feeding
of
the
open
source.
A
What
was
hudson
will
now
be
jenkins,
and
and
thus
because
of
that,
the
jenkins
project
is
sensitive
to
ownership
of
copyrights
and
and
we
will
continue
to
be
sensitive
to
it.
Prior
to
continuous
delivery
foundation,
the
copyright
was
held
by
an
organization
called
software
in
the
public
interest,
so
copyright
ownership
is
a
big
deal
for
us
and
we
make
sure
that
that
we
know
who
owns
the
copyright
and
that
it
is
a
legal
entity
with
the
right
defenses.
C
Okay
and
another
bit
of
trivia
is
that
koshiga,
who
is
the
person
who
originally
wrote
hudson
when
he
worked
for
sun
and
he's?
I
don't
know
if
you've
ever
met
him,
he's
very
impressive
he's
very
just
because
he's
so
gentle
he
always
said
I
was
just
lazy.
I
just
wrote
this.
I
was
tired
of
doing
the
same
stupid
thing
over
and
over
again
and
that's
the
beginning
of
jenkins,
but
he
is
one
of
the
co-founders
of
cloudbees
and
until
very
recently
he
was
with
us.
C
C
B
C
A
C
Yeah,
but
it
strikes
me
that,
like
because
we
have
been
very
careful
at
trying
to
keep
our
jenkins
courses
separate,
but
there
is
a
question.
This
is
a
jenkins
course.
It's
offered
by
cloudbees.
What
is
the
difference
between
what
cloudbees
there
ought
to
be,
and
there
was
some
other
stuff
there
once
which
got
terribly
crusty
and
we
lost
it,
but
it
ought
to
be
out
front.
It's
like
what
is
cloud
b's
compared
to
jenkins,
so
I
I
can
do
some
work
on
that.
So.
D
D
There
is
a
section
in
I'm
not
sure
if
section
is
correct
word,
but
there
is
part
of
configurations
code
called
tools
which
you
can
specify
different
tools
like
jdk
python
and
so
on.
So
the
question
is:
is
there
a
relationship
between
documentation,
our
documentation,
tools,
section
and
tools,
section
in
configurations
code?
D
A
A
Let's
see,
we
should
make
this
more
readable
there
we
go
and
there's
the
ant
tool
and
there's
its
definition
where
it's
downloaded
from
etc.
So
very
much
configurations
code
does
support
the
notion
of
tools.
I'm
not
sure
that
was
specifically
your
question,
though
vlad
so
ask
your
question
again
and
let's
be
sure
we
we
talk
it
through.
D
Well,
I
just
trying
to
understand
how
what
is
the
best
way
of
using
two
section
in
configuration
as
code
while
addressing
documentation
tools
section
in
documentation,
because
when
I'm
trying
to
go
through
tool
section
and
documentation,
I'm
trying
to
implement,
for
instance,
using
configures
code
approach
which
may
be
attract
attractive
enough
to
new
users.
So
to
make
it
simple.
A
D
C
C
Managing
tools
is
a
list
of
the
tools
that
are
there
automatically,
but
and
now
here-
and
I
actually
have
this-
is
on
my
question
of
things
that
I
need
to
learn
that
I
you
know,
I'm
getting
the
point
guys
where
I
know
a
lot
of
things
and
then
there's
the
basic
things
that
I
don't,
but
when
I'm
in
the
configuring
system
page,
I
can
configure
some
tools
up
there.
What
version
of
java
or
may
have
been
on
all
this
that
I
want
up
there?
C
I
can
configure
those
in
my
agent
or
I
can
in
my
pipeline,
call
and
say
I
specifically
want
this
tool
and
load
it
from
here
and
bring
this
tool
in
now.
What
is
the
relationship
of
all
these
methods?
They
have?
They
all
have
their
place.
I
believe,
mark
from
listening
to
our
favorite
could
majon
that
configuring,
the
tools
on
the
master
itself
is
not
the
preferred
way
in
most
cases
that
you
want
to
configure
them,
but
it's
more
efficient
to
have
them
on
the
agent
or
in
the
pipeline.
C
D
C
Like
it's
one
of
those
things
where
I
don't,
I
think
the
options
are
there
for
a
reason.
For
example,
if
your
pipeline
is
building
an
application
that
runs
on
desktops
and
androids,
you
want
to
build
it,
and
then
you
want
to
test
it.
You're
going
to
have
separate
stages
for
testing
it
and
you're
going
to
test
it
on
androids
and
you're,
going
to
test
it
on
linux
and
windows,
and
whatever
else
you
want
it
to
run
on.
C
But
today
the
the
right
way,
I
believe,
would
be
to
code
the
application
to
run
on
everything
and
then
write
your
pipeline.
So
it
gets
tested
on
everything
correctly
and
that's
going
to
mean
defining
your
agents.
Now,
if
you're
doing
you
know,
if
you're
going
to
do
a
cookbook
for
your
grandmother
for
christmas
using
jenkins,
you
probably
don't
care
you're,
going
to
use
one
version
of
every
tool
and
you
can
put
it
on
your
master
and
go
ahead
and
build
it
and
put
a
red
ribbon
on
it.
C
C
And
every
every
method
has
times
when
that
is
the
best
one
to
do
right
right
and
if
I
am
a
new
user
who
wants
to
get
quickly
to
this
understanding
rather
than
choosing
one
because
it
looks
like
fun
and
finding
out
six
months
later,
that
I
did
the
wrong
one.
I
don't
know
where
to
find
a
little
overview.
That
tells
me
you
can
configure
tools
here
and
here
and
here.
C
A
C
G
C
B
C
F
D
A
A
A
F
A
A
A
C
F
A
C
C
A
A
Yeah
this
one,
this
one
decidedly
does
not
go
on
jenkins
dot,
io
right.
This
is
this,
describing
those
differences
is
a
cloud-based
responsibility
and
therefore
cloudbees.com
can
worry
about
those.
The
jenkins
site
doesn't
need
to
worry
about
this
really
any
more
than
we
worry
about.
What
are
the
differences
between
spinach
and
jenkins.