►
From YouTube: 2022 09 08 Docs Office Hours
Description
Documentation office hours Sep 8, 2022 (Europe) with topics including Google Summer of Code, Hacktoberfest, and the Jenkins documentation site. Includes an overview of the backend extension indexer and the improvements made by Basil Crow to successfully index more of the Jenkins plugins.
A
Down
three:
two:
one:
welcome
to
the
european
jenkins
docs
office
hours.
This
is
the
september
8th
european
edition.
Today
we
have
a
few
topics
regarding
things
like
the
lts
release
that
we
just
had
go
out
yesterday,
google
summer
of
code
and
a
few
other
things
that
are
coming
up,
such
as
devops
world
and
oktoberfest.
A
A
C
C
So
as
of
now,
I
was
able
to
get
it
manually
and
get
some
result
done,
but
getting
that
done
automatically
does
not
seem
to
be
feasible
in
the
short
run.
So
the
change
that
we
are
proposing
is
to
simply
say
that
this
could
take
any
step,
and
maybe
then
we
can
say
that
try
out
the
slip
at
generator.
For
instance,
if
you
want
more
information
on
this,
so
we
can
create
a
manual
ascii
dock
that
will
replace
the
one
which
has
the
the
incorrect
content
on
the
page
drive
down.
C
B
C
Yes
sure
the
health.html
that
is
associated
with
the
program
in
that
the
health
that
is
listed
in
the
lag
tax
does
not
have
any
surrounding
ul
or
oven
tax.
So
the
problem,
and
because
of
that,
the
main
website,
which
has
the
other
listings,
also
it's
getting
confused
and
the
indentation
is
going
all
over
the
place
of
the
lists.
B
Yeah
so
that
that
seems
like
a
okay,
maybe
in
a
perfect
world,
the
tool
would
somehow
adapt
to
flawed
html,
but
really
that
html
is
not
going
to
render
correctly
anyway
right.
That's
now,
relying
on
on
a
browser
that
will
accept
an
li
tag
outside
of
the
list
that
defines
that
there
should
be
an
li
tag.
C
C
But
for
the
short
term
so
that
the
website
works
properly
and
somebody
who
goes
on
that
page
does
not
sit
waiting
for
30
seconds
for
the
page
to
crash.
Finally,
we
could
give
an
alternate
content
that
says
that
okay,
this
can
take
any
step
and
refer
to
the
snippets
editor
for
more
details,
something
that
japanese
registered
as
the
solution
to
that
problem
on
the
channel.
A
B
B
Right,
okay,
so
so
jenkins
has
a
concept
of
extension
points.
What
this
is
is
it
allows
a
it
allows
one
thing
to
declare
I'm
creating
something
that
other
people
could
extend
and
the
other
people
then
are
given
a
place,
a
technique
that
they
can
use
to
extend
that
thing
to
implement
an
extension
of
it.
So,
for
instance,
if
we,
instead
of
if,
if
you
are
willing
to
edit
your
url
up
at
the
top
instead
of
the
word
junit
change
it
to
the
word,
get
okay.
B
So
now
we're
getting
one,
that's
familiar
to
me
all
right.
What
the
what's
happened
here
is
the
git
plugin
has
implemented
an
extension
point
called
build
chooser
and
the
build
chooser
then
has
been
implemented
in
four
plug-ins.
In
total,
the
alternative
build
chooser,
the
flaky
test
handler
the
garrett
trigger,
and
in
the
git
plug-in
they
each
allow
a
separate
plug-in
to
add
capability
to
the
get
plug-in.
B
B
That
looks
at
the
whole
suite
of
plugins
and
reads
all
the
extensions
and
all
their
implementations
and
then
generates
these
pages.
So
vihan
will
probably
recognize
this
pattern,
because
this
is
exactly
the
kind
of
pattern
that
the
pipeline
step
stock
generator
uses
right
where
it
reads
all
the
plugins
massages
them
runs
them
through
a
series
of
transformations
and
presents
pages.
B
Well,
the
back
end
extension
indexer
had
been
unmaintained
for
quite
a
while,
and
I
started
a
pull
request
that
attempted
to
modernize
it
to
java
11..
But
I
couldn't
do
enough
to
get
it
all
the
way
to
done,
and
I
just
stopped
because
I
other
things
had
to
take
priority.
Thankfully,
basel
crowe
has
detected
that
work
and
said:
hey
he's
going
to
take
it
the
next
step
and
so
he's
doing
the
the
awesome
work
that
basel
does
of
taking
taking
this
thing
and
seeing
hey,
can
we
fix
it?
B
So
that's
the
work.
That's
happening
right
now
in
this
back
end
extension,
indexer
it
used
to
be
and
and
again
v
han
will
recognize
this
pattern.
It
was
built
with
java,
8
or
in
back
end
extension
index
or
java
7
or
maybe
java
6.
It
was
that
old
and
it's
now
been
updated
that
the
spot,
bugs
warnings
are
generally
resolved,
if
not
they're,
at
least
suppressed
it
compiles
with
java
11.
B
B
B
It
actually
won't
alter
anything
in
the
ui
right.
The
ui
should
remain
the
same
and-
and
we
haven't
had
the
same
level
of
complaints
about
this
ui
because
it's
intensely
focused
on
developers
right.
This
is
not
not
really
useful
to
someone
who's
using
jenkins
pipeline.
This
is
this
is
a
developer
centered
page.
B
A
A
Looking
into
the
case
by
case
of,
what's
going
on
there,
the
changelog
and
upgrade
guide
have
been
published,
and
there
is
also
a
blog
post
that
was
requested
from
the
continuous
delivery
foundation
for
their
blog,
that's
available
here
in
the
agenda
and
has
been
pushed
out
there
they've
also
tweeted
and
posted
on
linkedin
about
it.
So
the
releases
is
going
well.
Thank
you
to
everyone
who
helped
and
participated,
and
and
just
did
anything
to
make
this
a
success.
A
A
A
Okay,
great
best
show
ever
next
up
on
the
list.
We
do
have
the
next
lts
coming
up
2.361.2
the
release
lead
request
has
conversation
has
been
started
in
the
developer
mailing
list.
Chris
stern
is
actually
interested
again
and
has
shared
that
interest
right
now.
The
plan
release
date
is
october
5th.
So
once
we
get
the
ball
rolling
on
that
the
backboarding
change
log
upgrade
guide,
everything
will
start
being
compiled.
A
Next,
up
on
our
agenda,
just
quick
talk
about
devops
world
2022,
which
is
september
27th
to
the
29th.
This
is
big.
This
is
back
in
person
which
is
really
exciting
and
we
have
a
bunch
of
great
talks
and
subjects
that
will
be
displayed
and
just
and
shared
with
the
entire
community
there
mark
did
you
want
to
mention
the
poll
requests
and
modernizing
plug-in
progress.
B
The
workshop
is
how
to
adopt
a
plug-in
or
how
to
modernize
a
plug-in
and
prepare
to
adopt
it,
and
what
we're
going
to
do
is
take
participants
in
our
workshop
live
through
the
experience
of
submitting
useful
and
valuable
pull
requests
to
the
jenkins
plug-in
of
their
choice.
We've
adopted
bruno
john
mark
and
I
have
adopted
it's
actually
over
25
plugins
and
are
preparing
those
steps.
The
the
improvements
in
an
answer
book
we'll
then
ask
the
students
hey.
B
B
A
B
A
B
B
B
If
you
scroll
a
little
bit
further
down
the
thing
that
I
find
most
attractive
about,
this
is
they've
got
a
proposal
here
that
attempts
to
allow
non-code
contributions
to
be
considered
in.
Oh,
let's
see
it
must
be
up
above
kevin.
Sorry,
I
know
I'd
seen
it.
Oh
yes,
new
for
2022
go
down
about
halfway,
keep
going
down
down
a
little
further
right.
There
whoa
see,
on
that
right
hand,
side,
non-code,
contributions.
B
And
this
gives
that
us
a
chance
for
them
for
non-code
contributors
to
also
be
recognized
now,
thankfully,
jenkins
documentation
is
all
as
code,
so
it's
easy
to
recognize
that,
but
one
of
the
gaps
we
had
in
years
past
was.
It
was
very
difficult
to
recognize
contributions
from
translators
who
were
submitting
their
contribution
through
through
crowd
in
we've,
got
a
very
nice
translation
front
end
over
the
top
of
our
of
some
of
our
plugins.
B
D
D
B
What
this
this
further
lobbies
that
we
may
have
benefit
by
putting
extra
energy
or
having
others
put
extra
energy
into
internationalizing
and
localizing
and
and
they're
both
valuable
activities.
Internationalization
typically,
is
done
with
pull
requests,
localization
commonly
is
done
through
crowding,
or
we
hope
it
will
be
more
and
more
done
through
crowding
yeah.
So
thanks
kevin,
that's
that's
the
the
current
story
on
hacktoberfest
at
a
minimum.
B
D
B
So,
on
the
good
side
that
good
first
issues
query
identifies
several
jenkins.io
issues
that
a
brand
new
user,
a
brand
new
person
with
no
jenkins
experience,
could
successfully
help
with
this.
So
these
things
are
intended
to
be
for
complete
novices.
Now,
if
you
go
back,
there
are
also
places
where,
but
what
if
I've
got
some
jenkins
experience?
Okay,
these
labeled
with
hacktoberfest
are
intended
to
be.
You've
got
some
experience,
but
you'd
still
like
to
contribute.
B
So
so
we've
got
two
layers
there.
Now,
if
you
go
back
to
the
page
there's
yet
another
challenge,
which
is,
we
need
to
review
the
existing
open
issues,
yeah
that
that's
the
right
one
to
open
kevin
exactly
because
there
are
146
open
issues
and
only
a
tiny
fraction
like
roughly
the
first
30
have
actually
been
checked
to
see,
which
ones
are
good
first
issues
which
one
should
be
assigned
to
hacktoberfest
there.
They
need
some
skill,
so
so
we've
got
work
to
do
there
and
office
hours
is
a
good
place
to
do
that
work.
B
B
B
So,
if
you'll
click
to
open
that
migration
report,
we
can
see
get
a
hint
of
what
this
thing's
like.
So
what
this
is
is
this
is
a
report
that
tells
us
what
frat,
which
plugins
have
completed
their
migration,
to
host
their
documentation
in
github,
and
it's
a
good
number
at
the
top
at
the
very
top.
We
see
that
there
are
over
900
plugins
that
have
done
it,
but
unfortunately
there
are
still
over
900
that
need
to
do
it.
B
B
You
can
see
that
one
ansible
has
21
000
installations
and
still
is
to
do
now.
Ansible
is
a
little
awkward
because
if
you
click
it
you'll
see
now,
if
you
go
over
on
the
right
hand,
side
to
github
and
click
the
open,
pull
requests
so
tops
top
left.
Yeah
you'll
see
move
docs
to
github,
mark
wait's
pull
request
from
a
year
ago
that
hasn't
been
merged.
B
B
So
so
I
guess
what
I've
highlighted
is
plug-in
migration
plug-in
documentation.
Migration
is
a
good
hacktoberfest
topic.
However,
it
would
be
best
if
we
could
find
a
way
to
flag
those
plugins,
which
we
know
have
active,
maintainers
and
and
that's
a
more
challenging
topic,
because
it
means
we
have
to
ask
the
maintainers.
Are
you
active?
Will
you
commit
to
review
a
documentation
full
request
to
your
plugin
and
and
many
of
them
either
won't
respond
to
the
request
or
may
say
yes
and
then
not
do
it.
B
So
now
there
is,
there
is,
I
guess,
there's
one:
there
is
one
bright
spot
in
this.
The
earlier
thing
we
talked
about
for
devops
world
means
that
bruno
mark
and
john
mark
have
adopted
25
plugins
of
those
25
plugins.
We
promise
to
review
documentation,
pull
requests,
so
we've
got
at
least
a
list
of
of
up
to
25
that
we
know
someone
will
review
those.
B
Well
done
bruno
so
so
we've
talked
about
two.
I've
talked
about
two
good
things
for
hacktoberfest:
let's
talk
about
a
bad
one
tasks
intentionally
not
not
recommended
for
hacktoberfest,
and-
and
this
is
one
where
we've
tried
this
one
in
the
past-
and
we've
done
it
two
or
three
years
now
and
you
can
see
the
results
of
our
attempts
and
that's
why
I'm
explicitly
saying
we
don't
make
this
same
mistake
again
this
year,
click
that
wiki
migration
pull
requests.
B
What
these
are
is
these
are
issue
or
these
are
pull
requests
in
jenkins.io
that
are
flagged
with
the
wiki
migration
label,
and
this
is
for
jenkins,
user
documentation,
not
plugin
documentation.
So
if
you
look
at
the
topics
here,
it's
things
like
how
do
you
diagnose
build
failures?
How
do
you
use
parameters?
How
do
you
write
a
unit
test?
B
How
do
you
do
internationalization?
Those
are
all
things
that
are
not
really
specific
to
a
plug-in,
they're
general
purpose
topics
and
what
people
have
done
here
is
they
have
done
exactly
what
we
asked
them
to
do.
They
took
the
wiki
page,
converted
it
into
asciidoc
format
and
submitted
as
a
pull
request.
The
problem
is,
inevitably
the
wiki
pages
were
out
of
date,
and
these
people
didn't
know
which
things
were
wrong
and
which
were
right
and
of
course
they
didn't.
B
They
were
new
contributors,
so
they
submitted
these
transformations,
but
the
transformations
can't
be
merged
because
of
the
inaccuracies
that
are
in
them
and
what
does
it
take
to
fix
the
inaccuracies?
It
takes
an
expert
jenkins
user
or
an
expert
jenkins
administrator,
which
means
we
didn't
help
a
whole
lot
by
submitting
these
pull
requests
right,
because
all
we
did
is
pile
up
a
bunch
of
work
for
experts
who
already
have
more
than
enough
work,
gotcha,
okay.
So
so
this
one
back
to
the
back
to
the
the
google
doc.
B
That's
why
I
would
strongly
recommend
we
not
invite
people
to
do
wiki
migration.
This
time
we
we
rather
recommend
them
away
from
wiki
migration,
because
it
just
doesn't
and
it
doesn't
reach
all
the
way
to
the
user,
because
it
cues
something
up
for
experts
to
then
review
and-
and
it's
not
even
just
review,
it's
really
review
and
correct
right
yeah
if
it
were
just
review,
that's
a
different
thing,
but
inevitably
pages
that
were
written.
Seven
or
ten
years
ago
are
now
incorrect.