►
From YouTube: 2021 04 26 Docs Office Hours
Description
Jenkins documentation office hours Apr 26, 2021.
A
A
A
A
C
C
A
D
E
A
D
A
A
Okay,
good
all
right
so
sudakar
you
had
mentioned
so
we
had.
We
had
proposed
the
jenkins
project
proposed
a
google
summer
of
docs
or
a
google
season
of
docs
project
yeah,
but
it
was
was
not
accepted.
They
only
accepted
30
projects
this
year
and
we
were
not
one
of
them
and
so
we're
we're
doing
a
retrospective
now
to
try
to
understand
what
we
could
have
done
better
to
do
a
better
job.
However,
there's
still
an
opportunity
for
us
to
consider
so
the
project
definition
is
still
there.
A
A
E
A
Something
like
like
gsad
would
have
been,
and
the
answer
is
yes,
the
governance
board
has
has
been,
has
been
willing
to
consider
that
okay,
the
problem
is
our
mentors
are,
are
loaded
right
now
with
google
season
of
code
or
google
summer
of
code,
and
that
will
continue
until
september.
So
the
likely
time
when
a
funded
development
effort
would
be
is
probably
not
until
september
at
the
earliest.
C
Yeah,
for
me,
that's
okay,
I
can
start,
and
maybe
by
that
time,
I'll
finish
it,
but
funding
is
not,
but
a
real
need
for
me
at
this
time.
Okay,
all
that
I
need
is
a
full
request
review
like,
for
example,
right.
I
will
do
an
initial
outline
as
to
how
I
will
approach
it
and
then
maybe
in
another
one
or
two
submissions
I'll
finish,
the
submission.
A
A
A
A
A
A
Okay,
this
one,
I
think,
is
it
yes,
there
it
is
okay.
So
here
is
my
my
poor
and
just
so
you're
clear,
sudakar
poor
attempted
an
outline
of
the
kinds
of
things
that
we
should.
We
should
have
covered
and
be
warned
that
as
a
as
a
as
a
contributor,
I
am
the
worst
of
all
possible
people
to
suggest
what
is
the
best
way
to
describe
jenkins
on
kubernetes.
C
C
A
C
A
E
A
But
and
what
it
has
is,
let's
see
it
has
mini
cube,
mini
cube.
I
think
it
has
helm,
charts
yeah
and
it's
got
one
other
variant
that
I
don't
recall.
Let's
see:
oh
yaml
files
right
or
two
others,
yaml
files
and
jenkins
operator,
so,
okay
and
and
those
and
jenkins
operator
and
of
course
jenkins
operator-
is
an
active
project
for
for
this
year
as
a
proposed
project
for
google's
summer
of
code,
and
so
this
one
will
will
likely
get
some
attention.
B
C
A
So
so
there
are
many
many
use
cases
that
jenkins
jenkins
x
is
intensely
focused
solely
on
kubernetes
and
on
delivering
microservice-based
things
into
cloud-native
environments,
and
that
means
there
are
many
many
use
cases
that
jenkins
x
just
can't
do.
On
the
flip
side.
There
are
many
many
things
in
the
cloud
native
world
that
jenkins
doesn't
do
as
well
as
jenkins
x.
Does
one
is
a
horizontal
broad
application
jenkins
and
the
other
one
is
a
a
very
intensely
focused
vertical
application
jenkins
x.
A
A
D
D
I
think
blogs
need
to
cover
something
more
than
that,
for
example,
they
also
need
to
tell
us
like
it
might
be.
It
will
be
great.
They
can
tell
us
as
well
like
how
things
are
working
inside
at
the
class
level
like
how
the
yaml
is
being
passed
and
each
of
the
orientation
level
data
has
been
taken
and
been
put
into
jenkins
and
how
jenkin
is
using
that
and
configuring
itself
like
that
level,
I'm
more
interested
in
now.
D
I
can
contribute
to
this
plugin
really
well,
and
it
would
be
really
great,
like
the
contributor
contribution
level
for
this
plugin
would
be
increased
from
even
from
college
students
as
well
not
be
restricted
to
someone
who
just
knows
lots
of
has
lots
of
experience
in
coding.
That's
what
I
was
aiming
for.
E
D
A
A
A
E
E
E
E
E
E
D
Yes,
so
I
I
was
looking
through
the
github
repo
of
jks
and
I
found
out
that
they
have
a
demo
folder
in
which
they
have
added
the
example
configuration
of
some
plugins,
not
all
some
plugins.
So
if
you
click
there
are
many
plugins
there
and
if
you
just,
let's
say,
click
on
git
and
under
that
there
is
a
yaml
file
and
it
shows
what
you
need
to
include
in
your
main
jenkins.yaml
file
in
order
to
include
this
git
plugin
there.
So
it's
like
an
example
for
user
who
just
is
very
new
to
git
plugin.
C
D
D
E
D
Yes,
exactly-
and
I
was
my
second
part
of
the
question-
was
that
just
the
same
thing
like
if
I
I
can
contribute
to
write
a
documentation
as
per
I?
I
definitely
need
to
learn
a
lot
because
I
just
found
out
about
it
few
weeks
ago,
but
I
would
love
to
make
it
more
simplified
in
the
form
of
a
documentation.
E
Right,
which
might
actually
revive
some
interest,
I
mean,
if
we've
got,
you
know
the
same,
might
get
active
again.
Even
if
there's
somebody,
I
think
they
sort
of
got
it
implemented,
and
now
it's
sort
of
gone
dormant
right.
I
don't
know
mark.
Are
they
working
on
additional
features
for
it
or
is
it
pretty
much
feature
complete
or
we
don't
even
know,
mark
you're,
muted,
if
you're
speaking.
A
A
D
D
A
A
D
E
A
D
I
actually
asked
two
questions
yesterday
on
jitter
channel
of
jks.
First
one
was
that
how
do
you
decide
which
plugin
demo
you
want
to
put
up
next
on
this
demo
folder
like?
How
do
you
decide
the
priority,
so
tim
actually
answered
me
and
said
that
we
actually
ideally
need
as
if
we
have
as
many
plugin
demos,
that's
great,
but
we
go
by
the
popular
ones
first,
so
so
that's
the
way
forward.
I
think
so
we
can
start
looking
at
the
most
popular
ones.
D
If
they
are
not
documented
here
in
this
demo
folder,
then
we
can
add
their
configuration
now
then.
Our
second
question
I
asked
to
him
was
that
how
do
you?
Actually?
I
think
this
is
a
very
bigger
question,
but
for
me
I
had
really
I
had
doubted.
How
do
we
generate
a
yaml
file
for
a
particular
plugin
to
add
it
into
this
demo
folder?
Then
he
told
me
that
you
need
to
just
configure
it
on
your
jenkins
with
the
help
of
the
ui
and
then
download
the
yaml
file
from
that
jks.
D
D
D
Now,
if
I
want
to
add
a
demo
of
that
plugin
into
this
demo,
folder
like
there's
so
many
parameters,
how
do
I
decide
which
one
I
want
to
put
in
so
like?
I
have
to
do
lots
and
lots
of
configuration.
Where
do
I
stop?
Where
do
I
draw
the
line
like
this?
Is
enough
for
a
demo
folder
then
tim
suggested
me
that
you
need
to
just
configure
it
as
like.
It
is
sufficient
as
much
just
configure
it
that
much
so
last
thing
I
want.
I
know
I've
been
speaking
for
a
long
time.
D
I
don't
think
like
they
can
be
meant
as
the
best
way
to
know
how
to
configure
a
plugin,
because
if
I-
because,
if
I
add
job
dss
yaml
into
this
demo,
folder
by
just
playing
with
few
filters-
a
user
will
come
here
and
see
that
oh,
they
actually
have
a
yaml
file
for
jaw
job
view
plugin.
I
can
actually
use
that,
but
they
will
not
be
able
to
understand
all
the
parameters,
because
I,
as
a
contributor,
only
dealt
with
just
two
or
three
filters.
So
this
is
not
the
go
to
destination.
D
A
A
So
what
we've
seen
is
that,
with
the
pipeline
steps
documentation
users,
often
what
we
have
is
we
have
incomplete
but
accurate,
but
correct
material
and
it's
incomplete
in
the
sense
that
it
gives
the
name
of
the
argument,
but
does
not
tell
what
the
argument
does
or
what
it
doesn't
do,
and
what
we've
found
is
that
users
are
grateful
for
that,
because
at
least
it
tells
them
oh.
This
is
what
I
have
to
do,
but
they
want
something
more
exhaustive
and
what
we
found
is
the
best
way
to
get
them.
A
A
Okay,
so
so
here's
my
jenkins
server
that
I
have
running
yeah,
so
this
is
this-
is
a
jenkins
instance,
a
controller
that
I
have
running
that
I
use
for
tests.
It's
got
several
thousand
job
definitions,
folders
credentials,
all
sorts
of
things
like
that.
If
I
go
to
manage
jenkins
and
then
configuration
as
code,
when
I
show
view
configuration,
it
will
compute
the
current
configuration
and
show
me
all
sorts
of
things
that
are
this.
A
A
The
other
thing
we
can
do
is
just
download
the
configuration,
and
now
I
can
load
it
into
my
text.
Editor
like
this
oops,
let's
load
it
into
the
text
editor
like
that
and
there
it
is
so
now
I
have
ready
to
go
all
sorts
of
things
that
I
can
do
with
these.
I
can
turn
it
into
fragments,
just
by
deleting
pieces
of
it
does.
Does
that.
Does
that
help
with
what
tim
was
describing
in
terms
of
view,
the
configuration
and
download
it.
A
A
When
I
click
generate
pipeline
script,
here
is
the
script
that
I
would
paste
into
my
pipeline.
So
the
same
kind
of
thing
as
the
the
same
concept
is
applied
in
configuration
as
code.
I
can
generate
these
fragments
like
that
now,
if
you'd
like
to
see
examples
of
fragments
of
that
here
is
another
in
case
it
helps
you
again
whoops
github
and
let's
look
on
my
github
just
a
minute,
because
I've
got
a
repository
where
I
have
a
number
of
things
that
I
track.
A
A
A
A
Right,
right
and
and
well
it's
it's
a
hint
actually
that
computers
have
gotten
so
much
faster
that
we
don't
even
have
to
do
schema
generation,
we'll
pay,
the
penalty
of
doing
schema
generation
live
continuously.
It's
like
wow,
really.
I
am
wasting
that
much
processing
power
to
do
live,
schema
generation
all
the
time.
Yes,
actually
we're.
Looking
at
the
code
inside
of
it
look
at
having
it
look
at
itself
and
decide
what
the
schema
should
be.
D
C
A
So
there
the
if
it's,
I
think
the
definition
of
interesting
is
if
it's
interesting
to
you.
That
makes
it
interesting
and
if,
if
you
say,
oh,
I'm
not
sure
what
interesting
means
you
could
look
at
other
other
locations
for
ideas.
For
instance,
the
ci.jenkins.io
configuration
is
interesting
and
it's
interesting
because
it's
large
and
it
handles
many
many
things.
A
A
I
don't
know
if
you
have
access
to
read
that
configuration
as
code,
because
it
it
contains
some
sensitive
information
like
the
code
signing
keys,
but
but
those
two,
this
one
will
take
an
interesting
configuration
of
a
jenkins
controller
and
others.
Let's
see-
and
I
think
my
marks
docker
lfs
lts
with
plugins
is
interesting,
though
not
it
contains
no
credentials
right.
It
contains
no
secrets.
A
E
A
Okay,
so
I'm
gonna,
I'm
gonna,
do
a
two-minute
overview
of
how
bad
things
are
oops
two-minute
overview
of
how
bad
things
are,
and
then
we'll
talk
about
about
the
steps
we're
taking
to
improve
things
so
jenkins.
The
jenkins
pipeline,
domain-specific
language,
is
defined
dynamically
by
the
plugins
that
are
installed
in
the
current
jenkins
installation.
A
However,
we
also
present
a
summary
of
all
plugins
and
the
pipeline
steps
that
they
implement
in
this
pipeline
steps
reference.
So
this
is
this
is
the
set
of
all
all
plugins
that
provide
any
pipeline
implementation,
and
only
a
subset
of
these
are
installed
on
any
particular
user's
computer,
but
they
are
some
subset
is
installed
now.
If
we.
A
We
love
developers,
we
really
do,
but
sometimes
they
don't
write
documentation.
Much,
let's
see
if
we
can
find
here,
it
is
pipeline,
build
step.
Okay,
so
this
one
gives
a
reasonable
description
here.
What
what's
the
job
parameter
now?
What
about
and
what
does
propagate
mean?
And
what
does
this
mean
and
oops
no
description
of
what
weight
means
and
then,
if
we
start
expanding
things
here,
it
gets
gets
much
worse.
So
let's
say
what
about
get
parameter?
A
A
A
A
A
A
Critical,
I
actually
they're
they're,
quite
distinct
from
each
other,
so
j
j
cask
does
the
configuration
of
global
and
system
level
definitions
of
jenkins
things
like
which
which
authentication
method
should
we
use
etc.
But
what's
my
ldap
server,
those
kind
of
things,
it
will
remember
the
credentials
for
my
github
server
or
for
but
what
it
does
not
do
is
define
the
code
that
should
be
executed
while
running
a
pipeline
and
that
really
needs
jenkins
pipeline,
so
so
that
that
distinction
is,
is
the
is
the
subtlety
there?
Yeah
yeah,
okay,
god
got.
B
A
B
A
A
So
now,
in
terms
of
of
persuading
people
to
use
the
snippet
generator,
one
of
the
things
that
we've
gone
after
was
something
like
this
as
an
idea
oops.
Let's
just
do
git,
maybe
that's
what
it
is.
So
I
get
for
editing
the
url.
Shame
on
me:
okay,
oh
no!
This
is
not
even
the
right
page
right.
This
one
was
the
the
idea
we
had
was.
A
A
A
A
E
A
I
see
what
you're
asking
so
that's
that's
a
that's.
Maybe
that's
worth
highlighting
here
in
this
session
that
have
not
yet
been
touched.
Right
have
not
yet
been
touched
to
improve
their
documentation
and
and
so,
for
example,
what
we
did
with
chico
africa
is,
we
generated
a
pivot
table,
of
which
plugins
had
the
most
complaints.
A
Now
this
is
a.
This
is
an
awkward
kind
of
pivot
table
right.
This
is
this
is
not
the
the
thing
you
say.
Oh
everybody's,
happy
about
it.
It's
rather,
which
things
cause
the
most
complaining,
and
here
is
this
table
that
shows
the
most
complained
about
plug-in
was
the
build
step
with
86
complaints
of
those
86.
A
A
E
A
The
most
frequent
request
in
the
feedback
on
the
documentation
is
give
me
examples
of
pipeline
and
it's
the
same
question
that
dhiraj
was
asking
with
regard
to
configuration
as
code
right.
How
do
I
write
a
good
example
that
will
satisfy
a
significant
portion
of
the
users
when
I
don't
know
what
their
arguments
or
the
arguments
are
most
important
to
them?
Yeah
right.
E
Right
and
we'll
decide
what
I
don't
know
if
we
want
to
put
this
the
possibility
of
putting
a
check
in
for
when
changes
are
made
to
a
plug-in
that
has
steps
to
at
least
ping
them
that
there's
nothing
in
your
html
directory
or
something
I
don't
suppose
we
can
tell.
We
can
tell
whether
it's
useful
or
not,
but
we
could-
and
we
probably
can't
bust
them,
now-
start
busting
them
now,
let's
not
let
them,
but
we
can
at
least
put
out
a
warning
that
this
is
not
does
not
seem
to
be
documented.
A
E
A
E
E
A
E
E
And
then
what
about
a
summary
of
things
you
mentioned
something?
You
mentioned
something
about
sending
out
a
survey
before
the
monday
meeting.
Were
you
I
think
you
were
talking
at
the
friday
meeting
and
I
wonder
with
they
seem
very.
I
don't
know
that
this
group
is
going
to
be
comfortable
in
a
meeting
to
speak
up
and
say
you
could
have
done
this
better
and
you
could
have
done
that
better.
Oh.
A
Right
and
it's
not
I
so
let
me
see
if
I
can
find
it
really
quickly
here,
because
retro
retro,
because
if
I
link
to
it
then
jenkins
nope
looks
like
I'll
have
to
look
for
it
further.
Okay,
that
was
sent
by
oleg
and
oh,
oh.
Actually,
I
take
it
back.
I
know
right
where
it
is
meg,
it's
right
at
the
bottom
of
this
document.
Oh.
A
A
E
A
E
And
yeah,
maybe
the
and
maybe
the
good,
because
I
think
I
mean
it
would
be.
The
question
is
getting
information
from
them
about
how
we
could
have
helped
them
better
and
right.
You
know.
So
if
we
put
enough
of
the
you
know
problems
that
we
saw
there,
then
we
you
know,
then
there
they
can
either
agree
with
us
that
it
was
a
problem
or
they
have
to
disagree
with
us
that
no,
no,
that
wasn't
a
problem
so.
A
A
A
A
Nope,
oh
here
we
go
algolia
usage.
This
is
no.
This
is
from
two
weeks
ago
here
I'll
show
it
so
you
can
see.
So
this
highlights
our
total
usage
here
we
go,
and
this
is
what
I
wanted
to
see-
is
open
up
the
algolia
dashboard
so
because
we're
using
algolia
as
this
open
sour
as
an
open
as
a
their
open
source
program.
A
A
I've
got
to
look
at
the
so
we're
yeah,
so
conversion
rates
not
terribly
helpful,
but
there
we
go
one
hint,
a
ten
percent,
no
results,
so
one
in
ten
queries
to
the
plug-in
site
generates
no
results.
And
if
we
look
at
this,
the
top
searches
without
results
are
right.
Here,
tfs
check,
style,
pmd
and
of
those
three.
A
D
E
A
A
A
B
A
And
so,
if
I
click
that
improve
this
page
hyperlink,
it
takes
me
into
the
github
repository
for
that
page,
okay,
so
so
there's
the
the
first
of
seeing
oh
here's
a
page.
Now,
how
do
I
do
it
now
now,
the
general?
How
do
I
contribute
here's,
this
contributing
dot,
a
doc
that
gives
you
an
outline
of
what
it
means
to
contribute?
What
are
the
you
know
as
a
newcomer?
What
do
I
need
to
do?
How
do
I
communicate
with
people?
How
do
I
run?