►
From YouTube: 2022 06 23 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
B
Welcome
everyone:
this
is
the
european
docs
office
hours
for
jenkins
june
23rd
2022
edition
it's
been
a
busy
week
for
us
here,
so
there's
a
fair
amount
of
stuff
to
talk
about,
and
today
we
have
the
lts
which
just
released.
Yesterday
we
had
a
blog
post
concerning
a
couple
items
there.
The
changelog,
the
upgrade
guide-
and
I
know
mark-
was
doing
a
stream
just
prior
to
this.
Regarding
some
of
the
other
items
that
came
up
with
it,
which
is
great,
then
we
have
jahan
here
so
vihan.
B
If
you
can
give
us
an
update
on
the
google
summer
of
code
and
how
everything's
going
with
that
any
progress
you've
made
with
it
with
some
of
the
items
from
since
last
week
and.
B
and
then,
if
alex
joins
us,
we
can
talk
more
about
the
localization
with
crowden,
but
if
he
doesn't
join
us
today,
we'll
just
ignore
that
for
next
time,
so
first
things
first
yeah.
The
lts,
like
I
said,
came
out
released
yesterday
and
mark.
Would
you
like
to
add
some
kind
of
additional
context
and
details
about
the
release
and
how
everything's
going.
A
So
it's
looking
promising
so
far
haven't
seen
any
issue
reports
come
into
issues.jenkins.org,
yet
it
did
include
a
security
advisory.
The
security
advisory
means
that
more
users
should
deploy
it
more
rapidly
than
even
typically
so.
We're
looking
forward
to
that
now.
The
security
advisory
also
published
a
an
incremental
version
of
the
preceding
lta
lts.
In
case
people
weren't
ready
to
adopt
the
new
one
and
it
produced
a
new
version
of
the
weekly
in
case
they
were
already
using
the
weekly
version.
B
Great,
thank
you
so
much
yeah
and
from
my
side
of
things
I
was
able
to
publish
a
blog
post
regarding
the
svg
icon
migration,
since
that's
going
to
be
a
big
change
that
comes
along
with
the
lts
update
that
the
changelog
will
address
a
lot
of
the
ui
improvements
and
modernization.
That's
also
taking
place
for
this
release.
So
there's
a
lot
of
great
great
info
out
there
on
what
changes
have
happened.
Steve
hill
is
one
of
the
jenkins
contributors
that
works
with
us
on
a
regular
basis.
A
Yeah
so
steve's
a
a
jenkins
administrator
and
he
did
a
he
did
a
blog
post
on
his
personal
blog
about
his
experience,
upgrading
jenkins
through
one
of
the
earlier
large-scale
upgrades,
guava
and
he's
applying
similar
techniques
learning
further
and
describing
it
sharing
it
as
he
goes
through
these
kind
of
changes.
He
manages
multiple
jenkins
controllers
across
his
company
and
has
to
deal
with
variation
between
the
controllers.
It's
an
interesting,
interesting
space
that,
where
steve
works.
B
Cool
very
good,
that's
awesome,
and
that's
also
a
lot
of
great
visibility
for
what
we're
doing
so
kudos
for
everyone
on
that
and
then
the
spreadsheet
that
we
included
in
the
jenkins
tick.
The
jenkins
jira
ticket
just
have
the
tracking
for
all
plugins
that
have
either
been
updated
or
need
to
be
updated.
B
Regarding
this
change,
which
steve's
also
been
able
to
include
in
his
blog
post
and
share
out
which,
if
I'm
not
remembering
correctly,
he
said
it
was
very
helpful
and
just
kind
of
identifying
all
these
things
and
making
it
very
easy
to
recognize
and
act
on.
B
So
wonderful.
So
would
you
want
to
give
us
an
update
on
the
google
summer
of
code.
C
Project,
yes,
hello,
everyone
sure.
So
after
last
week
I
was
able
to
get
the
second
pull
request
in
which
was
the
plug-in
list
on
the
pipeline
steps
reference
page,
and
then
we
discussed
that
we
can
include
it
for
now,
and
we
can
wait
for
some
feedback
regarding
that
page.
If
the
users
want
to
get
anything
changed
for
that
or
perhaps
even
get
it
removed.
So
we'll
wait
for
that
and
until
then
we
think
that
we
can
include
that
particular
feature
on
the
steps
reference
page.
C
So
that
was
for
it
and
then,
after
that,
in
the
pipeline
steps
talk
of
officers.
Christian
explained
me
the
working
of
the
plugin
manager.
That
has
been
mocked
from
the
general
instance
so
that
that
was
something
very
interesting.
C
And
since
then,
I
created
a
couple
of
pull
requests
for
the
pipeline
step
stock
repository
the
first
one
being
about
separating
the
declarative
steps
generation
from
the
main
class,
which
is
something
that
christian
thought
would
be
better
to
do,
and
the
second
one
was
some
minor
refactoring
things,
so
both
of
them
were
pushed
today
for
the
next
week.
C
The
agenda
would
be
to
get
the
data
type
on
the
parameter
details
on
the
heading,
as
I
discussed
in
the
previous
officers
and
after
that,
one
of
one
of
our
goals
would
be
to
separate
the
entire
hyperlocal
plugin
manager
from
the
repository,
and
that
is
to
create
a
repository
for
the
plugin
manager
itself.
That
can
be
used
by
some
other
other
classes.
C
Other
repositories
in
case
as
well,
and
that
will
be
just
imported
and
used
for
the
pipeline
step
stock
generator,
because
this
is
something
that
we
think
should
be
present
as
a
global
feature,
so
that
others
can
use
it.
Because
there's
some
really
nice
things
happening
and,
as
christian
said,
this
could
be
helpful
for
the
rest.
Api
generator
as
well.
So
getting
that
plug-in
manager,
isolated
and
functioning
independently
is
something
which
would
be
very
cool.
So
yeah.
B
That
all
sounds
wonderful
and
is:
is
there
anything
that
you
could
share
as
far
or
you
wanted
to
share?
As
far
as
any
of
this
goes
on,
I
can
stop
sharing
my
screen.
If
you
want
to
share
yours
or
if
there
is
pull
requests
that
you
would
like
us
to
take
a
look
at
or
anything
like
that,
please,
by
all
means
feel
free
to
share
those
either
here
or
in
getter
or
anywhere
that
you
want
to
make
sure
they're
available.
C
Sure
so
I
usually
link
the
pull
requests
that
are
related
to
the
website
on
the
docs
channel
itself,
so
you
can
go
ahead
and
find
them
and
then
over
there
you
can
check
out
artworks
using
the
deployment
link
like
I'm
getting
some
feedback
from
others.
Like
tim,
has
commented
some
things
on
that,
and
I
guess
this
is
overall,
it's
going
quite
smoothly.
So
if
there's
anything
specific
that
that
was
in
your
mind
to
get
to
review
today,
so
I
can
perhaps
present
that
particular
thing.
B
Yeah,
I
didn't
have
anything
specific
in
mind
behind.
I
just
wanted
to
make
sure
we
gave
you
enough
time
to
share
and
everything.
Since
last
week
we
came
up
against
the
time
a
little
bit.
That's
all.
C
Okay
sure
so
I
can,
I
think
both
the
pull
requests
are
like
ready
to
merge
and
you're
just
waiting
for
the
release
this
week.
So
I
think
we're
good
to
go
in
that
sense.
A
A
D
A
Think
has
been
reviewed
yet
the
plug-in
list
on
the
steps
reference
page.
Do
we
okay,
but
we
do
have
comments
there
from
tim
and
from
daniel
beck
okay.
So
I'm
not
ready
to
merge
the
second
one
until
we
get.
We
address
daniel's
daniel's
observations,
but
the
first
one,
let's
see
did
did
we
have
any
new
feedback.
A
A
C
That's
fantastic
and
I
think
the
pipeline
steps
stock
pull
requests
are
also
rather
straightforward
to
review
and
merge.
I'm
keeping
the
request
a
little
bit
bite
size
so
that
it's
easier
for
the
reviewers
also,
so
I'm
I
think
that
that
would
also
get
merged
like
not.
It
won't
take
much.
A
Time,
yeah
so
the
that
that
one
now
has
a
conflict,
so
you'll
you'll
need
to
revisit
it.
The
conflict
comes
in
from
the
the
changes
that
were
just
merged
for
the
your
previous
pull
request,
so
you've
got
work
to
do
there
sure
I
look.
B
Great,
thank
you
so
much
for
han.
Is
there
anything
else
you
want
to
share,
or
does
that
cover
everything
for
you?
I
think
everything
is
good.
No.
Thank
you
great.
Thank
you.
So
much.
B
The
next
item
on
the
agenda
was
the
upcoming
java
11
requirement,
so
that
is
going
to
be
part
of
the
weekly
release
line
that
comes
out
next
tuesday
june
28th,
there's
going
to
be
a
blog
post
coming
from
basil
regarding
the
requirement,
it's
a
very
in-depth,
very
thorough
article
blog
post
about
it
that
addresses
why,
how
everything
up
to
making
sure
that
it's
installed
properly
and
updated
properly.
B
A
It's
the
issue
is
resolved
and
and
thanks
to
basel
crowe,
for
implementing
the
resolution
to
the
problem,
it
was,
it
was
a
and
there
is
more
that
will
probably
need
to
be
done.
If
you
visit
javadoc.jenkins.io.
What
you'll
find
is
it's
a
conglomeration
of
multiple
javadoc
pages?
It's
got
a
top
level
page
for
the
jenkins
core,
so
java,
javadoc,
no
c,
oh
yeah,
and-
and
so
it's
a
this-
is
a
somewhat
special
case.
The
java.jenkins.io
site
originally
was
just
for
jenkins
core
and
we
realized.
We
really
only
need
one
url.
A
We
could
put
all
the
plugins
under
that
same
url.
So
if
you
click
jenkins,
core
you'll
see
the
javadoc
for
the
more
a
recent
weekly
in
this
case
2.355,
and
it's
rendered
using
java
11
layout,
so
java,
11
layout
puts
that
search
search
field
in
the
top
right
hand
corner
so
kevin.
If
you
search
for
file
path,
for
instance,
f-I-l-e-p-a-t-h
you
see,
oh
here
are
all
the
places
that
file
path
is
used
and
if
you
click
one
of
those,
it
will
take
you
to
that
page.
A
A
A
Oddity
because
we're
placing
all
sorts
of
different
components
under
the
same
thing
now
pick
click
jenkins
components,
and
here
the
one
that
has
been
updated
is
windstone,
so
bottom,
the
bottom
most
very
last.
One
is
also
using
java,
11
semantics
same
look
and
feel
now
go
back
one
page
and
let's
look
at
one.
That's
java,
8,
like
jenkins
test
harness.
A
B
Great.
The
next
item
was
the
support
for
java
17.
again
that
will
be
announced
with
basil's
blog
post.
I've
also
been
going
into
the
existing
java
documentation
and
updating
that
to
make
sure
that
that's
included
in
our
support
and
also
to
make
sure
that
the
java
11
requirement
is
updated
as
well.
There's
going
to
be
some
differentiation
between
the
two
until
the
lts
catches
up
with
the
weekly
release
line
in
september.
B
At
that
point,
I'll
be
able
to
go
back
in
and
re
redo
the
documentation
to
make
sure
it
only
refers
to
java
11
upwards,
so
that
will
all
be
in
the
coming
months
and
coming
weeks,
so
lots
to
look
forward
to
there
bruno
did
you
have
anything
that
you
wanted
to
talk
about
or
share
in
regards
to
I
mean
anything
that
you've
been
working
on.
D
B
And
mark
did
you
have
anything
else
that
you'd
like
to
add
to
the
agenda?
I
know
we
didn't
get
a
chance
to
connect
beforehand,
so.
B
All
right
great!
Well,
then,
if
we're
all
set,
we
can
stop
the
recording
and
that'll
be
posted
as
it's
a
as
mark.
Can
this
yeah
I'm
sure
he
has
a
couple
other
things
on
his
plate,
so
it
might
be
24
48
hours.