►
From YouTube: 2022 07 07 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
to
the
european
jenkins
docs
office
hours
today
is
july
7th,
and
today
we
have
a
little
bit
more
of
an
agenda
than
we
have
lately.
We
have
a
couple
action
items
that
mark
will
share
just
quick
status
update
on.
We
have
some
exciting
news,
a
lot
of
stuff
going
on.
We
had
our
2.358
release
this
week,
which
now
is
requiring
at
least
java
11..
B
We
have
the
jenkins
232.346.2
lts
release
coming
out,
that's
going
to
include
the
changelog
and
upgrade
guide
behind
have,
if
we'll
be
able
to
share
the
google
summer
code,
progress
updates
that
he
has.
We
have
some
additional
improvements
and
enhancements
that
we're
going
to
be
working
on
for
java
11..
It's
not
a
one
and
done
situation.
B
There
are
still
other
pieces
that
need
to
be
updated
and
basil
cross
working
on
that
for
us,
and
then
we
also
have
a
proposal
by
gavin
mogan
who's,
one
of
the
jenkins
governance
board
members
about
enhancing
and
creating
a
new
commercial
support
site.
The
current
one
is
out
of
date
and
not
necessarily
the
best
resource
for
users,
so
creating
an
updated
one
based
off
on
the
stories.jenkins.io.
B
Will
go
a
long
way
in
helping
to
improve
that
experience,
and
then
there
was
a
pull
request
submitted
recently
that
suggested
some
changes
to
the
navigation,
banners,
headers,
footers,
carousel
sections,
pretty
much
any
part
of
the
background
on
the
jenkins
site
and
they're.
Looking
for
feedback,
we've
got
some
mark
and
other
folks
have
already
responded.
Let
them
know
about
recent
font,
changes
and
other
pieces
that
are
important
in
that
case,
but
we'll
go
over
that
in
time.
So
first
things
first
mark.
B
Okay,
great
and
so
then
again,
the
2.358
weekly
release
line
was
released
this
week
so
now
that
requires
at
least
job
11.
It
also
offers
java
17
support.
No
java
8
is
no
longer
supported,
and
that
will
be
reflected
by
the
lts
in
september
when
it
catches
up
and
matches
the
weekly
release
line
requirements.
B
I'm
actually
I've
also
gone
through
and
added
some
context
to
the
documentation.
Regarding
that
letting
folks
know
that
there
is
that
distinction
between
the
weak
release
and
lts
releases,
so
hopefully
everyone's
very
clear
on
that,
and
they
have
if
they
have
questions
they
can
direct
them
properly,
but
that
should
be
fairly
clear.
B
B
B
Would
you
like
to
show
us
our
ticks
through
the
google
summer
code
and,
what's
what
you've
been
up
to
since
last,
we
spoke.
C
Sure
so,
a
couple
of
pull
requests
related
to
jenkins
that
I
got
much
this
week
and
the
first
one
being
about
the
data
types
details,
so
that
has
been
merged
and
we
can
see
the
reflected
changes
on
the
website
now,
so
everything
has
been
built
successfully
and
all
the
documentation
has
been
updated
accordingly,
all
the
ascii
docs.
C
Then
this
week
I
also
created
up
a
request
to
add
a
search
filter
on
the
pipeline
steps
reference
page.
So
basically,
this
steps
filter
will
filter
out
the
content
on
the
page
dynamically
and
like
yeah.
C
If
you
could
demonstrate
that
something
that
so
all
the
content
would
get
filtered
accordingly
and
basically,
the
advantages
of
this
over
a
normal
browser
like
search,
would
be
if,
for
example,
you
search
kit-
and
you
want
to
see
the
related
plugins
of
the
steps
when
you
switch
that
on
the
browser
you
get
the
results,
but
the
other
things
which
are
not
relevant,
don't
get
removed,
so
you
have
to
navigate
between
those
things
top
down
and
it's
quite
tedious.
C
So
now
I
think
this
makes
it
slightly
easier
to
understand
to
find
the
piece
of
information
that
the
user
wants.
So
this
was
the
request
that
was
merged
on
wednesday.
I
guess
yesterday,
kevin.
A
A
That
pipeline
steps
reference
search
for
the
word
checkout,
okay,
so
in
order
to
find
things
about,
checkout
checkout
is
one
of
the
most
commonly
used
operations
in
the
pipeline,
one
of
the
most
common.
So
I
would
search
for
the
word
checkout
in
the
old
days.
I
would
press
ctrl
f,
I
would
enter
the
word
checkout
and
it
would
find
the
bitbucket
server
integration
first,
which
is
not
relevant.
It
would
find
plastic
scm
second,
which
is
also
not
relevant
to
what
I
was
trying
to
do.
Finally,
it
showed
me
pipeline
pipeline
scm
step.
A
B
B
C
C
If
I,
as
mark
showed
us
last
week,
so
jamar
said
that
he'll
take
care
of
that,
so
the
cd
part
is
like
yet
to
be
done,
but
since
there
are
not
many
releases
that
are
happening
for
that
repository
right
now,
I
think
that
becomes
low
priority
for
us
and
adding
some
tests
to
it
are
some
things
on
my
agenda
right
now,.
A
C
We
can
get
so
we
can
replace
the
mock
jenkins.java,
mock
extension,
list.java
and
the
hyperlocal
plugin
manager,
the
main
body
of
the
from
which
we
can
actually
execute
the
reactor
and
query
the
plugin
manager
to
get
the
results.
So
these
three
classes
would
not
be
required
in
the
main
repository
any
longer.
B
Awesome,
thank
you.
So
much
looks
like
there's
been
a
lot,
so
that's
very
exciting
and
yeah
very
much
kudos
to
y'all.
Thank
you.
Next
on
the
agenda.
Just
some
java
11
further
improvements
that
we're
working
on
the
jetty
upgrade
from
version
9x
to
10x
and
a
few
other
dependencies
necessities
that
are
being
that
need
to
be
upgraded
basil
grows,
helping
us
and
working
on
those
upgrade
enhancements
again.
This
is
not
something
that
can
be
done
very
easily
or
in
one
go.
It
is
over
time.
B
So
it's
a
marathon
not
a
sprint
in
that
regard,
and
then,
while
mark's
typing
out
that
information
or
mark,
if
you
want
to,
would
you
be
able
to
share
a
little
insight
on
that.
A
Yeah,
it's
just
the
the
this
was
a
a
fun
improvement
that
comes
as
a
result
of
the
java
11
work.
The
jetty
project
announced
the
end
of
community
support
for
jetty
nine
about
a
month
ago.
Their
our
timing
is
really
good
to
get
off
jetty
nine.
They
were
willing
to
support
us,
we're
not
we're
a
little
higher
on
their
list
than
just
a
community
project,
but
getting
off
jetty
nine
and
onto
jetty
10
is
a
real
positive.
A
Unfortunately,
in
this
case,
our
automated
tests
were
testing
a
particular
aspect
of
web
sockets,
but
weren't
testing
in
a
production-like
environment.
It
was
discovered
that
there
was
this
test
gap.
Jesse
glick
and
basel
crowe
have
been
working
together
to
close
that
test
gap
and
to
get
ready
to
do
the
upgrade.
B
Great
thank
you,
and
is
there
any
anything
else
that
we
should
know
about
the
java
11
language
extensions
in
this
case.
A
Well
and
this
one
may
impact
us
in
ways
that
that
are
documentation
related.
What
basel's
discovered
is
a
a
leading
jenkins
user.
Steve
hill
has
implemented
a
thing
with
a
tool
called
open.
Rewrite
open
rewrite
is
an
automation
system
that
will
do
apply.
Code,
refactorings
and
the
reason
this
matters
to
documentation
is:
we've
got
a
pending
pull
request
for
a
tutorial
on
how
to
modernize
a
jenkins
plugin,
and
this
user
steve
created
an
open
rewrite
rule
to
express
one
of
those
modernization
steps
through
automation.
A
Now
it
doesn't
do
automated
evaluation
of
the
quality
of
the
of
the
change,
but
it
does
perform
the
change,
and
so
it
gives
the
user
the
contributor
a
jump
start
on.
Oh,
I
ran
this
open
rewrite
rule
and
it
performed
these
code
transformations
for
me
now.
I
should
focus
on
testing
to
be
sure
it
works
to
be
sure,
it's
well
behaved
and
then
I
submit
a
pull
request.
B
That's
pretty
awesome
definitely
sounds
like
it
can
be
very
useful
for
us
if
we
can
get
that
kind
of.
A
B
Fantastic,
thank
you
mark
next
on
the
agenda.
B
So
just
a
couple
days
ago,
or
within
the
last
week,
gavin
mogen
who's
part
of
the
jenkins
government's
board,
had
made
a
suggestion
about
revamping
and
creating
a
new
commercial
support
page
for
a
vendor
support
page,
essentially
looking
to
make
sure
that,
if
we're
going
to
have
a
page
like
this
for
support
that
it's
up
to
date
offers
something
that
the
user
can,
you
know,
filter
through
navigate
a
bit
more
cleanly
and,
more
importantly,
things
like
direct
links
to
the
support
understanding
what
the
users
are.
B
Looking
for,
understanding
what
the
makeup
of
the
user
base
is
who's
looking
for
help
what
they're
looking
for
help
with
and
is
looking
for
just
general
feedback
on
anything
else
that
might
be
worth
tracking.
As
you
can
see,
there's
already
been
a
few
suggestions
and
comments
about
the
direction
that
we
can
take.
As
far
as
the
support
page
goes
and
gavin's
really
receptive
to
any
ideas,
so
by
all
means
feel
free
to
share.
B
If
you
have
any
suggestions,
any
experiences,
anything
that
might
be
worth
noting
that
hasn't
been
put
down
already,
even
if
it
is
that's
fine,
but
this
is
something
that's
really
it's
going
to
be
nice
to
have
after
the
stories.jenkins.io
pages,
finish
up
and
would
go
a
long
way
in
helping
just
reassure
and
reaffirm
a
lot
of
the
jenkins
resources
and
functionalities
with
those
external
partners.
So
this
is
like
I
said
this
is
just
something
that
we've
just
started.
B
Working
on
and
I've
been
working
with,
I've
been
sharing
some
suggestions
with
gavin
as
well,
so
yeah
that
that's
something
that's
where
we
have
something
to
look
forward
to
in
the
future
and
then
the
other
item
that
came
up
this
week
is
a
pr
that
had
been
submitted
request.
Looking
for
some
changes
to
the.
B
Navigation
and
some
other
parts
of
the
actual
jenkins
pages,
so
the
preview
site.
So
this
is
the
background
that
is
set
up
in
the
preview,
the
fonts
change.
There
are
some
other
items,
however,
there's
been
some
other
recent
changes
to
the
system
fonts,
for
instance,
with
jenkins
and
with
the
way
things
are
currently
going
in
the
world
and
with
jenkins.
B
We
want
to
make
sure
that
everything's
on
point
and
aligned
for
messaging
for
branding
everything
else
so
mark
and
some
others
have
commented
on
the
post
and
shared
their
insights
and
recommendations,
suggestions
for
what
can
be
done
so
there's
definitely
some
merit
to
talking
about
this
and
discussing
the
image,
usage
and
and
just
overall
burning,
color
scheme,
etc.
B
So
this
is
another
thing
that
any
feedback,
any
suggestions
that
can
be
shared
would
be
much
appreciated
and
will
go
a
long
way
in
helping
to
determine
what
sorts
of
improvements
we
can
make
in
the
future
or
sooner
than
later,
if
there's
something
that
we
can
agree
on
now,
yeah
and
now
mark
I
I
did
get
a
chance
to
look
through
these
a
little
bit.
Is
there
anything
that
you
wanted
to
point
out
or
make
note
of
on
these
in.
A
Any
specifics,
or
just
looking
for
community
feedback-
I
am,
I
am
notoriously
bad
at
assessing
quality
of
design
and
others
may
feel
similarly
inadequate.
So
those
who
are
good
in
design
like
japanese,
who
is
whose
comments
are
later
on
he's
very,
very
good
at
design
and
he's
very
so
I
give
great
weight
to
to
his
opinions
and
and
his
observations.
So
likewise,
tim
jacom
and
jan
faraczek
are
also
very,
very
good
in
this
kind
of
thing,
whereas
I'm
really
bad.
B
That's
fair,
I'm
not
so
great
with
design
either.
So
I
feel
you're
entirely
on
that.
Thank
you
very
much
lauren
great.
So
that
covers
the
agenda
that
we
have
written
down
for
today.
Did
anyone
have
any
other
points,
topics
or
items
that
they'd
like
to
add
to
or
bring
up.
B
And
as
a
side
note,
the
community
brown
bag
was
earlier
today
and
was
a
really
lovely
experience.
Bruno
actually
gave
a
wonderful
talk
about
the
coffee
papers
and
how
to
really
enhance
your
abilities
and
chances
with
them.
How
you
can
do.
C
B
B
Okay,
yeah-
and
I
think-
and
I
also
just
appreciated
a
lot
of
the
kind
of
the
self
affirmations
that
you're
sharing
and
how
to
take
care
of
yourself
when
you're
also
trying
to
share
all
your
excitement
and
knowledge
with
everyone
else.
So
it
was
really
nice.
B
Thank
you,
but
yeah
that
covers
everything
for
today
and
we've
made
it
through
the
agenda.
I
think
that
we
could
stop
a
video
recording
if
you'd
like.