►
From YouTube: 2023 05 05 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).
B
Welcome
this
is
documentation
office
hours,
it's
the
5th
of
May
2023
we're
in
the
Asia
section
of
office
hours
topics,
I've
got
pipeline
steps,
reference
damaged,
Google
summer
of
code,
Community
feedback
suggestions,
transition
from
java,
11
to
Java,
17,
end
of
life
notifications
and
early
end
of
life
of
Centos
7..
Anything
you
want
to
add
Chris
nope,
all
right,
okay,
so
first
topic
is
that
we've
got
an
unfortunate
and
it
seems
to
have
happened
within
the
last
two
or
three
days,
unfortunate
damage
to
the
plugin,
the
pipeline
documentation.
B
We
discovered
during
office
hours
Europe
that
it
appears
to
be
the
pipeline
step,
stock
generator
and
some
recent
change
to
it.
And
so
the
bisect
is
running
pipeline
steps.
Dock
generator
through
a
series
of
checking
different
different,
commits
to
see
if
this
is
the
one
that
collapsed
the
size
of
the
file
or
if
it's
the
next
one
Etc.
C
C
Not
really,
but
do
you
have
do
you
think
we
should
post
a
link
to
that
like.
B
B
B
And
it's
got
my
notes
in
it
of
things
that
things
that
we've
discovered.
We
found
that
older
versions
of
the
doc
generator
created
a
much
larger
file
than
the
new
ones,
and
the
bisect
is
trying
to
identify
which
which
commit
did
the
damage.
C
A
C
B
C
Yeah
so
like
for
this
year
for
2023,
we
got
four
projects
selected
and
I,
think
or
or
contributors.
C
C
Yeah
so
we
have,
there
are
projects,
so
maybe
yours
is
like
in.
B
A
A
B
C
C
C
Yeah,
maybe
we
should
talk
a
bit
about
seismic
project,
because
at
this
time
all
four
projects
are
made
him,
which
means
that
they
wouldn't
they're.
Not,
they
would
finish
by
the
end
of
summer
and
they
wouldn't
be
well
unless
we
have
some
exceptions
against
them,
since
they
normally
we
go
over
it
yeah
yeah,
so.
C
End
of
summer
yep,
so
it
was
like
around
September
and
the
end
of
summer.
It's
a
well
on
September
again.
A
B
Thank
you,
Chris
thanks
very
much,
so
the
next
next
topic
topic
was
on
community
feedback
suggestions.
So
this
was
one
we
had
discussed
last
week
and
I've
not
seen
any
further
comments.
We
had
discussed
it
and
I
included
the
notes
in
in
the
comment
here
about
end
users
using
the
ratings
and
possibly
consider
accepting
General
text.
B
A
C
A
B
C
C
B
So
in
the
tutorial
in
the
improve
a
plug-in
tutorial,
we
give
them
an
example.
So
if
we
look
oops
wrong
one,
if
we
look
at
it
the
improve
a
plug-in
tutorial,
we
tell
them
when
you
add
your
Jenkins
file,
test
Java
11.
In
this
case
the
example
is
chess,
Java
11
on
Windows
test,
Java
17
on
Linux,
so
that
both
get
tested-
and
you
know
that
your
plugin
supports
compilation
and
running
its
test
with
both
Java
11
and
Java
17.
A
B
And,
and
one
of
the
things
we've
found
there
is
that
there
are
still
some
few
plugins
that
don't
support
operation
with
Java
17
and
need
some
additional
improvements,
so
that
one
of
the
benefits
of
that
step
is
the
maintainer
of
the
plug-in
will
detect
in
their
normal
course
of
development.
Oh
I've
got
a
Java
17
problem.
I
need
to
fix
this.
C
Yeah
me
too,
I
do
actually,
let's
plug
in
with
some
issues
with
17,
because,
like
I
think
it
was
like
some.
Some
class
is
being
deprecated
and
no
longer
supported
in
17.
I
have
to
move
it
from
more
of
a
pocket
into
maintaining
yeah.
C
B
B
C
As
I'm
just
wondering
is
like,
is
it
any
other
documentation
sections
we
need
to
update?
Besides
what
we
discussed
so.
B
C
A
B
And
there
there
are
instructions
in
the
documentation
that
say
that
the
agent
Java
version
must
match
the
the
controller
Java
version,
and
that's
part
of
this.
For
instance,
the
Java
upgrade
guidelines
where
it
says
hey,
you
must
have
the
correct
jvm
version
on
the
agents
and
it
must
match
the
jvm
version
on
the
controller.
A
Oh
okay,
that
has
changed
then,
okay,
see
how
out
of
it.
I
am
well.
B
B
B
A
B
Okay,
so
next
topic
is
end
of
life
notifications.
We
discussed
this
two
or
three
meetings
ago.
There
is
now
an
open
pull
request.
It's
in
draft
State,
because
we've
realized,
thanks
to
a
good
review
from
Tim
jacombe,
that
the
way
it's
structured
right
now
isn't
viable.
It
needs
to
be
reworked,
but
the
concept
is
good.
Let's
see
if
we
can
get
the
that
pull
request
and
we'll
show
you
what
the
screenshot
looks
like
oops.
It
would
help
if
I
look
at
Jenkins
core
instead
of
the
docs.
B
The
example
is
for
red
hat
for
Red
Hat,
seven,
a
pop-up
or
a
a
subsection
of
the
page
that
says
hey
your
operating
system
will
no
longer
be
supported
by
Jenkins
after
such
and
such
a
date,
and
please
plan
your
upgrade
so
that
you're
off
of
this
thing
before
we
end
support
of
it
and
then
a
link
to
documentation
that
gives
more
details.
B
B
And
now
this
piece
is
the
piece
that
highlights
that
it
needs
to
be
redone,
because
what
I
did
was
I
created
a
monitor
for
each
operating
system
version.
Tim
correctly
noted,
really
the
controller
runs
only
one
operating
system,
so
we
could
just
iterate
over
all
the
choices
find
the
one
they
are
running
and
tell
them
about
that
one.
We
don't
need
to
have
Fedora
36
listed
in
this
list
if
they're
not
running
fedora,
36.
B
B
And
Basel
Crow
noted
he
thinks
really
the
piece
of
this.
That
I
was
asking
about
early
end
of
life.
His
answer
was
look.
End
of
life
is
already
happening
and
has
in
many
cases
happened
for
this
operating
system
version,
because
the
system
D
based
RPM
installer
no
longer
supports
it.
So
and
then
the
the
container
image
is
no
longer
maintained
and
hasn't
been
maintained
for
two
and
a
half
years.
B
B
A
C
B
C
That
one
yeah,
so
if
you
click
on
that,
if
it
go,
if
you
like,
if
we're
going
to
see
a
lot
of
the
pages
with
like
yellow
triangle,
the
warning
but
the
one
icon,
so
click
on
any
one
of
them,
so
I'm
just
wondering
is
like
I
I
have
been
contemplating
like
help
me
out
contributing
by
contributing
like
by
working
through
the
like
one
by
one,
these
items
to
like
add
content
to
them.
B
I
think
so
I
think
it
would
be
well,
at
least
for
me,
I
think
it
would
be
very
valuable.
Some
of
them
it
may
be
as
simple
as
declaring
this
thing
is
actually
already
well
enough
described
so,
for
instance,
the
internationalization
section
as
I
look
at
this
one
I'm,
not
sure
that
there's
much
more
to
say
other
than
possibly
we
add
a
section
about
crowd
in
other
than
that.
B
Than
that
it,
it
describes.
How
do
you
internationalize
Java?
How
do
you
do
it
in
jelly
I'm,
not
even
sure
we
want
to
suggest
to
people
use
groovy
for
views
anymore,
and
so
this
one
I
think
is
already
in
quite
good,
quite
good
condition
and
maybe
a
link
to
or
the
crowd
in,
localization
video
embedded,
and
then
we
remove
the
work
in
progress
indicator.
Yes,
that
would
be.
That
would
be
deeply
appreciated.
Chris.
A
A
C
A
B
So,
and
to
highlight
one
that
is
of
interest
to
me,
this
testing
one
is
one
that
I've
been
wanting
to
add
to,
and
it's
actually
in
quite
quite
a
good
bunch
of
contact
content
here,
some
of
the
things
yeah
so
I,
at
least
for
our
Google
summer
of
code
Stu
for
the
git
love
gitlab,
plug-in
modernization.
This
testing
page
is
quite
useful
already,
showing
them
hey
here's
how
you
can
use
the
Jenkins
test,
harness
and
here's
how
you
can
use,
do
pipeline
tests
and
here's
how
you
can
test
now.
B
What
it
doesn't
have
here
is
config,
oh
no,
it
yeah
it
does
not
have
configuration
as
code
tests,
but
it
does
have
configuration
round
trip.
So
some
of
the
some
of
the
really
cool
kind
of
testing
techniques
that
are
in
Jenkins
already
are
described
here
and
so
and
I
think
for
our
gsoc
students.
It
may
help
our
gstoc
participants.
B
Okay
thanks
everybody
I'm
gonna,
call
us
to
an
end
today,
I'm
a
little
weary
and
so
we're
gonna
call
it
a
good
one
I'll.
If,
if
you
don't
see
me
next
week,
it's
because
I
was
visiting
cdcon
in
Vancouver,
Canada
I'll,
be
there
Monday
and
Tuesday
back
in
the
office
Wednesday
and
we'll
we'll
see
how
things
go
from
there.
Terrific.