►
From YouTube: 2020 09 21 GSoD Office Hours
Description
Jenkins Google Season of Docs office hours Sep 21, 2020
A
B
A
A
A
B
A
C
C
B
A
B
B
Okay!
So
as
well
speaking
of
previous
meeting,
we
are
using
this
template
to
create
the
issues
so
the
first
part
the
station
and
central
information.
We
have
the
page
to
migrate
with
the
link
and
the
what
they
need
to
do
so,
for
example,
the
proposal,
in
this
case
it's
only
redirects
for
the
indicated
destination.
B
A
B
A
A
A
That's
that's
what's
actually
quite
important
here.
The
content
here
is
this
block
and
that's
it
yeah
all
the
rest.
It
says,
move
to
the
readme
and
is
a
bunch
of
comments
and
questions
from
users
that
we
would
not
put
into
the
documentation.
So
so
the
the
content
has
already
moved
actually-
and
that's
in
this
case-
yes,
right
and
and
even
better.
The
content
here
is
much
much
more
useful
than
that.
A
A
Well,
but
so
so,
because
I
don't
think
we
have
much
choice
there,
we've
got
to
redirect
because
wiki
is
read
only
so
this
top
page.
Let's
go
there.
This
page
oops
this
page
right
here,
the
one
that
opens
when
I
click
the
top
link
is
in
fact
only
readable.
No
one
can
write
to
it
right.
Therefore,
it's
not
going
to
help
anyone
find
the
information
they
have
to
search
and
get
lucky
that
they
find
this
hyperlink.
B
A
C
A
C
A
B
A
B
A
B
A
No
way
no
way,
I
think
it's
clear
to
me.
I'm
just
concerned,
I'm
not
sure
I
want
that
level
of
test
for
these
first
time,
particular
because
we're
coming
up
in
about
10
days,
we've
got
packtoberfest
starting
and
for
there
are
many
folks,
many
people
there
who
would
who
will
help
us
and
then
quickly
drop
off
because
they
did
something
just
for
the
fun
of
it
and
we
want
to
get
as
good
results
from
them
as
we
can.
B
So
but
for
example,
what
do
you
right
now?
You
are
doing
a
trade
on
the
previous
issue.
I
have
created
the
joke.
I
I
get.
I
guess
this
is
the
important
to
work
to
do
so.
For
example,
I
I
go
there
and
do
the
research
and
create
the
issue,
and
the
next
step
you
read
and
a
mark,
for
example,
is
good
issue
edit,
honest
remove
the
the
content.
You
guys
is
not
important
for
first,
usually
yeah
and
said
I
I
guess
it's
a
good
path
to
follow.
A
A
B
A
B
A
A
A
A
A
That
that
is,
that's
wonderful,
okay,
so
that
so
then
the
the
task
there
really
is
visit
those
and
say
yes,
these
are
good
first
issues
and
then
label
them.
And
if
I
remember
correctly,
you
don't
you
we
haven't
yet
granted
you
permission
to
assign
that
label
so
that
that
assures
us
a
two-step
process.
For
now
and
as
we
get
better
at
this,
we
may
grant
you
permissions
to
allow
you
to
do
good
first
issue
as
well.
B
A
Go
ahead
please,
this
one
is,
is
sort
of
a
hot
spot
for
megan
for
me,
because
this
should
probably
now
be
named
well,
so
this
one's
talking
about
all
sorts
of
things,
agent
related
and
there's
very
little
here,
but
there's
an
awful
lot
that
we
need
to
know
about
agents
and
so
yeah.
So
this
one
is
a
poster
child
of
a
wiki
page
that
has
lots
of
very
good.
Oh
no,
this
one
doesn't
have
this
one's
not
terribly
useful.
A
Okay,
this
this
target
page
needs
lots
of
information
on
it
and
has
nothing
particularly
useful
for
a
typical
user.
This
this
script,
monitor
and
restart
offline
agents
is,
is
a
very
specialized
unique
thing.
Not
not
the
thing
that
needs
to
tell
us
here
are
these
different
types
of
agents
and
here's
when
you
use
an
ephemeral
agent
and
so
exactly.
B
B
A
Right
so
this
one
this
one,
this
issue
has
a
dependency
that
we
need
to
get
the
existing
pr
in
before
this
one
will
make
any
sense.
Okay,
so
that's
that
one
there's
a
great
way
to
to
say
that
something
like
this,
this
pr,
this
issue
needs
pr
number
and
then
we
we
find
it
see
post
initialization
I
have
I'll
have
to.
Let
me
go
look
for
it
really
quickly
here,
because
what
it
really
needs
is
exactly
the
issue
that
the
pr
that
you've
submitted.
B
C
A
Review
yeah
and
oleg
won't
be
able
to
review,
he's,
probably
offline
for
at
least
another
week
or
two
potentially
a
month
with
other
things,
but
I
should
be
able
to
help
with
it.
So
that's
that's
a
that's
a
good
one
that,
knowing
that
it's
we've
got
another
issue
that
is
pending
on
it,
good,
very
good,
okay.
So
this
one
this
one
for
me,
I
would
not
flag
as
good
first
issue,
because
it
has
this
dependency.
A
B
B
A
B
A
Okay-
let's
see
so
it's
subset
of
how
to
report
a
bug,
okay
and
and
that
it
may
be
that
the
content
is
not
in
how
to
report
a
bug.
But
my
guess
is:
this:
information
is
probably
well.
Let's
see
when
was
it
last
yeah
here
we
go
look
created
in
2013.,
so
the
page
is
seven
years
old
and
this
class
of
failure
hasn't
hasn't
been
common
with
jenkins
for
a
very
long
time.
B
A
A
B
A
A
But
this
is
this:
is
these
are
great
candidates
for
for,
for
example,
the
one
that
you
highlighted
here
in
yellow
static
analysis
in
pipeline
static
analysis
is
quite
a
popular
topic
and
so
having
having
that
correctly,
redirect
will
probably
be
a
big
help
and
point
it
to
the
warnings
ng
plug-in
rather
than
to
to
this,
because
I
think
yeah.
In
fact,
this
is
early
documentation
of
warnings
ng.
This
is
but
it's
frozen
in
time
now,
and
so
the
current
documentation
for
it
is,
is
on
the
plugin
page.
A
A
B
A
A
B
A
A
A
B
A
A
B
A
A
Oh
and
now
now,
okay,
that's
a
that's
an
interesting
one.
I
think
we
would
be.
We
could
be
potentially
allowed
to
embed
the
video
recordings
of
those
into
these
pages.
I
hadn't
I
haven't
checked
with
cloudbees
to
see
if
they're
willing
to
allow
us
to
after
the
conference
is
complete,
embed
videos
of
those
into
jenkins.io
pages.
But
maybe
let's
let
me
put
that
as
an
action
item
for
me
to
see
because
we've
we've
done
it
before,
with
with
video
recordings
of
other
conferences.
A
Create
a
new
one,
absolutely
yeah!
If
someone
wanted
to
to
rephrase
it
just
that,
for
me
feels
like
a
lot
of
work
that
I'd
rather
not
do
if
and
and
it
doesn't
help
promote
their
videos
either,
so
they
may,
they
may
actually
like
that.
Hey
we
placed
it
there,
so
it
helps
promote
the
fact
that
they
did
this
video.
C
And
I'm
I
I've
seen
the
demystifying
through
logging,
video
and
it's
excellent,
but
I
I
think
that
they've
done
it's
pretty
much
stuff,
that's
applicable
to
both
the
open
source
and
cloud
bci,
but
I
think
there
may
be
more
there's,
definitely
something
where
it
talks
about
a
feature
you
get
in
cloud:
bci,
that's
not
in
there.
It
might
aggravate
the
community.
I
don't
know
right
valid
point.
B
B
A
A
A
A
C
C
B
B
C
C
I've
spent
most
of
my
career
documenting
for
developers
and
I've.
I've
actually
done
tests.
I
can
put
any
crap
at
all
in
a
paragraph
and
ask
them
to
review
it
and
they
will
see
tables,
they
will
see
lists,
they
will
see,
charts
and-
and
I
can
put
some
absurdity
in
a
paragraph
and
almost
nobody
will
catch
it.
D
A
C
A
A
The
page
here
describes
places
where
you
can
contribute.
I
just
submitted
the
update
on
this
page
this
morning
and
boldly
included
the
jenkins
website.
What
we're
talking
about
here
as
one
of
the
featured
projects
with
our
list
of
good
first
issues
as
candidates
that
they
should
be
considering
working
on,
but
we've
only
got
11
good
first
issues
and
last
year
I
think
we
we
completed
10
or
15-ish
good
first
issues
in
the
first
week
or
so
so
so
we'll
be.
A
A
That's
that's
what
I
was
thinking
is,
and
I
thought
this
time
it
might
be
fun
jonathan
to
have
you
be
one
of
the
presenters
and
vlad,
be
one
of
the
presenters
and
me
be
a
presenter
and
we
could
rotate
through
the
three
of
us
saying:
hey,
look,
here's
here's
this
piece
of
it
and
here's
this
piece,
maybe
jonathan!
We
have
you,
show
how
to
redirect
or
you
know
each
of
us
chooses
a
piece
and
we
consider
doing
it
sometime
during
october.
B
D
Yes,
I
would
be
glad-
and
also
tomorrow,
I'm
presenting
on
the
meetup,
which
was
organized
by
cdf,
and
I'm
going
to
talk
about
jenkins
and
well
going
to
engage
newcomers
to
jenkins
and
playing
junkies
is
well
not
so
complex,
as
some
people
think,
and
so
you
can
easily
start
contributing
to
jenkins.
This
is
kind
of
the
message
that
I
would
like
to
deliver
and
I'm
going
to
talk
about
jenkins
and
docker
and
also
see
how
it
is
possible,
using
official
gem
docker
image
to
call
docker
agents
inside
pipelines,
declarative
pipelines,
something
like
this.
D
Something
tutorial
like
which
we
still
have.
I
guess,
on
jenkins
dot
io
is
still
pointing
to
outdated
general
considerable
ocean
docker
image
right.
We
have
intention
of
substituting
it
with
with
official
docker
engine,
so
I'm
going
to
present
it
tomorrow
see
how
is
the
feedback
and
in
case
if
there
will
be
no
well.
D
C
C
A
B
Terminology
well,
but
a
issue,
just
a
converting
terminologies
may
be
caused
to
some
problems.
For
example,
imagine
if
thousands
of
pages
just
receiving
prs,
we
have
a
dq
200
just
to
update
the
terminology
terms
and
we
doubter
review
the
content
and
update
the
content.
What
do
you
care
about?
What
did
you
guys.
A
A
I
think
if
we
do
it
get
rep
minus
l
master,
we
can
identify
some
pretty
quick
okay,
so
blogs
have
actually
been
converted
already
as
a
section
and
what
else
has
I
believe
change
logs
have
in
in
this
one
but
for
instance,
administration
as
a
section
has
not
been
touched
and
managing
as
a
section
hasn't
been
touched,
so
those
might
be
reasonable
issues
as
a
group
to
say,
convert
all
of
the
pipeline
references
to
master
convert
all
of
the
system
administration
to
master
yeah,
it's
better.
I
I
guess
it's
better.
A
By
section
I
mean
for,
for
instance,
security
hat,
let's,
let's
do
it
differently,
minus
w
and
even
that
yeah.
So
so
the
security
advisories,
I
know,
have
been
converted
because
daniel
beck
did
those
very
early
but
others.
For
instance,
google
summer
of
code,
we've
got
lots
of
places.
We
could
do
those
conversions
and
do
them
as
as
blocks
or
groups.
A
I
think
so
yeah.
I
would
think
that,
and-
and
it's
a
section-
so
it's
not
so
large-
that
they
risk
being
overwhelmed
by
they
made
a
change
in
their
review
and
the
change
they
made
was
flawed
and
the
reviewers
rejected
it
and
threw
the
whole
pull
request
away,
whereas
if
you're
just
on
a
single
section,
a
change
is
probably
a
mistake-
is
relatively
small
and
can
be
corrected
without
without
destroying
the
entire
pull
request.
B
C
A
Oh
here,
let's
put
yeah
so
so,
let's
put
it
there
good.
So,
let's
do
it
that
way.
We
could
put
it
in
the
in
our
video
in
our
meetup
session
and
set
proposed
section.
So
here's
jonathan,
I
think
this
is
what
you
were
requesting
right
is:
could
we
just
have
some
proposed
sections
for
it
and
put
those
into
the
list
and
then
generate
issues
for
them
exactly
because.
A
C
C
C
D
And
just
oh
mark,
I
just
wanted
to
mention
continue
this
terminology
stuff,
which
mentioned.
I
noticed
that
he
was
searching
for
master.
My
understanding
master
is
kind
of
outdated,
which
is
going
to
be
replaced
by
controller.
Correct,
that's
right
and
it
looks
like
there
is.
There
are
not
many
sections
where
controller
is
mentioned
in
our
documentation,
so
there
will
be
a
lot
of
kind
of
changes
right.
C
A
A
And
on
jenkins
terminology:
oh,
this
is
from
marky
jackson
right,
okay,
so
so
this
one
is
the
the
introduction
to
it
and
then
then
it
continues
with.
There
are
actually
there's
a
more
recent
poke.
Oh
no,
this
one
is
the
most
recent.
This
one
is
june
where,
where
it
was
updated
and
then
alex
earl
posted
one
on
the
continuous
delivery
foundation
about
the
next
next
level
of
this.
A
C
Something
to
think
about
as
we're
looking
at
stuff
during
the
week
right
absolutely
and
then,
where
do
we
put
links
and
what
do
they
look
like
is
still
an
issue
but
yeah,
because
what
I'm
thinking
is
for
if
people
are
going
to
try
to
make
for
prs
that
get
them
a
t-shirt,
that
a
lot
of
people
might
at
the
beginning.
Do
one
of
these
and
then
be
able
to
go
on
move
on
and
do
something
a
little
more
interesting.
A
C
C
Yes,
although,
but
will
you
see
that
and
how
I
did
that,
I'm
not
you
would
see
each
line
that
got
changed,
but
if
you
know
you've
got
to
read
them,
but
so
to
somebody
who's
never
been
through
these.
As
we
all
know
this,
somebody
who's
never
been
through
this
as
a
reader.
It's
like
not
a
big
deal.
You
just
do
a
global
search
and
replace
and
you're
done
right
and
yeah.
We've
we've
all.