►
From YouTube: 2021 10 11 Docs Office Hours
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
welcome
everyone:
it's!
This
is
documentation
office
hours,
it's
the
12th
of
september
india,
standard
time,
11th
of
september
us
u.s
time
thanks
everybody
for
being
here.
Remember
we
abide
by
the
jenkins
code
of
conduct
and
deiraj
is
here
and
kristen
is
here
great?
Okay,
all
right,
so
oh
whoops
wrong
wrong
place
to
even
put
the
notes.
Let's
get
this
correct.
Sorry,
okay,
got
it.
So
one
topic
for
me
might
be
a
review
of
the
contributor
summit.
Part
two,
a
docs
without
jenkins
docs
without
wiki,
was
the
topic
that
we
had
there.
A
A
I
would
like
to
review
that
just
because
kristen
you
in
particular
may
have
some
additional
hints
for
topics
what
I've,
what
I've
discovered
by
creating
this
thing
is.
It
has,
I
think,
the
potential
to
be
a
tutorial
online,
and
I
would
like
to
talk
about
that
idea
and
then
talk
about
how
it
might
be
decomposed
into
useful
subsections
of
the
tutorial
sub
steps.
A
Okay
and
identify
the
other
is
the
other
thing
where
I
think
you
can
be
especially
helpful.
Is
you
may
be
able
to
identify
other
sub
steps
that
are
missing
other
steps
that
are
that
are
useful,
helpful,
etc?
And
then
we
always
have
the
option
of
we
could
partition
it
into
pieces
and
have
various
ones.
You
know
dhiraj.
A
If
you
want
to
do
if
you
feel
like
you'd
like
to
try
to
do
some
writing
with
me,
you-
and
I
could
do
this
thing
together,
introduce
it
as
a
blog
post
and
a
tutorial
at
the
same
time
sounds
great
okay.
So
so
that's
one
I'd
like
to
talk
to
and
then
I
think
that's
it
for
me
any
other
topics,
the
rest
of
you
would
like.
Oh
hacktoberfest,
do
we
need
to.
We
probably
need
to
talk
to
that
one
to
identify
what
work
we
need
to
be
done,
etc.
A
Okay,
then,
let's
go
ahead
with
jenkins
docs
without
wiki
as
part
one
so
dhiraj
thanks
again
so
much
for
attending
the
saturday.
The
saturday
event
that
was
that
was
really
great
and
I
thoroughly
enjoyed
the
process
we
used.
So
what
we
did
is
dhiraj
and
I
and
four
or
five
other
people
all
got
together
and
had
a
session
of
about
one
hour,
an
unconference
session
talking
about
what
are
we
going
to
do
for
jenkins
documentation
since
wiki.jenkins.io
is
gone
and
is
not
coming
back
at
least
not
as
a
confluence
server?
A
So
what
we
did
is
we
talked
about
three
three
or
four
stages
right,
so
there's
what
we
have
today
what's
in
progress,
what
what
are
the
alternatives
and
next
steps,
and
then
we
had
one
open
question
or
one
question
that
came
up.
What,
if
I
want
to
help,
so
those
were
the
the
ideas
and
we
broke
the.
What
do
we
have
today
into
three
things?
A
There's
www.jenkins.io
the
primary
documentation
site
and
it
has
lots
of
broken
links
to
wiki.jenkins.io
many
incomplete
pages.
The
wiki
data
for
that
is
for
for
wiki.jenkins.io
is
now
stored
as
html
files
on
this
git
repository
confluence
data
content,
and
so
in
this
jenkins,
folder
with
1006
files
is
the
content.
So,
for
example,
if
I
open
the
one
I
was
just
using,
was
this
one
ansible
plugin
here
it
is
as
html
and
then,
if
I
clone
this
repository
run
it
locally.
I
can
actually
open
it
and
read
the
file,
and
so
it's
usable.
A
A
A
A
A
A
A
A
A
And
and
yeah
so
we've
got
the
the
high
the
high
use,
plug-ins
are
already
migrated
and
some
set
of
plug-ins
will
probably
never
migrate
because
their
last
release
was
10
years
ago
and
they
don't
have
an
active
maintainer
and
their
installed
base
is
small
enough.
It
just
doesn't
matter.
We've
got
an
active
project
to
improve
the
jenkins
architecture
description.
I've
got
to
show
you
this
one.
By
the
way.
This
thing
is
a
thing
of
beauty
that
angelique
jarred
has
done.
You've
got
to
see
it
in
the
developer,
documentation
so
in
the
reference
documentation
under
architecture.
A
Look
at
this
picture!
Oh
my!
Isn't
that
a
thing
of
beauty
and-
and
it
really
is
an
accurate
description
reviewed
by
people
like
jesse,
glick
and
others
to
say,
yeah,
that's
actually
and
tim
jacom
reviewed
and
said:
well,
hey
what
about
this
attribute
and
that
and
and
she's
got
another
diagram
just
that
somewhat
like
this
one
right
now
done
in
just
pure
ascii
to
ascii
art.
C
A
C
A
Mean
to
be
behind
a
corporate
proxy
server
and
how
complicated
can
life
get
behind
a
corporate
proxy
and
and
and
then
okay,
the
the
integration
layers
of
yes,
you
can
do
api,
you
can
do
end
user
and
notice
this
little
box
up
here.
I've
got
to
zoom
in
on
that
the
usage
statistics
box.
This
is
one
that
tim
jacom
reminded
saying:
hey
usage
statistics
actually
come
from
the
the
user's
web
browser
and,
and
it's
like-
oh
yeah,
right
of
course,
and
and
so
it
it
reminds
that
hey.
This
is
an
interestingly
sophisticated
system.
A
Yeah,
so
this
is,
this
is
angelique's
hacktoberfest
contribution.
I
I
she
may.
She
may
be
frustrated
with
me
because
I
merged
it
today.
I've
had
seen
enough
comments
and
enough
approvals.
I
said
this
thing's
going
in.
I
want
it.
There
she's
still
got
to
store
the
source
code
for
it
and
some
other
things,
but
I
just
absolutely
wanted
that.
So
we
didn't,
we
could
show
it
around.
It's
such
a
beautiful
thing.
B
A
A
A
So
here,
okay,
it's
not
it's
not
published
yet
got
it,
but
it's
very
nice
to
all
we
have
to
do
is
do
a
like
this,
because,
thanks
to
the
magic
of
github
and
asciidoc,
this
is
how
it
will
render.
C
A
And-
and
this
is
trying
to
show
the
the
the
layer,
the
architectural
layers
inside
the
software
so
xml
extreme-
for
xml
processing,
various
scheduling
and
models,
then
the
the
page
routing
framework
called
stapler
and
the
communication
protocol
wrote
remoting.
That's
used
to
talk
to
the
agents
web
and
http
both
coming
through
stapler
a
command
line.
A
A
A
A
Now,
security
docs
are
a
an
area
where
meg
has
the
added
benefit
that
they
won't
be
merged
until
we
get
approval
from
members
of
the
security
team.
One
of
the
things
we've
accepted
on
the
jenkins.io
site
is
that
security
team
review
is
required
for
things
we
write
in
the
security
section,
so
you
make
your
point
that
you
need
to
ask
daniel
to
approve
absolutely
holds.
I
won't
merge
anything
without
at
least
one
member
of
the
security
team,
giving
an
approval
to
things
that
are
in
the
security
section.
A
They
can
do
it
or
I
can
do
it,
okay,
it
doesn't,
it
doesn't
require
me
to
do
it,
but
if,
if
we,
for
instance,
take
your
let's
see
where
was
it?
Let's
take
your
let's
look
at
your
recent
stacks
card.
D
B
A
B
A
A
Not
have
merged
it
because,
right,
if
you
look,
there
is
oh
no,
it
doesn't
show
it
here.
Why
not,
maybe
this
one?
No,
it
should
see.
This
should
have
been
labeled.
If
I
remember
correctly,
it
should
have
been
labeled
security,
and
I
thought
it
was
automatically
labeled
that
way,
but
maybe
not
so
so.
What
there
is
is,
I
think
we
put
in
place
safeguards
the
security
team
has
to
review
anything
in
the
security
section.
Go.
B
B
A
Yeah
and
the
plus
one
for
removal-
this
is
tim
jacom
is,
is
yeah,
he's
the
release
officer.
So
absolutely
very,
very
good
well-versed
he's
not
a
member
of
the
security
team,
but
he
is
the
release
officer,
so
he's
very
capable
with
jenkins
and
jenkins
development
right.
B
A
And-
and
this
one
you
see
here,
it
says
daniel
reviewed
on
behalf
of
jenkins
and
for
slash
security.
This
is
this.
Is
that
code
owners
thing
where,
when
you
submit
something
into
a
secure
one
of
the
security,
the
security
tree,
it
will
place
security
info
over
here
or
security
team.
Is
it
secured
jenkins
security
jenkins
session
for
security
will
be
listed
over
here
as
one
of
the
reviewers.
B
B
A
A
Then
the
one
that
we
discussed,
but
that
is
that
is
absolutely
inactive-
is
wiki
migration.
These
are
the
non-plug-in
pages
migrating
to.
Let's
see
you
know,
how
does
this
yeah
so
migrating
non-plug-in
wiki
pages
and
the
problem
we
see
there
is
that
it
needs
it's
not
just
whereas
plug-in
migration
is
a
mostly
mechanical
effort
copy
something
from
existing
document
place
it
in
a
new
location,
create
a
poll
request,
do
some
minor
changes,
etc.
A
This
one
we've
hit
the
point
where
most
of
the
things
that
we
might
bring
in
that
were
that
kind
of
mechanical
migration
are
already
done.
The
new
migrations
need
careful
thought
by
someone
who
is
skilled
in
use
of
jenkins
and
understands
its
history
and
its
structure,
and
therefore
we
can't
just
put
it
as
a
hacktoberfest
project.
It's
not
viable.
A
B
C
B
A
Yeah
and-
and
so
that's
that's
one
of
the
projects
that
needs
an
expert
we
had
a
beginning
of
that,
but
only
a
beginning
and
the
the
effort.
For
me,
that's
that's
almost.
We
need
to
gather
a
group
of
three
or
four
of
us
together,
physically
in
a
row
in
a
room,
put
information
on
three
by
five
cards
and
start
shuffling
and
stacking
and
sorting
and
prioritizing
them.
Okay
and-
and
I
just
I-
I
would
love
to
do
that.
But
right
now
I
haven't
got
the
capacity
to
do
it,
and
so
it's.
B
C
C
And
that
way
it's
like
okay,
like
maybe
we
don't
have
a
lot
of
time
but,
like
you
know,
office
hours
or
something
like
we're.
Gonna
take
the
next,
like
it's
probably
going
to
take
a
while
there's
a
lot
going
on,
and
I
can
assume
that
some
of
this
stuff
is
also
probably
going
to
be
superseded
by
that
demo.
Some
of
it
might
be
superseded
by
the
updated
developer.
C
A
A
Well,
I
think
I
think,
that's
an
inspiring
idea
actually
to
consider
consider
making
a
a
fixed
portion
of
each
office
hours
as
processing
for
some
portion
of
wiki.jenkins.io
content.
D
B
A
For
something
to
do
right
right,
if,
if
we're,
if
the
output
is
something
we're
confident
is
worth
worth
an
issue,
absolutely
we
could
I
mean
my
initial:
is
there
there
are
things
where
I
fear
putting
an
issue
out
there.
Somebody
would
think.
Oh,
it's
now
a
mechanical
guide,
a
mechanical
thing.
I
can
just
do
it
and
then
we
end
up
with
a
lovely
copy
of
something.
That's
got
so
many
errors
in
it
that
it's
just
not
helpful.
A
All
right,
so
so
the
wiki
migration
good
good
observation,
then
the
she-code
africa
pipeline
steps,
improvement
project
so
kristin
and
meg,
and
oleg
and
angelique
all
helped
as
mentors
on
this
project
back
in
march
dhiraj
and
what
we
did
was.
We
ran
them
through
a
a
series.
It
was
a
month-long
project
where
these
women
and
five
women
in
africa
were
paid
to
assist
with
jenkins
development,
and
so
we
ran
them
through
a
series
of
steps
where
they
compiled
a
plug-in
modified
online
help.
C
A
Now
one
of
the
challenges
here
and
one
of
the
embarrassing
challenges
is
that
the
problem
has
not
been
money.
The
biggest
challenge
was
not
getting
some
companies
to
donate
to
fund
this.
It
was
getting
enough
mentors
in
an
open
source
project
to
be
willing
to
help
for
the
month
and
again,
thanks
to
kristen
and
to
meg
for
having
been
willing
to
do
that.
B
C
B
A
We
we
could
the
last
time
I
tried
that
it
didn't
fly
right,
okay,
so
so
yes,
we
that
there's
that
doesn't
stop
us
from
doing
it
in
the
future.
We
absolutely
can
and
certainly
should
ask
for
ask
for
one
of
the
one
of
the
observations
for
of
what
didn't
go.
Well
here
was
we
did
not
enlist
the
reviewers,
so
we
ended
up
receiving
pull
requests
that
did
not
ultimately
reach
the
plug-in
because
we
didn't
have
reviewers
right.
A
So
so,
yes,
that's
that's
certainly
part,
and-
and
that
was
one
of
the
things
that
inspired
this
sheet
in
the
in
the.
Where
is
that
sheet
this
one?
This
sheet
is
specifically
because
of
the
things
we
saw
with
chico
africa
contribute
on.
I
didn't
want
anybody
working
on
documentation,
migration
for
a
plug-in
in
hacktoberfest
that
then
wouldn't
get
a
code
review,
so
each
of
these
that
say
will
review
it's
because
the
maintainer
of
the
plugin
replied
to
me
in
an
email
and
said.
A
E
I
have
two
questions.
Yes,
so
first
question
is
like
I'm
trying.
I
want
to
know
when
you'll
be
putting
the
label
of
oktoberfest
or
in
the
pr,
because
until
you
do
that,
only
after
that
will
be,
the
contributors
will
be
able
to
see
their
pull
request
in
the
hacktoberfest
website
has
been
counted.
E
A
A
E
A
E
Yeah
right,
that
makes
sense,
so
we
might
want
to
do
the
same
procedure,
for
I
think
all
the
contributions
that
we
have
received
till
now,
so
that
the
contributor
also
get
motivated,
seeing
their
pull.
A
D
A
Interesting
update
parent,
okay
and
this
one
okay,
so
this
one:
let's,
let's
open
that
one,
because
this
one
is
now
closed,
let's
find
another
one,
though,
because
I
am
going
to
label
this
one
hacktoberfest.
I
am
now
a
I'm
now,
a
maintainer
of
this
plugin.
I
asked
to
adopt
it,
and
so
I'm
going
to
take
advantage
of
my
my
asking
having
asked
to
adopt
it,
and
I
am
going
to
edit
the
labels
and
give
myself
a
new
label
called
hacktoberfest.
A
A
A
A
But
yeah
and
the
others
are
not
there's
not
actually
enough
useful
in
them
to
to
justify
it
cool,
that's
a
much
better
presentation
than
we've
had
in
past
years.
Oh
okay,
here's
a
point
of
pride.
For
me.
This
one
is
not
labeled
hacktoberfest
but
because
the
docker
project
has
oktoberfest
in
it,
it's
counted
good,
so
dhiraj
did
that.
Did
that
address
address
your
question.
E
A
A
A
Let's
see-
and
I
don't
think
that
that
alissa
has
put
cloudbees
on
this
as
an
example:
no
she's,
not
okay,.
E
A
Well,
well,
and
that's
that's
something
it's
let
me
put
an
action
item
for
me.
Maybe
it
goes
into
the
docs
notes
here
so
discuss
with.
A
A
E
A
E
A
Let
me
let's,
let's
just
go
ahead,
oops
wrong
one.
Let's
pick
that
and
let's
let
me
just
do
a
reminder
to
the
to
the
maintainer,
because
there's
no
reason
we
should
not.
A
E
A
A
Exactly
that
is
a
very
good
question:
meg
oops,
okay,
so
back
to
where
we
were
so.
We've
talked
about
what's
in
progress
with
hacktoberfest
and
wiki
migration
and
she-code,
then
what
we
were
trying
to
do
remember
that
the
theme
of
this
this
session
was
docs
without
the
wiki.
So
it's
what
do
we
do
about
these
set
of
problems?
We've
got
described
up
here
like
many
broken
links
to
wiki.jenkins.io
many
plugins
that
haven't
migrated,
documentation
to
github,
etc,
and
so
the
the
primary
focus
was
on
this
one.
A
And
so
first
topic
was
for
plug-in
docs,
that's
easy!
Do
the
do
the
work,
we're
doing
of
migrating
plug-in?
Docs,
that's
that's
healthy!
It
works.
We
understand
how
to
do
it.
It's
just
a
machinery
thing.
The
general
purpose
docs
oops
we'll
just
have
to,
and
so
here
the
choices
are.
Okay
there's.
There
are,
for
instance,
pages
that
are
very,
very
useful
still
in
the
wiki
and
the
thought
was
we
could
just
host
them
at
a
static
location
and
eventually,
over
time,
migrate
them.
A
What
I've
got
right
now
is
I've
got
more
to
report
here
that
on
my
team
at
work.
A
A
Now,
right
now
they
they
are
not
named
the
same
as
they
were
on
the
wiki.
So
so
that
doesn't
solve
the
whole
problem,
but
it
does
avoid
us
having
to
pay
any
hosting
costs.
We
don't
see
the
bandwidth
charges,
because
github
pages
host
for
free
and
one
of
the
participants
noted
they
can
be
the
exact
static
web
pages
that
we
have
right
now
and
we
could
even
assign
a
custom
domain
like
wiki.jenkins.io
to
the
pages.
A
It
it
it
will
yeah.
So,
for
example,
the
let's
see,
if
I
could,
I
could
show
it
probably
best
by
doing
it
from
my
local
computer.
So
forgive
the
windows
command,
prompt.
A
A
A
A
A
A
A
Good,
so
let's
look
at
it
together.
This
is
perfect,
then
we'll
we'll
review
it
as
a
group
here,
and
so
this
is
oh,
oh
dear,
so
I
didn't
satisfy
the
formatting,
even
when
I
did
it.
Shame
on
me.
Okay,
so
tell
a
story.
First
notice,
this
red
block
here
what
happened
was
last
last
week
when
we
did
the
security
release.
A
This
was
out.
It
was
indented
two
spaces
less
than
it
is
even
right
now
and
as
such
was
not
rendered
correctly
notice
that
the
automated
formatting
of
the
changelog
has
pushed
it
out
two
more
spaces.
So
it's
fixed
even
more.
The
mistake
that
I
made,
but
at
least
the
mistake
I
made
was
rendering
correctly
so
now
we
need
to
look
at
2.316.
A
All
right
so
dhiraj,
what
do
you
think
bump
the
spotless
maven
plug-in
that
should
probably
be
listed
as
skip
change?
Large
shouldn't
it?
Yes,
okay!
So
let's
go
find
the
jenkins
core
pull
requests.
A
A
A
A
A
E
The
legend
is
also
an
official
term
for
this.
A
A
A
A
E
A
B
A
A
D
A
A
A
A
A
A
A
No,
this
one
is
intentionally
hidden
because
it
was
included
already
in
2.315,
so
this
is
just
a
merge
to
make
2
2.315
visible
in
master
branch
and
later
okay.
So
I
intentionally
hit
this
one
because
2.316
is
not
a
security
release.
Okay,
good
question,
very
good
question
had
had
exactly
that
conversation
here,
let's
go
there.
We
had
exactly
that
conversation
in
the
poll
request
itself,
where
I
think
it
was
tim
jacom
asked.
Should
this
be
in
the.
A
A
A
A
C
A
C
A
A
A
C
A
Understand
why?
Because
because
I
didn't
think
that
I'd
changed
anything
and
yet
yeah.
Absolutely
so,
let's
see
if
oh,
oh,
wait
a
sec,
maybe
it's
yeah,
look
what
happened!
It
detected
that
these
are
changes
to
the
pipeline,
shared
library,
okay
and
they
did
they
do
change
the
build.
They
could
change
the
build
and
therefore
they
need
to
be
reevaluated.
A
A
A
For
you,
okay,
great
okay,
then
let's
look
at
other
labels.
Ready,
okay,
update
the
french
translation,
this
one-
I
just
don't
know,
but
I
trust
that
tim
or
somebody
else
will
approve
it.
It's
got
two
native
french
speakers
who
reviewed
it.
Angelique
and
vadak
are
both
native
french
speakers.
As
far
as
I
know,
you
put
a
lot
of
open
words.
I
think
oh
good,
okay,
so
and
it's
it's
running
the
checks
again.
Okay,
so
when
tim
wakes
up
he'll
see
things
or
have
been
through
the
checks.
A
A
The
proper
labels
are
set
yes
and
it
does
not
need
upgrade
steps
and
it
doesn't
need
to
back
port
okay,
good
all
right,
so
we
reviewed
that
one.
We
have
to
remember
this
by
the
way.
This
is
this.
The
reviewing
ready
for
merge
is
a
great
way
to
to
get
ahead
of
some
changes
that
are
likely
going
to
merge.
A
C
Wait:
okay
fix
that.
C
C
C
C
D
A
Okay-
and
I
think
we're
ready
to
commit
that
to
say
yes
update,
that
comment,
okay,
great,
and
that
should
also
help
us.
So
this
gives
this
says
tim
is
tim,
can
do
merges
in
the
next
three
or
four
hours
of
the
things
that
are
ready
for
marriage
and
they'll,
be
in
2.316,
and
we
think
they'll
look
good
in
the
automated
change
log.
A
A
Okay,
so
I
think
we've
covered
the
topics
that
we
had
intended
to
maybe
dhiraj.
If
you
would
be:
oh,
no
actually
kristin,
you
were
the
one.
I
wanted
to
beg
for
help
on
this
one,
if
you'd
be
willing
separately,
to
look
at
sure
at
the
the
steps
in
this
thing.
Okay,
could
you
stand
for
me
to
do
a
five
minute,
quick
overview
of
this
yeah
sure
this.
A
C
A
C
You're,
like
you
know,
like
dude,
if
you
want
to
because
I
know
I
mentioned
you
want
to
like
roll
it
out.
I
was
like
man
it'd,
be
interesting
to
run
this
before,
like
a
contribute,
thought
like
a
tribute
on
or
like.
If
there
was
like
any
type
of
conference
like
he
could,
we
could
roll
it
out
as
like
a
getting
started
program,
but
also
it's
a
good
workshop
too.
Okay
I'll.
Let
you
talk
now.
A
Exactly
see,
this
is
even
something
we
might
consider
using
this
for
chico
africa
instead
of
instead
of
the
pipeline
thing
or
in
addition
to
it,
because
this
is
this
is
also
an
end-to-end
experience
for
a
new
contributor.
A
So
they
can,
they
can
start
from
gee
I've
never
done
any
of
this
and
and
go
through
and
by
the
end
of
it
they
have
made
significant
and
valuable
contributions
to
at
least
one
jenkins,
plug-in
and
they're.
In
fact,
by
the
time
they
reach
the
end
of
this
by
the
time
they
reach
page
18,
or
so
they
are
really
ready
to
adopt
the
plugin,
because
they've
been
through
four
or
five
pull
requests.
They've
they've
shown
clear,
clear
progress,
etc.
I
mean
it's
it's
that
kind
of
oh
yeah
this.
This
really
is.
A
So
the
first
story
is
choose
one
of
the
hundred
plus
plug-ins
that
are
up
for
adoption
and
and
that's
you
can
find
those
plugins
here
and
if
we
pick
one
that's
up
for
adoptions,
like
the
schedule
build
plug-in.
It
has
a
label
over
here.
Adopt
this
plug-in
here
are
110
plugins
that
are
up
for
adoption.
Pick
one
of
these
and
that's
interesting
to
you
and
start
doing
these
steps.
First
be
sure
it
has
a
jenkins
file.
A
Then
update
the
base
jenkins
version,
and
this
one
is
where
jenkins
the
the
current
palm
now
has
this
concept
that
you
declare
what
the
base
jenkins
version
is.
The
minimum
jenkins
version
you'll
support
and
we
have
a
page
on
jenkins.io
that
recommends
a
specific
base
version
number
and
right
now
it's
this
one
2.289.1.
A
So
again
that
one
now
has
narrowed
the
breadth
of
things
versions:
they're
supporting
and
is
helping
the
plug-in
maintainer.
Let's
make
life
simpler,
okay,
now
that
it
and
it
just
keeps
going
from
there
okay,
so
next
stop
was
enable
more
spot
bugs
checks,
so
by
default
spot
bugs
is
enabled.
I
turned
it
up
from
the
default
level
to
threshold
low
effort
high,
so
maximum
involvement
of
spot
bugs
and
okay.
A
D
A
Then
use
dependable
to
update
depend
automate,
automate
dependency
updates,
enable
incremental
delivery,
so
that
we
can.
We
can
test,
builds
easier.
This
one
this
last
one
kristin
the
convert
ap.
This
was
one
that
I
discovered
while
watching
sasha
do
work
on
a
plug-in
he
was.
He
was
doing
these
steps
on
what
he,
what
he
showed
was.
Oh
yeah,
here's
this
big
plug-in.
In
his
case
he
was
working
on
the
white
source
plugged
in
inside
that
plug-in.
A
A
A
C
A
C
A
C
A
A
A
A
One
with
a
six
digi
six
digit
install
count
is
not
going
to
be
quiet.
That's
not
a
that's,
not
low
visibility,
exactly
the
other
is
the
dependencies
tab
here
gives
us
a
hint
of.
Oh
here's
what's
required,
and
here's
here
are
the
things
that
might
depend.
Here's
how
you
would
no
there
isn't.
Oh,
no
there
it's
so
it's
just
this
one's
actually
got
relatively
few
dependencies.
I'm.
C
Impressed,
I
expected
many
more
me
too.
Actually
thinking
about
this
is:
do
we
have
a
thing
how
to
install
the
pendabot
or
any
of
the
other.
A
C
A
C
A
Okay,
actually,
let
me
just
put
it
in
there
jenkins.
Let's
see
github.com
jenkinscr
slash
dot
github.
I
was
just
reading
this
today.
I
was
really
truly
impressed
dot,
github
releasedrafter.adoc
here
is
this
beautiful
document
with
table
of
contents
that
describes
how
you
enable
it.
It
has
links
to
videos
that
describe
it.
Everything.
A
All
right
so
again,
kristen
if
you're
willing,
if
ideas
come
to
mind
by
all
means,
please
please
add
them
or
add
comments
or
suggestions
there
and
then
dhiraj
you,
and
I
will
try
to
do
this
if
you're,
okay,
helping
me
with
this,
we'll
try
to
craft
this
together
as
a
as
a
both
a
combined
blog
post
and
a
tutorial.
A
Thank
you
so
so
we'll
and-
and
I
think
I
think
what
I
may
do,
I
wonder
dhiraj,
maybe
you
and
I
want
to
collaborate
through
a
separate
repository
and
then
because
then
I
can
give
you
right
permission
to
it
and
then
we'll
we'll
grab
it
together,
great,
get
it
together
and
I'll
I'll.
Send
you
a
link,
because
I've
got
a
little
a
little
github
git
server
that
I
run
on
my
own,
my
own
network.
So
I
may
send
you
a
here:
you
can
log
into
this
location
and
we'll
collaborate
there.