►
From YouTube: 2023 05 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
Welcome
to
the
Jenkins
documentation
office
hours
today
is
May
11
2023,
and
this
is
the
EU
US
edition.
Today
we
have
myself
Mark,
Waite
and
vernova
Rockton
thanks
for
joining
and
we'll
welcome
others
as
they
come
in
on
the
agenda.
I
have
the
April
newsletter,
which
we
just
published
yesterday.
The
pipeline
step
reference
had
an
issue
just
this
past
week.
We've
got
some
temporary
fix
involved,
but
we'll
discuss
that
a
little
bit
more
Google
summer
of
code
is
officially
now
underway,
with
the
projects
and
contributors
being
announced.
A
A
end
of
life
notifications
in
Jenkins
core,
which
is
something
that
we've
been
discussing
and
going
back
and
forth
on
what
that
might
look
like
and
what
we
can
do
for
that.
The
early
end
of
life
for
cento7
in
Jenkins,
again
something
that
we've
been
discussing
for
a
bit
now
and
a
newer
topic
is
improving
the
developer
documentation
so
that
we
can
remove
the
work
and
progress.
Flags.
There's
a
handful
of
those
pages.
I've
actually
created
a
list
of
them
and
we'll
go
over
that
anything
else.
A
To
add
to
the
agenda
here
or
is
that
looking
good
for
everyone?
So
far,
nothing.
A
Cool
first
things:
first
again,
so
we
just
published
our
April
newsletter
yesterday.
This
is
live.
It
has
everything
that
we've
accomplished
over
the
month
of
April,
some
really
nice
Insight
and
just
a
big
shout
out
and
thanks
to
digitalocean.
We
mentioned
it
a
couple
times
throughout
the
newsletter,
but
they
did
provide
us
with
an
additional
credit
to
help
us
get
through
some
higher
usage
times.
So
we're
very,
very
thankful
for
that.
A
There
are
other
notes,
and
there
is
a
brief
recap
of
what
Jenkins
at
cdcon
since
it
just
finished
up.
We
will
have
more
information
about
this
later
on
and
Alyssa
Tong,
who
contributed.
A
The
Outreach
and
advocacy
part
noted
that
the
CDF
YouTube
channel
will
actually
have
recordings
in
about
two
weeks
or
so
so
keep
an
eye
out
for
more
there
and
we'll
actually
have
a
blog
post
to
announce
the
CDF
award
or
the
Jenkins
Awards
winners
that
were
also
presented
at
cdcon,
highlighting
Daniel
back
John,
firechek
and
Mark.
Do
you
remember
who
won
the
security
award
off
top
of
your
head?
I
forget
or.
B
A
That's
right,
it
was
you,
you
won
so
yeah,
so
a
lot
lots
of
great
times
and
there
will
be
more
insights
and
everything
from
cdcon
get
opscom
in
the
coming
weeks
from
various
Outlets.
A
A
We
did
some
backtracking
and
testing
and
found
where
the
issue
looks
to
have
been
created.
Marx
created
a
temporary
fix
so
right
now,
if
you
were
to
go,
if
we
go
to
the
steps
reference
guide,
it
does
display
properly
now
so
it
has
been
fixed
in
the
meantime,
there
still
needs
to
be
some
testing
done
and
some
understanding
of
what
might
have
happened
there,
but
this
nested
choice
of
objects
list
was
not
showing
up
whatsoever
again.
A
The
temporary
fix
has
solved
that,
for
the
time
being,
the
nested
objects
are
all
being
listed
throughout
the
guide,
so
we're
good
with
that
for
the
time
being.
But
again,
there
is
an
issue
in
GitHub
for
this
there's
more
testing
and
work
that
can
be
done.
Then
you
can
follow
the
additional
information
and
work
there.
Yeah.
B
So
really
pleased
actually
to
share
that
that
vihan
Thora
the
author
of
the
pipeline
steps,
John
doc
generator
most
recent
changes.
So
vihan
was
a
Google
summer
of
code
contributor
last
year
in
2022,
and
that
project
was
what
created
that
nice
work
on
that
that
much
better
checkout
page
vihan
did
an
investigation
himself
and
was
able
to
duplicate
the
problem
on
his
own
development
environment.
B
His
workload
right
now
is
heavy
and
so
he's
not
able
to
do
much
more
than
that,
but
I've
left
it
open
that
there
is
a
an
automated
test
now
that
will
reject
or
block
any
pull
request.
That
would
cause
the
the
bug
to
reappear,
to
bug
the
bug
to
again
become
visible.
So
the
automated
test
is
is
flawed
and
imperfect
and
sort
of
horrible
in
that
it
checks
to
see
if
a
particular
file
is
at
least
75
kilobytes
long.
But
that's
good
enough.
It
detects
the
problem.
B
Yeah
and
I
don't
know
that
vihan
will
ever
be
able
to
submit
a
full
fix.
What
vihan
said
was
hey
I'm,
I'm,
heavily
loaded
at
work
right
now
and
I
I
replied
we'll
leave
the
issue
open
and
if
he
or
I
or
someone
else
is
able
to
work
on
it
great
for
right
now
we
have
the
benefit
that
the
documentation
won't
be
broken.
The
negative
is
it
means
that
we're
we're
stuck
one
version
of
parent
Palm
behind
the
current
parent
Palm
version
for
the
for
Jenkins
core
and
that's
okay.
B
Yeah
one
version
behind
yep
exactly
and
what
it
probably
needs
is
someone
who's
willing
to
go
in
and
investigate
fairly
deep
details
about.
Why
is
this
thing
failing
in
this
way?
Now
it's
not
not
at
all
clear
to
me.
What's
going
on
that's
causing
the
failure,
but
I
did
a
very
high
level
investigation
right.
My
investigation
was
find
the
change
that
causes
the
problem
and
write
a
test.
That
will
tell
me
if
the
problem
is
visible
or
not.
A
Great,
thank
you
very
much.
Mark
I
appreciate
the
additional
insight
and
information
on
this
and
yeah
and
thanks
to
vihan
for
first
of
all
creating
the
steps
docs
in
the
first
place
that
is
incredible
and
night
and
day
difference
from
before,
but
yeah.
This
is
something
that
we
can
definitely
step
in
and
help
out
with
and
investigate.
If
we
can
so
great
next
up,
the
Google
summer
of
code
has
officially
announced
its
accepted
projects
and
contributors.
A
So
we
did
have
a
blog
post
to
announce
this
and
share
this
that
was
published
just
last
week,
but
just
really
thankful
for
all
of
the
participants.
Candidates,
applicants.
The
work
that
has
been
done
already
is
outstanding.
A
We
had
a
record
like
a
way
higher
than
average
number
of
proposal,
submissions
in
and
of
itself
giving
all
of
the
lead,
mentors
and
org
admins
a
lot
more
work
to
do,
but
they
got
it
done
huge
thanks
to
Alyssa
John,
Mark,
Bruno
and
Chris
Stern
for
taking
care
of
this
and
leading
us
on
this.
It's
been
fantastic
and
we
couldn't
do
any
of
it
without
you,
so
yeah,
just
congrats
to
all
the
selected
participants
and
contributors.
A
We're
really
excited
about
what's
to
come
and
we
hope
you
get
as
much
out
of
the
Google
summer
of
code
as
you
possibly
can.
A
The
four
projects
that
were
accepted
are
the
alternative:
build
tools
for
jenkins.io
the
git
lab
plugin,
modernization,
jocker
for
quick
start
and
the
plug-in
Health
scores
probe
projects,
so
just
continuing
the
work
that
we've
been
getting
done
and
looking
to
move
jenkins.io
and
Jenkins
in
general
to
the
next
level,
so
I'm
really
really
excited
yeah.
All
the
projects
are
medium
complexity,
so
shouldn't
be
anything
that
we
can't
finish,
or
at
least
get
to
a
really
good
point
with
by
the
time
September.
The
end
of
September
rolls
around.
A
A
Options
for
users
to
respond.
There
are
pros
and
cons
to
this
there's
you
know
things
that
could
be
improved
for
sure,
but
at
this
point
in
time
it's
tough
to
say
what
would
be
a
better
option.
This
does
provide
some
insight
that
is
useful
and
at
the
very
least,
even
if
it's
not
the
most
intuitive
thing
for
a
user
to
use
or
if
there
isn't
a
way
to
prevent
things
like
jenkins-1
from
coming
through.
A
There
is
still
some
value
there.
It
would
obviously
make
life
a
lot
easier
if
we
could
go
and
track
these
submissions
back
to
the
original,
Creator
or
submitter,
so
that
we
could
talk
with
them
and
discuss
further
what
kind
of
issues
they're
facing
and
what
kind
of
troubleshooting
could
be
performed,
but
removing
entirely
is
a
little
drastic
in
the
sense
of,
for
me
at
least
we're
allowing
transparency,
we're
at
least
giving
that
that
kind
of
litmus
test
sort
of
overview
to
to
remain
so.
People
can
just
make
a
decision
based
on
okay.
A
A
So
even
if
it's
just
a
cursory
piece
of
information,
it's
still
something
to
go
off
of
yeah
Mark
Bruno
did
you
have
I
know
that
Mark
you've
commented
and
suggested
in
the
issue,
but
any
other
thoughts
or
suggestions.
I.
B
C
You
don't
have
feel
ashamed.
Of
course.
I
would
have
done
the
same
thing.
You
know
sharing
a
nice
dinner
with
a
nice
person.
Of
course
no
I
was
wondering
there
is
no
incentive
to
report.
Everything
goes
well.
So
why
do
people
click
onto
Sun,
icon,
I
I
feel
I
feel
grateful
for
that
because,
most
of
the
time
people
just
say
when
everything
is
going
wrong,
not
when
it's
going
right,
so
it
works.
B
So
this
the
version,
the
page
that
that
Kevin
shows
when
I
look
at
the
distribution
of
versions,
adopting
the
get
plug-in
so
one
example
right
I
see
that
there
are
from
80
000
to
up
to
a
hundred
thousand
that
regularly
adopt
the
most
recent
release
and
yet
with
80
000
controllers,
70,
positive
votes
or
a
hundred
and
forty
or
a
hundred
and
ninety,
obviously,
there's
not
much
incentive
for
people
to
report
their
results
and
we're
okay
with
that
right.
It's
it's!
It
does
no
harm
for
them.
B
C
Okay
and
Kevin,
you
ask
for
thoughts,
so
let
me
give
you
some
things:
I'm,
not
really
proud
of
it,
but
I'm,
not
so
good
at
math.
So
what
if
we
had
some
percentage
written?
You
know
because
I
know
three
is
nothing
compared
to
69,
for
example,
but
just
as
persons
it
could
help
me
understanding
what's
going
on
and
could
we
have
some
kind
of
Graphics?
You
know
showing
the
progression
along
the
time
of
the
number
of
yes,
it's
doing,
okay,
no,
it's
not
doing
it
doesn't
make
sense.
C
B
But
but
I
think
I
think
you've
got
an
at
least
to
me.
It
sounds
like
an
interesting
concept
when
you
think
about
what.
How
might
we
graph
that
data
and
we
can
graph
the
data
right?
We
could
have
a
separate
indicator
which
says
how
many
people
gave
a
rating,
how
many,
how
many
times
people
is
the
wrong
wrong
number.
How
many
times
was
the
ratings
icon?
B
A
And
I
I
something
I
thought
of
Mark.
When
you
mentioned
that
you
notice
it's
like
a
four
week
span
of
adoption,
it
would
be
interesting
to
see
what
those
numbers
are
like
right
when
the
new
LTS
drops
and
like
it's
gradually
like
graphing
it
like
Bruno,
saying
and
seeing
you
know.
First
week,
There's
x,
amount
of
clicks,
but
the
second
week
There's
this
many
more
clicks
and
then
the
third
week.
It
maybe
drops
down
a
bit,
but
then
the
fourth
week
everyone's
to
a
point
where
they're
like
okay,
this
is
fine.
A
Next
LTS
is
coming
out,
I
can
upgrade
so
it
would
be.
It
would
be
interesting
to
see
like
the
trend
of
when
most
people
are
actually
like
clicking
on
that
or
something.
A
Great
okay,
okay,
perfect!
Thank
you
very
much
Mark
and
thank
you
Bruno
for
sharing
your
thoughts.
I,
like
I
like
really
enjoy
the
idea
of
having
a
graph
to
at
least
share
some
more
insight
into.
What's
going
on
next
up
on
the
agenda,
so
we've
been
discussing
and
talking
about
the
documentation
transition
from
java
11
to
Java
17..
This
was
originally
spurred
by
the
upcoming
release
of
Debian
12,
which
will
not
ship
with
jdk
11..
A
So
we
decided
that
the
Jenkins
documentation
for
installation
for
Java
requirements,
stuff
like
that,
will
transition
it
to
using
Java
17
as
the
preferred
option
so
that
we
can
get
that
transition
happening
now
and
encourage
people
to
use
the
top
of
the
line.
17
provides
better
testing
faster
testing,
more
Edge
testing
just
develop
development
environment
overall
is
better,
so
there's
no
reason
not
to
use
shot
of
17.
A
We
want
to
do
so
so
yeah,
there's
a
GitHub
issue
for
this
that
I've
created
that
goes
through
and
explains
this
a
bit
further.
It
also
highlights
some
pages
where
this
information
would
need
to
be
updated.
I
started
working
on
this
myself
and
I
have
gotten
to
a
couple
places
where
I'm.
Okay
with
the
information
I,
have
run
into
a
couple
struggles
of
just
trying
to
make
sure
that
I'm
getting
the
steps
exactly
correct
and
make
sure
that
I
can
go
down
to
the
root
level,
but
it's
still
being
worked
on.
A
A
Plugins
do
not
need
to
require
Java
17,
but
we
are
saying
that
plug-in
should
test
with
both
the
tutorial
does
guide
them
to
test
with
both
describe
tests
with
both
Java
17
and
Java
11..
So
the
plugins
and
other
documentation
should
reflect
that
there
is
no
open
pull
request
yet,
for
this,
I
have
been
working
on
things
locally
and
will
be
submitting
a
pull
request.
A
A
There's
also
a
section
in
the
current
upgrading
Java
guidelines
that
discusses
the
Oracle
jdk
11
licensing
and
how
it's
not
available
to
be
listed
at
this
time.
The
the
Oracle
jdk
17
may
not
fall
under
the
same
limitation,
so
I'm
doing
a
little
bit
of
Investigation
to
find
out
whether
or
not
that's
an
open,
a
more
open
policy
and
it
can
be
used,
if
not
we'll
make
sure
that's
clear
as
well.
A
A
So
the
end
of
life
notifications
in
Jenkins
course
something
that
again,
we've
been
discussing
Mark's
been
able
to
talk
with
some
other
contributors
and
such
as
Chris
Stern
as
Alex
brandes,
to
get
some
feedback
and
suggestions
on
how
those
could
be
handled
and
where
Mark
has
submitted
a
pull
request.
A
draft
pull
request
to
add
the
monitors.
However,
there
were
some
suggestions
and
feedback
saying
that
it
might
be
a
little
much
or
if
something
can
be
done
to
make
things
easier
for
the
process
involved,
so
it
just
needs
some.
A
B
Yeah
we
once
that's
merged,
we
will
have
and-
and
it
I've
got
a
I've
got
a
major
rework
to
do
on
that
pull
request.
It's
it.
It
was
a
good
first
experiment
and
it's
good
to
throw
the
first
experiment
away.
So
I
got
some
good
feedback
and
the
feedback
will
make
the
the
final
implementation
much
better.
A
Great
good
to
know,
thank
you
very
much
Mark
and,
as
noted
not
available,
not
an
option
just
yet,
but
when
it
comes,
it
will
be
very
made
aware.
A
The
early
end
of
Centos
7
for
the
Jenkins
project
has
been
being
just
has
been
discussed
at
length
for
some
time
and
I.
Think
we're
at
the
point
where
now
Marco
Jep
is
just
going
to
be
submitted
for
that
and
we'll
be
going
from
there.
B
With
it,
or
is
there
yeah
I
think
I
may?
Even
so,
it's
been
awfully
quiet
and
my
request
to
the
Jenkins
developers
list
I
submitted
a
message
to
the
Jenkins
developers
list,
saying
I'm,
proposing
this
and
and
no
no
responses
that
were
negative
to
it.
Puzzle
Crow
observed,
hey,
we've
already
dropped,
support
and
other
projects
have
already
dropped
support
in
various
subsections.
For
instance,
the
docker
contain
the
container
image
on
which
we
base
our
agent
images,
our
Centos
7
agent
images
and
our
Centos
7
controller
image
has
been
unmaintained
since
2020..
B
A
Great
yeah,
you
know,
I
did
seeing
Basil's
message
about
where
other
projects
have
dropped
that
support
as
well
so
yeah
I.
Think
it's
good
that
we
have
the
actual
experiences
and
anecdotal
evidence
to
say:
hey
we're,
not
the
only
ones.
This
is
pretty.
You
know
Common,
so
yeah
great
and
then
the
last
topic
I
had
on
the
agenda
is
improving
the
developer
documentation
so
that
we
can
remove
the
work
in
progress
Flags.
A
So
this
is
definitely
something
that
can
be
handled
by
various
people.
This
isn't
a
one-person
job
by
any
means.
What
I've
done
to
help
is
create
a
list
of
the
work
in
progress
pages,
so
I've
got
the
directory
and
then
the
pages
and
what
I
think
their
prioritization
should
be.
The
stars
are
just
one
through
five,
five
being
the
most
urgent
one
being
not,
but
things
like
managing
users
managing
tools,
obviously
securing
Jenkins.
A
A
It's
definitely
not
a
good
first
issue,
type
of
thing,
so
for
the
developer
architecture,
there
are
a
few
pages
where
there's
just
nothing
available
on
the
page,
so
it
does
need
content
or
we
need
to
figure
out
whether
or
not
that's
going
to
be
a
valuable
section
to
include
I
think
there
is
yeah
these
two
system
administration
pages,
that
I
found
with
chef
and
with
puppet
there
is
no
content.
I
haven't
honestly
heard
anything
about
either
of
these
in
some
time.
A
So
I
don't
know,
for
instance,
how
relevant
those
would
be
if
it's
worth
keeping
those
pages.
If
we
should
look
at
other
options,
maybe
there's
a
different
tool
to
do
the
administration
with
so
yeah.
There's
just
some
ideas
again
and
I've
put
some
notes
on
things
that
they,
where
they
do,
have
some
content
and
might
just
need
further
information
or
expertise.
A
So
yeah,
just
there's
a
good
amount
of
stuff,
but
I
noticed
that
there's
also
probably
40
of
the
pages
do
have
content
and
it's
more
a
it
seems
like
it's
not
finished,
then
there's
nothing.
There.
A
And
then
one
of
the
other
a
couple
of
other
things
that
I
noticed
so
with
the
recent
update
for
the
XML
values,
not
reading,
no
backward
compatibility,
I
think,
might
need
to
be
updated
for
that
I'm,
not
100
sure,
but
that
when
I
was
reading,
it
seemed
to
come
up
a
develop.
The
developer
navigation
itself
is
unordered
in
any
seeming
way.
So
I
submitted
a
pull
request
earlier
today,
just
to
reorder
them
in
alphabetical
order.
A
I'm
not
saying
this
has
to
be
the
way,
but
going
from
this
to
this
just
feels
a
little
bit
cleaner
and
nicer
to
read.
I
would
also
be
open
to
putting
these
in
in
order.
That
makes
sense,
workflow
eyes
for
the
developer
like
if
we
want
to
start
with,
you
know,
initialization
or
just
building
and
debugging
something
very
straightforward,
and
then
you
know
releasing
plugins
and
stuff
can
go
or
publishing.
Plugins
could
go
down
here
if
there
is
a
workflow
order.
A
I
just
figured
that
we
could.
This
would
be
a
quick,
low
hanging
fruit,
something
easy
that
we
could
just
make
the
navigation
and
topics
a
little
easier
to
navigate
so.
A
A
So
then
that
covers
everything
I
had
for
the
agenda
today,
if
that's
taken
care
of,
so
the
recording
will
be
available
in
24
to
48
hours
and
yeah.
We'll
see
you
next
week.
Thank
you
very
much
for
coming,
appreciate
it
and
take
care.