►
From YouTube: 2023 05 04 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
One
welcome
to
the
Jenkins
documentation
office
hours
today
is
May
4th
2023,
and
this
is
the
EU
US
edition.
Today
we
have
myself
Mark,
White
and
I.
Think
Bruno
Brockton
will
be
joining
us.
He
was
here
briefly,
but
we'll
most
likely
be
reconnecting
the
agendas
fairly
short
today.
Right
now,
the
agenda
includes
there's
an
issue
at
the
moment
where
the
pipeline
steps
references
has
some
areas
where
the
nested
options
and
information
is
not
present.
Mark
and
I
have
been
reviewing
this
and
investigating.
A
All
morning
we
were
just
talking
about
this.
We
seem
to
have
gotten
down
a
time
frame
from
when
this
happened.
What
exactly
caused
it?
We
don't
know
yet
we're
still
trying
to
figure
that
out,
but
there
could
have
been
in
one
of
several
different
places,
which
is
the
biggest
thing,
so
it
could
have
been
the
pipeline
step.
Stock
generator
could
be,
it
doesn't
appear
to
be
the
jenkins.io
site.
A
Mark
has
been
able
to
figure
out
that
has
a
working
and
non-working
repository,
so
he
does
have
a
control
to
test
out
with,
but
we're
still
looking
into
this
and
figuring
this
out.
This
is
yeah,
not
ideal.
A
Of
course,
but
yeah
we'll
go
into
that
more
Google
summer
of
code,
so
the
only
update
here
is
that
they
will
be
sharing
their
announcement
for
accepted
projects
today
at
18
UTC,
so
keep
an
eye
out
for
that
really
really
excited
and
yeah
just
keep
an
eye
out
for
that
and
then
further
communication
from
the
Jenkins
project
as
well.
A
I
wanted
to
highlight
that
we
just
published
Bruno's
latest
blog
post
in
his
series
on
Android
development
with
Jenkins,
so
really
exciting
stuff.
It's
really
wonderful
and
I,
just
love
being
able
to
read
the
different
ways
that
this
has
been,
that
Jenkins
have
been
utilized
and
seeing
how
mobile
app
development
can
go
through
it.
It's
really
cool
so
definitely
be
sure
to
check
that
out
and
one
of
the
other
blog
posts
I
wanted
to
highlight
that
I
don't
have
on
the
list
here,
but
cdcon
is
next
week.
A
A
Something
a
couple
other
things
so
recently
I
had
a
book
submission
guidelines.
This
is
something
that
I
just
figured
we
could
put
in
and
have
outlined
there.
We've
gotten
more
book
submissions
lately.
So
having
some
guidelines
is
just
some
structure
that
we
could
use
the
LA
the
most
recent
LTS,
which
was
yesterday
of
2.387.3
released
successfully.
A
There
are
a
couple
of
interesting
things,
but
we've
noted
them
in
the
2.403
change
log,
so
XML
handling
of
null
values
is
something
that's
going
to
change,
and
so
just
be
aware
of
that
again
we
have
documentation
all
sorts
of
stuff
around
these
and
jira
tickets
or
not
zero
tickets.
Sorry
gith
GitHub
tickets.
That
provide
more
context
as
well.
So
there's
lots
of
information
for
that.
A
The
next
LTS
Baseline
right
now
is
currently
voted
as
2.401.
That's
scheduled
for
a
May
31st
release.
So
keep
an
eye
out
for
that
more
to
come
on
that
and
right
now,
I'm
working
on
a
working
on
the
Jenkins
documentation
to
transition,
installation
guidelines,
Java
requirements,
system
requirements
from
java,
11
to
Java
17
as
the
preferred
method
we're
still
supporting
job
11.
We
just
want
to
show
people
that
Java
17
is
the
way
to
go
and
that
it
is
the
future,
so
faster
testing,
Edge
testing
functionality,
development.
A
Everything
is
just
better
in
Java
17,
so
we
want
to
encourage
people
to
hop
on
that
yeah,
so
Mark,
so
I
did
want
to
spend
more
time
on
the
pipeline
steps
reference
since
that
is
relevant
to
what's
going
on
today.
A
So
what
would
be
the
next
steps
that
we
could
look
at
for
this
or
I
was
when
I
was
trying
to
do
some
testing
and
figuring
it
out?
Backtracking
I
wasn't
sure
how
I
could
potentially
test
some
of
the
pull
requests
on
other
areas
like
the
docs
step,
generator.
B
Yeah
it
will
and
I
so
okay.
So,
let's,
let's
describe
first
what
I
think
we
know,
and
maybe
maybe
by
writing
those
I'm
gonna
I'm
gonna,
try
to
type
some
some
ideas
here
in
terms
of
things
that
I
think
we
know
right.
So
what
we
know
right
is
the
current
site
shows
no
entries
for
the
checkout
step
or
or
know
what
would
you
call
it?
No
nested
entries
for
the
checkout
step
all
right
and
that's
that's
our
test
case,
so
maybe
Kevin.
B
A
B
So
pipeline
steps,
reference
search
for
the
word
checkout
yeah
and
then
that
very
bottom,
one
notice
that
here
nested
choice
of
objects,
right
is,
is
very
brief,
whereas
in
the
actual
production
site
or
in
the
in
the
the
working
site
and
and
now
let's
bring
up,
let's
bring
up
one
that
was
working.
Let's
see,
we
had
notes
on
one
that
was
working
right.
It
was
yep.
B
A
The
screen
so
I
can
share
it:
okay,
so
so
yeah.
So
this
is
the
deploy
from
6323.
B
So
we've
got
this
is
this
is
looks
good
and
then
the
other
one
was
the
looks
bad
now.
What
we
see,
what
what
I
see
in
my
development
environment
is
I've
got
a
a
working
repository
and
a
bad
repository,
the
working
repository
and
and
the
thing
that
generates
this
page.
The
thing
that
generates
the
content
in
this
page
is
this
file
all
ascii.zip
Maybe.
B
Maybe
what
we
ought
to
try
is
well
here's
an
idea
Okay,
so
we've
got
on
my
system.
I've
got
two
conditions,
one,
that's
good
and
one
that's
bad,
and
one
theory
is
that
the
whole
problem
is
in
this
data
file
called
all
ascii.zip
that
is
generated
by
the
pipeline
steps.
Doc
generator
right
now
that
data
file
is
the
current
data
file.
Size
is
about
290k
in
the
broken
State.
That's
good!
Let's
make
a
note
of
that.
B
Okay,
so
marks
working
site
working
good
working
copy
has
a
has,
has
the
master
Branch
checked
out,
so
the
current
the
current
tip
of
the
master
branch,
but
with
an
older,
all
ascii.zipped?
B
B
Now
now
the
problem
is
I.
Don't
I'm
not
expert
enough
on
all
of
the
detailed
steps
here,
so
it
may
be
that
moving
those
files
around
won't
actually
change
anything
because
I
don't
know
if
all
ascii.zip
is
actually
used
during
site
generation
or
if
it's
unpacked
once,
let's
see
how
would
I
guess
that.
A
Mark
as
a
side
note,
do
you
know
if
it's
do
you
know
if
it's
possible
to
extract
like
the
date
or
date
and
time
for
the
the
older,
all
ASCII
zip
for.
A
We
were
looking
at
the
two
pull
requests
where
it
was
good
to
bad
I.
Think
the
time
frame
was
very
early
on
the
20
on
the
25th
and
then
very
late
on
the
25th.
So
if
the
older,
all
ASCII
is
from
around
that
time
frame,
that
might
point
us
in
that
direction.
B
Yeah
well
so
that's
that's
a
good
thing
to
check,
because
I've
got
that
I've
got
both
files,
and
so
let's
look
at
so
Kevin
I'm
going
to
share
my
screen
and
we
can
stare
at
the
contents
of
the
zip
file
together.
Okay,
all
right!
So
looking
at
my
screen
here,
so
here's
what
I've
got
I've
got.
Oh
that's
not
useful!
Oh
here
nope
where'd
it
go
where's,
my
terminal
there
it
is
okay.
So
this
has
content
underscore
temp
I'll,
ask
you
dot!
Zip
is
the
actually,
let's
just
look
at
them,
so
the.
A
B
B
Here
it's
or
oops
89,
so
they
are
exactly
the
same
size
in
in
the
two
places:
the
one
that
oops
reading
again:
okay,
the
one
that
provides
workflow
the
workflow
step.
What
is
that
one
that
is
help
me
out
there?
Kevin
I
you've
got
it
on
your
on
your
screen
in
the
URL
it's
pipeline.
If
I
look
at
the
steps
reference,
if
I
search
for
checkout
check
out
here
it
is
it's
the
pipeline
s,
so
workflow
SCM
step.
So,
let's
see,
if
there's
a
difference
between
those
two
workflow.
B
B
So,
okay,
so
obviously
there's
a
difference
between
good
and
bad.
So
really
it
is.
It's
got
to
be
in
the
pipeline
step,
stock
generator.
Okay,
that's
good!
This
means
we
don't
have
to
spend
time
in
this
meeting.
I
can
go
separately
and
do
diagnosis
on
Pipeline
step
stock,
generator
that
that
already
thanks
for
the
insights,
because
that
already
has
shown
this
is
so
if
I,
for
instance,
if
we
look
inside
this
file.
A
B
A
A
B
That's
that's
a
very
testable
condition
now
I
can
I
can
go.
Do
the
do
the
bisect
to
find
where
all
ascii.zips,
workflow
SCM
step
file
is
too
small
because
that's
that's
what's
happened
right,
it's
it's
that
in
fact,
I
should
be
able
to
even
see
it
here.
I've
got
two
directories:
oh
no
I,
don't
apparently
so,
but
it's
that's
a
that's
a
doable
bisect.
So
what
we
need
is
workflow
SCM
step
should
be
90
kilobytes,
not
two
kilobytes.
A
And
Mark
that
the
pipeline
sem
adoc
would
not
be
coming
from
the
plug-in
in
this
case,
then.
B
Actually
you
you
good
point:
it
is
coming
from
the
plug-in,
but
for
some
reason,
the
tool
that
extracts
it
from
the
plugin
is
no
longer
doing
the
extraction.
Okay.
So
it's
it's
that
something
changed
in
the
pipeline:
steps,
doc
generator
source
code.
So
so
the
process
that
happens
is
the
pipeline
step
stock,
generator
downloads,
all
plugins
extracts
them
all
and
then
pulls
out
their
help,
files
and
formats
them
into
ASCII
doc
and
somehow,
in
that
process
of
extracting
and
formatting
to
ASCII
doc.
B
This
thing
is
being
lost
and
that
that
loss
has
happened
in
a
fairly
recent
change
and
I
I
say
fairly
recent
because
I
we
we,
we
saw
the
yeses
and
the
no's
in
our
in
our
earlier
analysis
and
there's
some
Oddity
there.
But
we
got
some
rough
timelines
that
we
can
use
to
check
to
see
where,
where
did
the,
which
change
or
changes
to
the
pipeline
step
stock
generated,
caused
it
to
stop
generating
correctly
and
and
then
we
write
some
tests
to
be
sure
that
this
problem
never
happens
again.
A
B
A
Of
course
Bruno,
so
since
I
know
you're
having
some
audio
issues,
is
there
anything
that
you
wanted
to
share,
bring
up
put
on
the
agenda
talk
about
today?
A
No
thanks
for
asking
Kevin,
okay,
yeah
no
worries
just
want
to
make
sure
I
did
also
highlight
your
newest
Jenkins
and
Android
blog
post,
since
we
just
got
that
published
the
other
day,
yeah
thanks
for
your
help
and
yeah,
always
of
course,
and
then
yeah
we're
just
talking
we're
just
sharing
that
the
Google
summer
code
announcement
will
be
later.
So
thanks
to
you,
Alyssa
Jamar
Kristen
for
all
your
work
being
org
admins
on
that
and
spearheading
all
this
everyone's
very
excited
and
can't
wait
for
it
so
yeah.
A
Thank
you,
okay,
so
that
I
had
for
the
agenda
today.
If
that
covers
everything
for
everyone,
we
can
go
ahead
and
call
it
early
today,
no
problem
at
all
and
yeah
thanks,
as
always
for
joining
again
appreciate
all
the
work
and
contributions
and
assistance
and
everything
so
take
care.
Have
a
great
rest
of
your
day.
See
you
later
the
recording
will
be
available
in
about
24
to
48
hours.