►
From YouTube: 2022 08 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
Two
one
welcome
to
the
european
docs
office
hours
for
jenkins.
This
is
the
august
4th
edition
and
we
have
quite
a
few
items
on
our
agenda
for
today.
First
we'll
have
some
action
items
that
mark
will
just
give
us
a
brief
update
on
we'll
have
a
discussion
about
the
there's,
been
some
updates
to
the
page,
look
and
feel
for
jenkins,
we'll
discuss
that
in
some
of
the
other
discussions
that
have
come
up
since
it
being
merged.
A
A
We've
got
an
item
for
discussing
the
search
improvements
for
jenkins.io,
the
next
baseline
selection,
the
commercial
support
page
that
gavin's
proposed
and
we've
started
talking
about
previously.
A
The
fact
that
change
log
entries
can
come
from
multiple
repositories.
We
have
the
jenkins
2.346.3
changelog
and
upgrade
guide
with
the
release
coming
out
on
august
10th
tentably.
So
that's
in
progress
and
then
just
some
tooling
updates
for
java
11,
as
that
will
be
the
requirement
with
the
september
lts
and
is
the
weekly
requirement
now.
A
Okay,
then
mark
if
you
want
to
start
us
off
and
if
you
have
any
any
info
for
the
action
items
there.
B
Yeah,
so
I'd
still
have
to
hang
my
head
in
shame.
No
progress
on
any
of
the
action
items,
although
I
take
it
back.
I
have
started
writing
the
blog
post
on
she
caught
africa
contributon
and
it
will
probably
be
done
today
and
submit
it.
So
so
I
I
guess
I
have
started
some
action.
It's
just
no,
nothing
visible
yet
so
keep
your
eyes
open
for
pull.
Requests
to
review
later
today,.
A
Sounds
good,
thank
you
very
much
great,
so
then,
to
start
us
off
jihan.
Would
you
like
to
share
what
you've
been
up
to
on
a
google
summer
code.
C
Yes
sure
so,
last
week
the
pull
request
for
the
degraded
level
was
label
was
merged,
so
that
was
the
first
task
after
the
midterm
evaluation,
and
now
the
big
task
is
to
reduce
the
content
of
the
pipeline
steps
documentation.
C
So
we
I
have
been
looking
into
some
approaches
for
that
and
I
put
a
ticket
on
the
group
on
the
chat
channel
and
that
I've
mentioned
some
of
the
things
that
I've
tried
and
I've
noticed
that
making
changes
in
the
two
ascii
top
the
ascii
generation
java
class
is
actually
much
harder
than
making
changes
to
the
ascii
docs
that
we
have
that
are
generated
from
the
class.
C
So
I
am
looking
at
making
something
like
a
post-processing
system
rather
than
a
pre-processing
system,
because
those
functions
are
recursively
calling
each
other
and
getting
the
depth
of
the
initial
choice
of
objects
becomes
quite
hard
to
track.
So
and
basically,
I'm
visualizing
these
documentation
like
a
tree
and
so
each
parameter
would
represent
the
root
node
and
inside.
We
have
the
nested
choice,
which
would
be
the
following
nodes
and
the
very
end.
C
The
last
parameters
would
be
like
the
leaves,
and
we
just
want
to
find
the
depth
of
these
so
that
we
can
maybe
separate
out
the
deeper
parts
of
the
tree
onto
a
newer
page,
but
that
was
becoming
quite
hard
to
track
since,
as
I
said,
the
two
functions
were
calling
each
other
recursively
and
the
depth
was
it
was
I
tried
some
algorithm,
but
the
depth
was
coming
out
to
be
wrong.
C
So
then
I
thought
that
it
would
be
easier
to
work
on
strings
rather
than
working
on
iterating
java
objects,
because
if
we
have
a
ascii
dock,
we'll
just
do
a
file
reader
on
that,
and
once
we
have
the
string
array
of
the
lines
we
can
maybe
read
for
the
tags.
So,
for
example,
we
see
an
entire
tag,
is
between
some
li
tags
and
even
in
between
them.
If
we
have
li
tax,
we
know
that
the
root
will
be
closed
if
we
are
able
to
find
the
equal
number
of
closing
tags
as
well.
C
A
Yeah
go
ahead,
john.
I
just
stopped
sharing
my
screen,
so
you
can
take
over.
C
Yes,
it
is
okay
great,
so
I
basically
wrote
a
processing
class
for
the
process,
ascii
doc,
it's
not
doing
much
right
now.
It's
maybe
just
for
some
research
things.
I've
added
some
code
to
see
so,
as
you
can
see,
I'm
measuring
these
number
of
lines
that
are
encapsulated
within
one
single
lecture:
choice
of
objects
for
different
ascii
docs,
and
these
are
all
the
ascii
docks
that
are
on
the
documentation
page.
So
I
downloaded
one
of
the
all
ascii.zip
file
and
unzipped
over
here.
C
So
I'll
show
you
some
interesting
results
that
I
saw
so,
for
example,
the
workflow
multi
branch.
In
that
the
nested
choice
of
objects
is
present,
it
has
146
000
lines
and
similarly,
if
we
scroll
for
different
things-
and
this
is
not
the
worst
thing-
trust
me
so
like
workflow
scm-
is
by
far
the
largest
page
that
we
have
even
the
ticket.
I
mentioned
the
size
in
mds.
C
It
was
around
four
and
a
half
mps,
which
is
quite
a
lot
for
an
ascii
auction
and
once
we
run
the
javascript
on
that
page,
the
page
basically
hangs.
So
for
me,
whenever
I
try
to
click
on
that
page,
it
at
least
takes
around
two
minutes
for
that
page
load,
so
yeah
this
is
it,
and
the
next
thing
that
I
found
very
surprising
was
the
amount
of
redundancies
that
were
present
in
the
ascii
dock.
C
So
I
have
one
example
for
you
right
now,
so
the
git
scm
parameter,
the
choice
is
actually
present
at
10
different
places
in
the
documentation.
So,
for
example,
we
have
two
occurrences
of
the
exact
same
block
of
grid
scm.
This
might
contain
thousands
of
lines.
So
basically
I
am
talking
about
the
just
for
reference.
I'll
show
you
what
it
looks
on
the
front-end
side
so
that
we
know
how
much
content
is
getting
repeated.
The
documentation.
C
This
new
number
looks
great
by
the
way.
The
only
problem
for
me
on
my
machine
is
a
lot
of
content
is
getting
clipped
from
the
top,
so
I
have
to
like
zoom
out
to
see
the
upper
part,
my
I'm
using
a
14-inch
laptop.
So
maybe
we
can
rectify
that
in
the
future
updates
yeah.
So
basically,
all
content
within
this
data
same
so
this
has
many
more
nestings
within
itself.
C
So,
as
you
can
see
all
of
these,
so
this
it
will
be
fair
to
assume
it
would
have
around
a
thousand
lines
of
ascii
dock
within
itself,
and
this
is
getting
repeated.
The
exact
same
content
is
repeated
twice
in
jail.edo
and
four
times
in
pipeline
guru,
v,
dot
the
exact
same
content.
As
you
can
see,
it's
not
changing.
Nothing
is
changing,
so
this
has.
C
This
is
basically
present
at
ten
different
places,
so
my
goal
would
be
to
separate
all
the
scm
providers
and
localize
them
to
a
different
url
altogether,
and
once
that
is
done,
we
all
these
places
would
simply
contain
the
hyperlink
to
that
page
and
instead
of
showing
the
entire
of
continuing
the
entire
documentation
at
every
local
position,
they
will
just
point
on
to
their
new
page,
which,
which
would
be
present
in
the
like
ascii
talks,
which
are
on
the
website.
C
B
So
vihan,
actually
we
may
want
you
to
continue
sharing.
I
I
had
some
questions.
Are
you?
Okay?
If
I
ask
you
some
questions.
C
B
B
C
In
one
of
the
collapsible
lists,
let
me
just
share
my
entire
screen
screen
and
all
right.
We
will
find
it
together.
C
C
B
C
Okay,
so
this
is
interesting.
What
we
can
try
is,
I
can
run
this
locally
and
maybe
disable
the
javascript,
but
there's
no
there's
not
a
lot
of
content
on
this
page.
That
means.
B
B
Yeah,
it's
it's
as
though
it
embedded
okay
so
and
then
maybe
it's,
maybe
it's
just
something
for
you
to
investigate
separately,
because
that
that
embedding
looks
disastrous,
and
yet
I
don't
see
it
on
the
page
and
when
I
look
at
the
size
of
the
web
page
and
its
source,
it's
it
doesn't
look
at
least
to
me
like
it's
like
it's
huge
and
I
would
have
expected
it
based
on
what
you
were
seeing
for
that
page
to
be
absolutely
huge.
A
B
B
C
C
C
Okay,
okay,
so
we're
done
so.
We
have
here
modern
cm
and
in
this
legacy-
and
here
it
is
so-
the
entire
same
thing
is
check
out.
So
we
have
the
name
branch,
branch's,
name,
browser.
Everything
is
the
same.
B
Right,
right
and
and
and
that
I
I
think
I
see
your
point
there
and,
and
that
absolutely
is-
is
expected
based
on
the
current
structure
and
certainly
bloats
the
page
right,
because
what
it
lists
is
every
known,
modern,
scm,
implementation
and
and
therefore,
and
and
it's
right
inside
the
page
content
you're
correct
it's
because
it's
a
static,
page
good.
Thank
you.
Good
good
detection.
C
So
basically,
all
these
are
coming
like
a
bit.
We
have
built
keeper
on
the
checkout,
so
all
these
are
basically
there's
a
lot
of
repetition.
So
what
I
am
proposing
is
for
each
one
of
them.
This
collapsible
section
will
turn
into
a
clickable
link
and
we'll
have
one
single
page
for
git
scm,
one
for
arvis,
and
that
way
I
guess
it
would
be
easy
for
the
user
to
identify
as
well
on
that
page.
We
can
maybe
help
them
in
identifying
which
plugin
that
particular
class
is
coming
from.
C
B
Lying
yes,
yes,
no!
That's
that's
great!
Thank
you.
I
like
that
very
much
so
that
that
covered
that
topic.
Then,
if
we
could
rewind
back
one
topic,
if
you're,
okay,
that
would
be
with
deprecated,
so
you
mentioned
that
deprecated
has
been,
has
been
deployed.
But
could
you
show
us
the
the
page
and
let's
talk
about
how
deprecated
is
presented
to
the
user.
C
Okay,
so
this
was
the
example
that
I
think
was
any
ticket,
scm,
http,
client,
and
so
once
we
go
into
that,
we
are
able
to
see
the
deprecated
label
next
to
the
plugin.
Now.
B
Okay,
okay,
so
the
the
fact
that
that,
for
instance,
the
github
plug,
oh
okay,
I
was
trying
to
understand
why
artifact
z
did
not
have,
but
in
this
case
that's
the
case
of
artifact
z.
It's
not
a
deprecated
plug-in,
it's
a
deprecated
part
of
the
documentation,
that's
in
the
plug-in,
and
so
the
word
deprecated
appear
you're.
What
you're
showing
me
is
in
fact
scm-http
client
is
deprecated,
and
it
correctly
shows
that
it's
a
deprecated
plug-in
there
and
if
I
open
the
plug-in
site,
it
shows
it's
deprecated
as
well.
Good.
I
understand.
C
Sure,
and
like
so,
for
these
steps
that
have
been
what
dedicated
is
not
added
by
me,
it's
by
default,
the
name
it's
coming
with
this
step,.
C
C
So,
for
example,
checkout
is
no
longer
coming
in
the
pipeline
scm
step,
it's
getting
fed
into
core
and,
like
code
core,
is
getting
crowded
by
all
these
things
like
zeus,
also,
it's
not
able
to
find
the
plug-in
name,
and
basically
this
happens
when
there's
a
method
known
as
getting
a
name
for
descriptor
and
once
it
it's
not
able
to
find
a
name,
it
sends
all
of
them
to
core,
and
it's
not
supposed
to
happen
like
this,
because
earlier
we
just
have
had
a
couple
of
steps
in
code
and
others
were
in
their
respective
plugins.
C
So
this
maybe
I'm
not
sure
why
this
has
occurred.
I've
also
noted
this
to
christian
the
office
hours,
and
maybe
we
can
do
a
force
build
on
the
for
this
repository
and,
let's
see
if
the
new
one
is
better
and
if
it's
not,
then
we
can
investigate.
B
C
B
B
B
Thanks
for
thanks
for
showing
this
vihan
you've
once
again
shown
something
very,
very
helpful
that
I
wasn't
aware,
and
I
think
if,
if
it's
not
fixed
magically
by
by
running
it
again
I.e
by
having
had
got
the
bug
fixed
in
three
2.362,
then
we
we
probably
need
you
to
take
some
deep
dive
to
understand.
What's
changed
what
broke
it.
C
B
Could
you
know
what
let
me
just
run
it
and
if
it
fails
I'll,
create
the
ticket
that
way?
That
way,
we
know
we
know
the
result
and
the
result
is
represented
exactly
in
the
in
the
ticket.
If
it,
if
we
didn't
need
it,
you
could
have
issue
for
it.
It'll
just
be
fixed
and
there'd
be
no
value
to
the
the
github
issue.
So
let
me
create
the
issue.
If
I
see
a
problem.
A
Thanks
mahan
really
appreciate
it
and
just
to
reiterate
that
looks
amazing,
really
appreciate
what
you're
doing
and
investigating
and
working
on
with
the
jenkins
project
like
this
is
all
very
amazing
and
helpful,
so
yeah.
Thank
you.
Much
appreciate
it
cool
all
right
so
just
to
touch
base
on
the
look
and
feel
page
improvements,
so
this
was
something
that
was
submitted
recently
within
the
last
month
by
contributor
and
frankly,
the
page.
A
I
think
it
looks
great,
but
there
have
been
some
challenges
as
far
as
the
font
being
updated
goes
and
just
other
small
things,
but
nothing
too
major.
However,
the
the
font
really
needs
to
be
what
it's
already
been
updated
to.
So
while
this
ticket
has
been
merged,
we
do
have
a
revert
ticket
open
as
well,
in
addition
to
the
submitter
contributors
themselves,
also
having
an
updated
issue
where
they've
corrected
the
fonts.
A
So
this
is
something
that's
been
happening
over
the
last
couple
of
days
and
just
wanted
to
bring
it
to
the
community
to
discuss
how.
How
does
the?
How
do
the
improvements?
Look?
How
how
does
the
page
feel
now?
Is
there
anything
else
that
anyone
might
notice
or
pick
up
on
as
they're
reviewing
it
reviewing
it?
You
know
these
are
all
things
that
we
want
to
capture
here.
So.
B
Yeah,
so
my
my
question
here
was
I
I
appreciate
daniel's
comment
visible
on
the
screen.
Now.
Can
we
just
revert
this
already?
I'm
not
really
ready
to
revert
it
because
my
personal
preference
is
keep
it
and
go
forward.
Try
to
resolve
his
concerns,
rather
than
revert
it
and
try
to
do
them
again.
I
feel
like
it's.
It's
a
generally
positive
improvement.
We
had
gavin
mogan's
involvement
and
gavin
has
been
willing
to
adapt
the
pi
the
plug-in
site
to
handle
it
as
well
and,
and
so
I'm
I'm.
I
wanted
to
hear
other
people's
opinions.
B
C
Could
I
see
the
issue
that
was
like
created
and
because
of
which
we
want
to
reward
that?
Maybe
if
that
is
open,
I
don't
have
a
link
to
it.
5
3,
3
4.
Is
it.
A
Which
has
been
this
one
has
been
closed
this
one
specifically,
this
is
the
newest
version
of
daniel's
comments
and
and
pull
requests.
Essentially
here,
oh
okay,.
C
So
it's
five,
as
I
mentioned,
like
the
the
problem
with
me,
was
the
number
overflowing
on
and
keeping
my
content,
and
but
I
think
it
is
fixable
so
and
the
new
look
new
page
looks
nice,
so
I
would
say
we
can
go
ahead
with
this.
A
And
I
have
already
voiced
my
enjoyment
of
the
page
itself.
I,
like
the
background,
the
font,
the
color
updates,
the
blue
is
a
little
bit
warmer
and
a
little
less
abrasive
on
the
eyes.
I
think
it
flows
really
nicely
and,
like
mark
said,
the
gavin's
gone
ahead
and
already
updated
the
plugins
page
to
match.
So
this
work
is
being
done.
A
It's
already
been
done
and
I
think
it
would
be
really
valuable
to
keep
this
and
move
forward
and
update
as
we
go
innovation's
the
name
of
the
game,
and
I
would
love
to
just
see
us,
you
know,
move
forward
and
iterate
on
that.
B
Okay,
so
kevin.
Could
you
help
me
with
one
more
tour
item?
Let's
go
back
to
the
the
the
documentation
or
back
to
the
notes
for
the
meeting.
I
think
there's
a
link
to
the
new
poll
request.
That's
to
to
repair
it
yeah,
so
that
bullet
that
says
new.
Okay,
this
one.
Could
you
look
at
the
preview
here?
I
wanted
to
see
if
the
rest
of
us
see,
okay,
is
the
font,
improved,
etc,
etc.
B
A
A
Let
me
just
make
sure
yeah
I'm
on
the
right
percentage,
zoom
and
everything
for
both
screens
yeah.
Okay.
So
that's
so
it's
moved
a
little
different.
It
looks
and
yeah
your
font's
definitely
a
little
different.
B
B
A
Yes,
and
so
this
is
how
it
currently
looks
on
the
production
site.
This
is.
A
A
Yep
and
and
my
screen
and
just
for
the
for
the
reference,
is
my
screen's,
a
much
larger
monitor
than
what
beyond's
using
so
my
nav
bar,
I
don't
think,
is
going
to
have
the
same
issues
as
far
as
appearing
and
rendering
goes.
But
I
know
that
that
was
something
that
came
up
in
the
conversation
of
the
original
public
west
and
is
part
of
the
original
public
west.
So
there
was
something
there
for
sure.
B
Okay,
all
right,
so
if
it
feels
to
me
like
at
least
as
the
group
of
the
four
of
us
here,
we're
okay
with
pressing
forward
I'll,
probably
have
a
conversation
with
daniel
separately
and
and
see
okay,
it
may
he
may
disagree
strongly
with
it.
A
Thank
you
mark,
okay.
So
next
thing
on
the
list
is
book
update,
so
the
blue
ocean
stat
we've
up
I've
updated
the
blue
ocean,
docs
pages
with
a
blue
ocean
status
message.
This
is
to
properly
set
expectations
for
blue
ocean,
where
it's
at,
where
it's
going
to
be,
and
just
overall
the
product
itself.
It's
been
included
on
every
blue
ocean
document
page
including
the
index
and
is
thanks
to
my
working
with
mark
we've
made
sure
to
place
it
above
fold
so
that
it
doesn't
hide
it
hidden.
A
When
you
go
to
any
of
the
pages
now.
The
nice
thing
is
with
the
status.
It's
also
been
updated
to
include
conditional
statements
so
that,
depending
on
what
page
is
being
viewed,
you'll
get
different
versions
of
the
status
update
in
the
statement.
So
it's
it's
all
based
on
what
functions
of
blue
ocean
are
being
discussed
so
here
in
creating
a
pipeline,
it
talks
about
all
three
pieces
of
it:
blue
ocean
itself,
overall
pipeline
visualization
and
the
pipeline
snippet
generator
syntax
snippet
generator.
A
So,
but
if
we
go
to
something
like
the
dashboard,
we're
not
going
to
get
those
things
pipeline,
visualization
isn't
necessarily
a
part
of
this
same
thing
with
the
activity
view,
but
we'll
go
to
the
pipeline
editor
and
we
see
the
pipeline
syntax
snippet
generator
piece
here
as
well,
so
it's
been
implemented
really
nicely
and
everything's
been
aligned
in
that
sense.
So
hopefully,
this
helps
relieve
a
lot
of
the
concern
with
the
blue
ocean
documentations.
A
These
have
that
has
come
up
and
I'm
still
working
on
the
blue
documentation
overall
to
get
these
pages
more
in
line
with
status
statement.
I've
submitted
a
couple,
but
I
still
have
plenty
of
work
to
do
on
these.
So
that's
coming
down
the
pipeline
as
well
mark
is
there
any
other?
Would
you
like
to
make
any
other
comments
or
insight
on
that.
B
No,
I
I
was
well,
I
take
it
back.
Yes,
one
item.
I
was
proud
to
see
a
developer
in
the
community,
quoting
from
the
page
in
a
mention
in
an
answer
to
a
bug
report
on
jira.
Somebody
had
submitted
an
enhanced
request.
Hey
give
me
this
in
blue
ocean
and
the
the
responders
said
appreciate.
Thank
you
for
the
response
refer
to
our
comment
on
blue
ocean.
It
won't.
It
is
not
likely
to
be
implemented
unless
you
implement
it.
A
Very
nice
yeah
and
then
so
mark
you
want
to
touch
base
on
these
search
improvements
for
jenkins.io
item.
B
So
so,
when
I'm
searching
for
something
in
using
the
search
field
on
jenkins.io,
it
sometimes
gives
me
much
worse
results
than
it
used
to,
and
that's
because
we
need
to
do
this
upgrade,
but
as
far
as
I
can
tell,
it
needs
to
be
either
me
or
gavin
mogan
that
do
it,
because
it's
a
privileged
operation
that
has
to
be
done
to
configure
the
algolia
site
that
does
the
search
engine
generation
for
us.
So
it's
it's
something
we
have
to
access,
it's,
not
something
just
anybody
can
do
so.
I
guess
kevin.
B
A
Great
yeah
and
yeah,
and
I
want
to
be
able
to
I'll
help
whatever
I
can
do
to
like,
add
any
documentation
in
or
if
there
needs
to
be
new
things
added
to
make
sure
the
search
results
are
hitting
more
than
happy
to
step
in
and
take
care
of.
All
that
you
know.
A
Okay,
so
the
next
base
lts
baseline,
is
going
to
require
java
11
for
the
september
base,
the
server
lts
the
baseline
is
likely
going
to
be
2.361.
A
There
has
been
a
thread
started
in
the
jenkins
developers
group,
so
that's
there
and
we
have
there's
already
a
conversation
going
around
that
the
next
lts
is
also
going
to
support
java
17..
So
that
will
be
a
new
thing
coming
out
that
people
want
to
be
aware
of
and
find
out
the
upgrade
guide
and
change.
A
Log
content
creation
and
gathering
will
start
soon
enough,
since
that
will
be
part
of
my
ongoing
work
for
the
next
lts
and
as
soon
as
those
requests
start
coming
in
and
we'll
start
putting
that
together.
A
One
of
the
other
things
that's
come
up
recently
in
our
docs
office
hours
is
the
commercial
support
page
idea
that
gavin
mogan's
proposed.
The
idea
is
that
we
have
an
updated
version
of
our
support
site
because
right
now
our
commercial
support
site's
out
of
date,
and
it
doesn't
offer
very
many
relevant
items.
A
So
there's
been
a
lot
of
discussion
between
members
of
community
gavin,
mark
myself,
daniel
beck
and
lots
of
others
that
we
want
to
figure
out.
What's
the
best
way
to
go
about
implementing
this
page,
what
kind
of
information
we
can
put
on
this
page,
what
things
are
going
to
be
helpful?
What
extra
items
that
we
might
be
able
to
include
on
the
page
there's
been
mentions
of
cloud
services,
since
it
might
not
be
a
direct
vendor,
but
it's
something
we
work
with.
So
there's
a
lot
that
can
be
applied
here.
A
The
idea
and
obviously
we
want
as
much
community
involvement
and
feedback
as
possible.
This
is
something
that's
going
to
be
beneficial
to
the
community
as
a
whole,
so
it
only
makes
more
sense
to
have
as
much
input
on
it
as
possible.
A
It's
definitely
still
a
work
in
progress.
This
is
not
something
that's
going
to
be
finished
up
in
the
next
week
or
two,
but
as
long
as
we
can
keep
pushing
forward
on
it
and
getting
better
feedback
and
more
info,
we
can
continue
to
build
that
vendor
site
and
make
sure
that
it
looks
great,
and
then
it
has
things
like
direct
links
to
cut
to
support
and
other
really
helpful,
useful,
necessary
items
that
just
are
missing
right
now.
A
Does
anyone
have
any
other
comments
or
feedback
on
the
commercial
support?
Vendors
idea
anything
I
mean
the
the
ticket
is
linked
here
in
the
agenda,
so
it's
always
accessible.
I
can
post
it
in
the
getter
channel
as
well
afterwards,
so
that
it's
readily
visible,
but.
A
Okay
and
then
mark,
do
you
want
to
just
touch
base
on
the
change
log
entries,
multiple
repositories,
items.
B
Yeah,
I
I
haven't
done
the
ask
to
the
developer
list,
yet
it's
I
think
what
we
want
to
do
is
I'm
going
to
create
a
ticket
in
the
in
the
the
backlog
somewhere.
That
says,
hey
extend
it
for
this.
It's
still
the
the
idea
is
still
somewhat
nebulous.
It's
infrequent
enough
that
I'm
not
sure
we
want
to
do
it
always
and
the
the
the
interface
is
complicated.
B
A
Right
yep
makes
sense
and
that
actually
kind
of
leads
into
the
next
item
on
our
list.
The
2.346.3
changelog
and
upgrade
guide
itself.
So
that's
been
opened
up
and
ready
to
go.
That's
been
added
to
the
lts
checklist
that
is
currently
open
for
2.346.3.
A
A
It
should
have
everything
ready
to
go
for
the
release
next
week
and
there
were
updates
from
a
few
different
places,
such
as
chicken's
core,
and
then
the
remoting
update
came
through
so
yeah
there's
definitely
a
chance
that
multiple
change
log
entries
can
come
from
multiple
places,
but
as
long
as
we
can
get
them
into
one
place,
that
shouldn't
take
care
of
everything
and
then
lastly
mark
do
you
want
to
just
briefly
touch
on
the
julian
updates
for
java
11.
B
B
Okay,
so
kevin.
If
you
can
update
that
it's
it,
there's
not
a
it's,
not
a
crisis,
that
we
must
do
it,
it's
just
just
that
it
will
be
good
for
us
to
get
there
and
I'd
on
that
second
line
down
the
extension
indexer
so
in
the
jenkins
documentation
on
jenkin.io.
B
I
realized
that
that
extension
indexer
is
badly
out
of
date,
whereas
vihan's
work
has
already
updated
the
pipeline
step
stock
generator
to
use
modern
tooling.
This
extension
indexer
is
well,
it
didn't
even
compile
with
java
11..
It
was
that
out
of
date,
so
so
at
least
now,
with
this
change
it
compiles
with
java
11..
However,
there
are,
there
are
a
whole
bunch
of
failures
that
need
to
be
analyzed
to
see.
Is
that
a
safe
change
given
the
current
state
of
the
code
base?
B
And
if
not,
what
could
we
do
to
make
it
more
modern
and
still
be
safe?
And
I
don't
know
when
I'll
get
to
that
it?
I
started
it
because
I
was
of
interest,
but
I'm
not
sure
I'm
going
to
finish
it,
because
I'm
not
persuaded
that
that
I
can
take
the
time
to
do
the
analysis
yet.
So
this
is
one
where,
if
somebody
wants
to
do
a
little
bit
of
java
coding,
they're
welcome
to
that's
it.
For
me,.
A
C
I
wanted
to
add
that
was
like:
do
we
need
to
make
changes
to
the
bomb.
C
Documentation
to
see
the
new
change,
the
newer
version
do
we
have
to
manually.
Add
it.
B
I'm
so
I
don't
know
for
sure.
I
think
that
in
order,
so
what
the
pipeline
steps
dock
generator
right
now
does
is
every
week
it
receives
a
new
dependabot
generated,
pull
request
that
offers
to
upgrade
its
dependency
from
last
weekly
to
current
weekly.
But
I
don't
know
if
that's
that's
what
you're
asking
is
that
the
question
you're
asking
or
are
you?
Were
you
asking
something
different.
C
Yes,
so
basically,
I
want
to
say
that
once
we
want
to
run
the
job
again
for
these
steps
documentation
will
we
need
to
upgrade
the
jenkins
version
that
it
uses.
So
currently,
I'm
I'm
seeing
two
point
360.,
so
I
will
need
to
update
that
is
this
still.
The
buggy
version
is
what
I'm
asking.
B
B
So
if
you
can
open
up
that
url
that
I
just
put
in
the
chat
okay,
so
this
is
the
pipeline
steps,
doc,
generator
and
kevin.
If
you'll
pick
one
of
those
pull
requests,
196
or
yeah,
so
now
click
the
github
link
there
on
the
left
hand,
side
of
the
page,
click
that
github
link
and
let's
see
what
it
yeah.
Okay.
So
this
one
updated
us
two
days
ago
from
361
to
362.
B
B
A
C
B
The
the
the
latest
version
is
2.362
and
it
resolved
the
problem.
So
the
the
root
problem
that
I
saw
in
the
back
end
extension
index
generator
was
that
the
source
code
was
not
available
for
jenkins
2.361
in
the
maven
repository
archive
and
because
the
source
code
was
not
available,
it
failed
to
do
the
generation.
B
We
fixed
that
in
time
for
2.362,
so
the
source
code
is
available
for
2.362
in
the
repository,
and
if
that
had
been
at
the
root
of
this
change
to
to
map
things
to
jenkins
core,
then
that
would
be
fixed,
but
I
I
I'm
not
sure
that
that's
at
the
root
of
it.
So
now
it's
maybe
the
best
answer
is
vihan.
Could
you
paste
a
link
to
that
page?
That's
broken
into
our
notes.
It
was
it's.
I
think
it
was
the
checkout
page.
Is
that
right.
B
C
Just
it
shows
that
the
the
problem
is,
it
should
be
present
in
the
python
scf
step
plugin
and
not
before.
So
it's
not
able
to
find
its
parent
right.
B
B
C
B
Okay,
so
so
that's
the
regression
is,
is
this
thing
that
says
jenkins
core
isn't
actually
helping
us
as
or
at
least
it's
it
seems
to
have
broken
many
other
things.
We
need
to
be
get
back
to
what
we
were
previously
great.
Thank
you
so
because
that
job
on
ci.jenkins.io
has
a
history,
we
can
actually
look
at
the
old
generations
and
see
when
the
change
happened.