►
From YouTube: 2021 05 17 Docs Office Hours
Description
Jenkins documentation office hours May 17, 2021 discussing Jenkins on Kubernetes with specific focus on the plugin installation manager documentation being created by Y.R. Sudhakara and the configuration as code blog post being created by Deeraj Singh Jodha
A
Welcome
to
doc's
office
hours,
it's
the
18th
of
may
in
asia
and
australia
where
we're,
where
we're
hosting
it's
only
the
17th
of
may
on
my
side
of
the
international
date
line.
Thanks
for
being
here,
that's
great
topics
that
I
had
on
mine,
jks,
plug-in
documentation.
We've
got
an
initial
pull
request
from
dhiraj
with
or
that's
already
received,
reviews
from
oleg
and
tim
and
then
oh
whoops.
I
meant
to
put
this
one
jenkins
on
kubernetes,
because
soda
car
we've
got
a
proposal
from
you
see
the
mailing
list,
content
for
a
proposal.
A
A
C
A
And
and
thought
we
would
go
through
it
here
today.
I
will
give
additional
feedback
online,
but
there's
there's
some
pieces
of
that
that
I
think
you
can
make
it
easier
for
us
to
review
so
review
here.
I'll
just
put
it,
let's
put
it
in
the
in
the
notes,
so
that
we've
got
it
because
it's
part
of
the
google
group
thank
you
for
posting
it
to
the
group.
A
A
A
Yes
and
that's
a
good
one
for
us
to
discuss,
I
saw
that
in
your
in
the
the
getter
chat
channel
and
let's
discuss
it
because
there
there
are
good
things
to
learn
there
about.
Okay,
what's
happening,
you
may
be
able
to
do
some
diagnosis
while
we're,
while
we're
online
here
to
help
us
understand
what
what
it
is.
That's
affecting
you.
B
B
A
A
To
the
jenkins
dot
io
site,
proposing
a
blog
post,
excellent,
very,
very
good,
and
we
see
initial
feedback
from
oleg
and
suggestions
for
alternate
videos.
When
I
looked
at
it,
my
preference
is
this:
the
one
that's
six
months
old
rather
than
the
one
that's
a
year
old,
but
but
either
is
certainly
newer
than
this
overview
and
evelina.
The
the
person
who
provided
this
six-month-old
one
is
actually
a
member
of
the
jenkins
governance
board.
C
A
A
So
we
look
at
the
checks
in
the
under
the
checks
tab
here
and
in
the
checks
tab.
We
see
jenkins,
had
a
failure
and
if
we
look
to
see
what
was
the
failure,
I
can
click
rerun
here.
Oh
yes,
sorry!
So
what?
What
this
message
is?
Is
the
ci
server
had
a
problem
and
the
problem
it
had
will
be
in
the
logs
and
the
problem
will
say
something
obnoxious
like
it
lost
connection
with
the
agent.
A
So
this
is
a
transient
error
that
we've
had
on
this
particular
ci
server,
because
in
order
to
manage
costs,
we
have
to
run
both
azure
and
aws,
and
crossing
cloud
providers
does
not
always
give
us
a
seem
to
give
us
a
reliable
connection.
But
this
is
now
running
and
10
or
15
minutes
from
now.
We
should
come
back
and
check
and
see
if
it's
gone.
Green
so
is.
A
Yeah
well,
if,
if
we've
got
a
red
build,
we
need
a
green,
build
before
we'll,
merge
it
absolutely
and,
and
the
challenge
is
you
as
a
submitter,
probably
cannot
request
a
rebuild,
I'm
not
sure
that
the
rerun
link
there
is
available
to
you.
Yes,
and
so
so
all
you
one
one
technique
we've
used
in
the
past
is,
you
could
add
an
additional
commit
that
will
cause
it
to
be
rebuilt
or
you
could
close
the
pull
request
and
reopen
it.
That
will
cause
it
to
be
rebuilt
or
you
could
message
someone
else
and
say
hey.
C
A
Okay,
yeah
and
that's
that's
just
fine
now.
This
is
actually
a
good
example
where
we
may
want
with
10
commits.
Would
you
mind
if
we
squash
them
all
into
a
single
into
a
single,
commit
sure
I'll?
Do
that
you
you
don't
even
have
to
actually
do
it
if
I
just
put
a
label
on
it
that
says
squash
merge
that
reminds
whoever
does
the
merge
of
it.
They'll
do
the
squash
for
you.
A
A
You
had.
I
like
the
three
questions.
It
was
hey
which
of
these
options.
Should
we
take
my
the
first
one
you
described
as
should
we
have
a
separate
section
which
is
inside
the
book
using
plug-in
ins
after
a
separate
section
after
using
after
the
managing
plug-in
section.
So
let
me
open
that
and
let's,
let's
look
at
it
together
and
see
all
right.
A
So
I
think
what
you're
saying
is:
should
we
have
a
separate
section
in
the
managing
jenkins
volume
where
today
we
have
managing
plug-ins,
you
think,
should
there
be
a
separate
section
which
is
whoops,
which
is
titled
using
the
plug-in
installation
manager
tool,
so
it
would
have
its
own
dedicated
section
in
this
chapter.
Did
I
understand
what
you
were
suggesting?
A
A
A
A
Right
exactly
and
and
my
thought
was
I
I
had
personal
preference
for
option
three,
if,
if
you
think
that
would
work
what
you
now
what's
your
sense,
because
you
were
the
one
who
did
the
the
writing
of
it,
it's
it
certainly
talks
it's
important
to
talk
about
hey.
How
do
we?
How
do
we
get
it
downloaded
onto
our
system?
A
How
do
we
do
and
now
there
are
a
number
of
different
activities
and-
and
you
highlight
many
of
them
here
as
hey-
there
are
many
different
tasks,
not
just
installing,
not
just
installing
plug-ins
right.
So
this
is
the
installing
a
plug-in
section,
but
the
tasks
that
are
described
here
listing
dependencies
previewing.
A
It's
given
the
length
of
the
page.
I
think
it
could
easily
be
a
separate
page,
particularly
if
we
expanded
some
of
these
here
links
this
one,
for
instance,
takes
us
to
a
a
nice
multi-paragraph
description,
and
this
one
also
provides
us
a
multi-paragraph
description,
oops
wrong.
One
sorry
that
was
it
was
this
one
here
we
go.
These
things
give
us
some.
Some
really
good.
Examples
of
hey
here
are
details
that
we
may
want
to
put
in
line
inside
the.
A
D
D
A
A
A
B
A
Good,
okay,
meg
any
objections
free
from
you.
If
we
were
to
say
hey,
let's
go
with
option:
one
yeah:
okay,
that
that
that
sounds
good
to
me.
It's
plugin
installation
manager.
Doesn't
it
does
much
more
than
just
install
plug-ins
right?
It's
it's
got
the
ability
to
install
them.
It's
got
the
ability
to
report
on
them.
It's
got
the
ability.
We
actually
use
it
in
the
jenkins
infrastructure
to
maintain
the
list
of
the
current
exact
version
numbers
that
are
available
now.
A
A
A
A
A
A
I
often
have
to
find
a
way
to
break
the
command
line
into
multiple
pieces,
because
if
I
don't,
when
I
put
it
in
as
a
sample
as
an
example
in
the
in
the
code
or
in
the
the
file,
it
will
this
one.
For
instance,
if
this
line
gets
too
long,
it
will
force
the
page
to
render
widely
and
have
a
horizontal
scroll
bar
on
it.
B
A
A
If
we
look
under
docker
and
here
on
mac
os
and
linux,
we
see
exactly-
and
in
this
case
it's
it
even
allows
us
to
attach
explanatory
bullet
bubbles
to
each
item
so
that
we
can
explain
hey
this
thing
means
this,
and
this
thing
means
this
and
then
they
read
down
here
and-
and
that's
actually
pretty
easy
to
do
that
layout
and
ascii
doc.
If
we
now
jump
to
the
bottom
of
this
page
and
click
improve
this
page,
it
will
take
us
to
the
page.
A
A
B
A
A
A
B
A
A
B
A
Excellent.
Thank
you
thanks
very
very
much.
We
got
we
received
another
question
related
to
this
from
the
there's
work
going
on
in
the
docker
images
that
would
benefit
from
your
your
documentation
on.
It
was
mentioned
on
one
of
the
the
pull
requests
to
the
docker
image
about
using
plug-in
installation
manager
as
a
complete
replacement
for
an
old
shell
script.
We
had
so
thank
you
again
for
doing
this
documentation.
It's
very
much
appreciated.
A
And
those
I
will
send
to
you
yeah
I'll
I'll,
send
those
to
you
separately,
so
so
those
the
there
there
are
some
places
where
I
think,
oh
okay,
we
might
want
to
say
it
this
way
or
that
way,
but
it's
it's
probably
easier.
If
I
just
send
those
to
you
separately
as
you're,
getting
ready
to
submit
them
through
the
ascii
doc.
A
A
A
B
B
A
D
B
I
looked
at
some
of
these
pages
right.
They
are
very
in-depth,
so
it
will
take
a
lot
of
effort
and
you
can
pull
them
into
a
reference
manual
for
somebody
like
a
developer
or
plugin
developer.
To
look
at,
for
example,
on
this
page
in
the
reference
manual
like
the
regular
reference
manual
you
have
for
products,
you
can
do
that
for
darker
page.
You
can
improve
that,
but
it
it
takes
a.
D
Yeah,
I
might
you
know
just
a
general
for
all
documentation
is
that
I
want
the
guide
when
I'm
getting
started
the
guide
that
sort
of
puts
it
all
together
once
I
know
that
then
I
just
need
a
re.
I
don't
need
to
trip
over
all
that
pros
every
time
I
just
need
to
go
to
the
reference
manual
and
see:
what's
you
know
what
options
are
there
and
what
what
is
needed,
but
that's
my
general
approach
to
everything
and
I'm
sure
there
are
some
things
where
that's
not
appropriate,
but.
A
C
C
No,
it
totally
makes
sense
to
me
so
just
wanted
to
confirm
if
my
thought
process
is
right.
That
is,
we
have
some
secrets.
We
don't
want
to
put
them
directly
on
the
yaml
file,
because
this
yaml
file
is
supposed
to
be
shared
to
different
different
colleagues,
let's
say
so
that
they
can
reproduce
the
same
configuration
very
quickly.
So
we
are
looking
for
a
wave
where
we
can
indirectly
refer
them
on
the
yaml
file
so
that
it's
not
stolen
right.
C
So
next
question
here
is
that
what
like
these
are
the
three
ways
right
using
credential
provider,
plugins
then
variables
and
then
encrypting
the
strings.
So
so
these
are
the
three
things
that
there
should
be
in
the
blog
right
like
these
are
three
things
you
can
do
with
jcask.
So
is
that
what
I
want
to
write.
A
Yes,
I
think
so
now
now
for
me
the
the
credentials,
the
credentials
plug
in
with
its
yeah
yeah.
This
is
okay.
Here
we
go
so
each
of
them
has
has
their
own
subtleties
and-
and
yes,
this
is,
this-
is
an
ideal
place
for
a
blog
to
describe
hey.
Here
are
the
experiences
I
had
and
you
choose
one
or
two
of
these
and
use
them.
A
A
B
A
A
That's
that's
what
I
would
do.
I
think
I
think
people
would
enjoy
that
and
it
shows
shows
to
them
hey
look.
This
is
how
you
do
it,
and
this
is.
The
here
are
some
of
the
things
that
I
encountered
here.
Some
of
the
mistakes
I
made.
While
I
was
learning
so
that
they
can,
they
can
learn
from
your
mistakes
and
say:
oh
whoops,
I
shouldn't
do
this.
I
should
do
that.
A
A
A
A
A
A
C
A
C
A
A
B
D
B
A
A
And
what
had
happened
was
w
get
on
something
resulted
in
a
page
from
okay,
so
trying
to
download
the
kubernetes
plug-in
1.29.2
and
instead
got
an
a
404
not
found
while
trying
to
reach
get.jenkins.io
right.
So
I
did.
I
describe
it
correctly,
sudacar
that
what
you
are
trying
to
do
is
attempting
to
install
kubernetes
plug-in.
B
B
C
B
A
Absolutely
yeah,
so
so
I
wanted
to
start
first
with
updates.jenkins.io
because
I
think
that's
where
everything
starts
yeah.
So
so,
if
we
go
there,
it
presents
this
page
and
one
of
the
things
that
I
use
this
page
for
is
to
find
the
latest
releases
so
that
up
the
latest
releases
link
and
then
here
it
was
kubernetes.
A
A
Is
something
like
that
right
that
resp
so
there's
the
there's
an
example
this
then,
if
I
look
at
what,
when
I
try
to
open
that
url
so
copy
this
one,
oops
nope,
that
I
just
made
the
mistake
copy
the
link
address,
if
I
paste
it
here
and
append
on
the
end,
question
mark
mirror
list,
it
will
show
me
the
mirrors
for
that
page
or
for
that
plug-in
by
my
geography
and
now
what
this
means
is
for
you.
I
think
what
you'll
see
is
that
your
mirror
is
likely
oops.
I
went
the
wrong
direction.
A
B
Yeah
that
is
see
it
is.
This
is
not
a
bandwidth
issue,
it
is
a
net.
I
want
somebody
to
tell
me
whether
it's
a
network
issue.
Okay,
so
if
you
use
those
get
urls
that
I
sent
you
in
the
gita
chat
and
if
it
works
for
you,
then
I
can
be
sure
that
it's
a
network
issue,
my
gut
feeling
is
this-
is
a
network
issue.
A
A
A
B
A
A
A
B
A
A
A
A
B
B
A
B
A
B
A
B
A
A
B
A
A
B
B
A
Excellent
we've
we've
hit
our
time.
I've
got
one
item
just
to
forewarn
that
I've
I've
been
approved
to
donate
a
kidney
to
my
nephew
and
so
june.
7Th.
I
will
have
surgery
and
I'll
be
gone
for
recovery
for
as
much
as
eight
weeks
I'll
be
sending
out
invitations
to
people
asking
various
people
asking
if
people
would
like
to
volunteer
to
help
take
some
take
on
some
of
the
things
that
I'm
doing.
A
Look
for
the
email
message
it'll
come
out
to
the
docs
list
would
love
to
have
your
help
in
in
any
one
of
the
areas
that
are
identified
there
if
you're
interested
so
I'll
be
available
till
june
7th,
but
then
june
7th.
I
I
have
surgery
and
I'll
be
gone
then
at
least
well,
it's
expected
two
weeks
and
the
doctors
say
it
could
take
six
or
eight
I'm
almost
60
years
old
and
therefore
I
don't
heal
as
quickly
as
I
used
to.