►
From YouTube: 2023 08 03 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
Code,
hello
and
welcome
to
the
Jenkins
documentation
office
hours
today
is
August
3rd,
and
this
is
the
EU
US
edition.
Today
we
have
myself
Bruno,
Broxton
and
markway
and
on
our
agenda
today,
so
we
have
some
new
blog
posts
to
highlight
the
next
LTS
Baseline
the
weekly
release.
For
this
week
last
week's
weekly
and
LTS
releases,
there
was
a
security
advisory
published
last
week,
some
notes
on
Google
summer
of
code,
the
Java
17
transition
and
the
documentation
a
couple
of
pull
requests
of
interest
and
some
notes
on
devops
world
tour.
B
I
was
thinking
of
my
Infamous
PR
regarding
the
automatic
update
of
dependencies
in
the
documentation
yeah.
It.
C
A
And
I'm
gonna
go
ahead
and
put
this
first
thing
a
list:
okay,
okay,
fantastic!
Thank
you
Bruno
anything
else
to
put
on
here:
okay,
okay,
first
up
so
for
blog
posts,
so
we
actually
published
the
July
newsletter.
This
past
Monday
or
two
Tuesday
I
should
say
so
that
or
I'm
sorry
point
to
say
yesterday,
so
that's
available.
Now
this
is
great.
We
were
able
to
get
it
out
a
little
sooner
than
later
this
month.
A
So
really
nice
work
done
here
from
everyone
thanks
to
all
of
the
Sig
leaders
for
their
input
and
their
editions
and
yeah.
If
you
want
to
see
more
about
what
we
were
able
to
accomplish
in
July,
the
Jenkins
newsletter
is
available.
A
In
addition
to
that,
we
had
our
so
for
the
Google
summer
of
code.
We
just
had
our
midterm
presentation
it's
a
couple
weeks
ago,
and
there
is
a
blog
post,
just
kind
of
recapping
that
explaining
some
of
the
insights
and
work
that
our
participants
have
done
thus
far
and
where
things
are
heading.
A
A
Ultimately,
we
just
want
to
encourage
people
to
use
Java
17
if
they
feel
like
they
can
it's
just
going
to
provide
more
benefits
and
and
tools.
So
why
not
jump
start
that
the
next
LTS
Baseline?
A
So
it's
been
decided
it's
going
to
be
2.414
at
this
point,
so
2.414.1
is
currently
set
to
release
on
August
23rd
I'm
working
on
the
change
log
and
upgrade
guide
at
this
point
in
time,
drafting
it
putting
it
together
and
the
release
candidate
is
planned
to
be
available
for
August
9th.
So
one
week
from
yesterday
and
yeah,
there
still
need
to
be
some
security
back
ports
between
now
and
the
release,
but
other
than
that
it
does
look
pretty
good.
A
Most
people
have
voted
for
it
and
are
in
favor
of
it
and
yeah
the
more
I
come
there.
A
A
They
also
published
a
security
advisory
last
week,
just
to
note
that
there
are
issues
affecting
Jenkins,
core
and
plugins.
So
if
you
need
further
further
information
here,
there
is
plenty
of
insight
that
the
security
team
has
provided.
A
Next
up
so
for
Google
summer
of
code
again,
the
midterm
presentations
happened
towards
the
beginning
of
July,
so
Works
being
progressed
very
well
thanks
to
all
of
the
participants
for
their
work
and
their
efforts.
Here
they
have
presented
and
have
we
actually
recorded
that
as
part
of
the
webinar,
so
they
are
available.
You
can
check
that
out
from
these
links,
actually
not
that
one,
but.
A
And
something
that
I
wanted
to
share
is
again
just
a
preview
of
the
project,
the
building
all
jenkins.io
with
alternative
tools.
This
is
being
worked
on
by
Von,
deep
Singh,
and
this
is
the
demo
site
for
using
antora
As
for
the
jenkins.io
site
bill.
It's
got
really
good,
clean
visuals
to
it.
It's
presented
very
nicely
functionally.
It
lends
itself
to
just
a
little
bit
more
clean
navigation
and
various
other
parts
of
just
navigating
the
jenkins.io
site.
A
A
So,
instead
of
constantly
having
to
worry
about
the
documentation,
changing
and
what
version
a
user
might
be
on,
this
gives
us
the
ability
to
have
all
the
documentation
available
and
users
can
pick
and
choose
what
version
they're
on
to
get
the
corresponding
documentation,
and
that
just
makes
life
a
lot
easier
for
any
users
that
are
looking
to
get
info
for.
Maybe
a
couple
versions
older
that
they
might
be
interested
in
the
Java
11
versus
the
Java
17,
for
instance,
as
a
recent
change,
and
so
having
that
version
choice
is
huge.
A
In
regards
to
the
Java
17
transition,
so
this
is
mostly
complete.
The
only
item
that
has
not
been
completed
yet
is
the
Windows
installation
instructions.
This
has
more
to
do
with
the
fact
that
the
Jenkins
version
currently
used
in
the
screenshots
is
much
older
than
we
would
like
it
to
be,
so
this
needs
to
be
updated.
A
Accordingly,
it
does
have
a
slight
one
mention
of
java
8
in
one
of
the
folder
structures,
but
outside
of
that,
it's
really
more
just
making
sure
the
screenshots
are
up
to
date
and
relevant
to
what
people
are
doing
now.
Then,.
C
I
mean
when
we,
when
we
shoot
the
screenshots,
we'll
naturally
get
Java
17
there,
and
if
we
don't,
we
should
force
ourselves
to
do
it.
Yeah,
yeah,
absolutely
and-
and
we
should
not
take
it
in
program
files
Java,
because
that's
not
where
Eclipse
installs
theirs
anymore,
I'm
pretty
sure.
Anyway,
it's
not.
A
Gotcha
and
I'm,
currently
working
with
RIT
my
it
Department
to
figure
out
best
course
of
action
to
get
me
on
windows
so
that
I
can
get
these
screenshots
worst
case
scenario.
If
anyone
wants
to
assist
and
take
some
screenshots
feel
free,
the
Jenkins
issue
is
available,
so
on
GitHub.
You
can
see
here
what
the
work's
been
done
and
where
we've
done
gotten
to
thus
far
and
yeah
so
open
for
anyone
to
take
over
if
they
want
to,
but
I
am
working
on
that.
A
We've
also
added
an
instructions
page
for
the
Java
11
to
Java
17
transition.
Darren
Pope's
created
a
video
for
it,
so
all
makes
sense
to
include
here
and
provide
instructions
on
folks.
Upgrading
biggest
thing
here
is
not
only
upgrading
but
making
sure
that
all
installed
plugins
are
updated
as
well,
both
prior
to
and
after
the
upgrade.
This
ensures
that
the
compatibility
is
there.
A
A
Now
Mark
I
got
a
pretty
okay
idea
of
all
this.
Would
you
like
to
give
an
overview
of
this
and
and
kind
of.
C
Share
more
about
this
or
yeah,
so
I
would
like
that.
So,
if
there
are,
there
are
multiple
parts
and
pieces
to
this
proposal.
It
just
happened
to
work
well
that
it
could
all
sit
in
a
single
proposal.
The
Proposal
is
publicly
readable,
so
the
link
in
the
in
the
documentation
office
hours
agenda
will
get
people
to
this
document,
but
the
the
concept
is.
First,
let's
talk
about
Java
11,
because
Java
11
is
the
immediate
and
most
pressing
question.
C
So
the
idea
the
idea
is
Java
11
support
will
end
we're
not
changing
that,
and
since
JavaScript
11
support
will
end
we're
not
going
to
extend
the
Jenkins
projects.
Support
of
java
11
beyond
the
lifetime
of
the
Java
11
Upstream
maintainers,
it
just
doesn't
make
sense
so
Java,
11
story,
I,
think,
is
pretty
clear
there
and
Tim
Jacob
and
others
so
Kevin
you,
as
the
docs
officer,
others
have
said.
Yes,
this
seems
like
a
reasonable
plan,
so
Java
any
questions
on
Java
11
before
I
go
on
to
the
next
part
of
the
story.
I.
B
Have
a
stupid
question:
yes,
what
do
you
mean
by
what
was
written?
We
have
to
give
something
like
nine
months
of
warning,
for
users
to
transition.
What
do
you
mean
by
transition?
I
mean
people
will
just
have
to
have
for
the
controller,
I
guess
more
recent
version
of
the
jdk,
but
it
won't
change
for
their
agent
for
the
job
if
they
still
need
GDK
8
for
their
job,
they
still
can
have.
Gdk8
am
I
right.
Well,.
C
So
it
it
depends
good,
very
good
question,
so
the
transition
is
a
transition
of
control,
the
Java
virtual
machine,
that's
running
the
controller
and
the
Java
virtual
machine.
That's
running
the
agents
it
does
not
so
so
they
must
run
them
both
on
Java
17.,
but
that
does
not
prevent
them
from
using
that
Java
17
executing
agent
to
invoke
a
Java,
compiler
or
even
a
Java
6
compiler.
A
C
C
It's
affectionately
called
the
evil,
Maven
job
tag,
because
because
evil
in
the
sense
that
it
is
strongly
coupled
to
the
Java
version
that
is
executing
on
the
agent
oh
and
it
is
tightly
coupled
to
that
Java
version.
Therefore,
when
they
upgrade
their
Java
version
on
the
agent
to
Java
17,
all
of
a
sudden,
their
Maven
job
types
execute
with
Java,
17.
C
and
and
the
solution
to
that
is
stop
using
the
evil.
Maven
job
type
use
pipeline.
If
you
can't
use
pipeline
use
freestyle,
so
it's
much
much
better
to
you
to
get
off
the
maven
job
type
to
something
else,
and-
and
that
is
that
has
been
our
recommendation.
Even
since
Java
11.,
the
Java
11
transition
at
2.361
had
exactly
the
same
scenario
where
you
would
I.
I
was
running
Java
8,
but
I
had
a
maven
job
type.
C
B
Oh
I,
even
though
that
thanks
a
lot
for
the
explanation,
so
is
there
a
depreciation
warning,
something
that
will
tell
the
users
please
stop
using
the
maven
type
job
or
not
at
all.
You
know,
even
when
they
are
creating
some
new
Maven
type.
So.
C
We've
put
we've
put
disclaimers
about
12
months
ago:
I
think
it
was.
We
put
disclaimers
and
clear
statements
of
the
risk
into
the
maven
plug-in
documentation,
but
the
challenge
is
Maven.
Job
types
were,
some
are
some
of
the
oldest
job
types
in
the
Jenkins
infrastructure
in
the
Jenkins
environments
and
therefore
they're
maintainers
are
much
less
likely
to
look
at
documentation
than
anybody
else
because,
hey
it
just
works.
Why
should
I
look
at
documentation?
It
still
works
and
if
it
doesn't
work,
I
have
to
go.
Investigate
got
it.
Thank
you.
C
C
So
so
did
that
address
your
question?
Bruno!
Oh,
yes,
thank
you.
Okay,
great
Kevin,
any
questions
from
you
on
Java
11.
C
C
So
the
question
then
was:
when
should
Jenkins
support,
Java
21
and
here
what
I've
got
a
commitment
from
the
infra
team
led
by
Damian
de
portal,
is
that
they
will
provide
Java
21
infrastructure
using
Early
Access
builds
so
that
we
can
do
the
work
in
core
and
tooling
and
in
documentation
to
describe
Java
21
even
before.
Hopefully,
it's
released
in
September,
with
the
expectation
that,
by
end
of
October,
we'll
have
Java
21
support
officially
in
a
Jenkins
weekly.
C
So
any
questions
on
Java
21
now
in
terms
of
what
that
means,
I,
don't
think
we
will
change.
We
should
change
the
Jenkins
documentation
to
recommend
Java
21,
beginning
in
October
I'm,
not
ready
for
that.
Yet
we
may.
But
that's
that's
a
separate
discussion
for
me
right
now.
Getting
people
onto
Java
17
is
is
a
good
thing.
C
Okay,
so
then
the
next
next
part
of
the
story
is
Java
17
and
here
the
Java
17
thing
really.
What
we're
doing
is
preparing
with
Java
17
for
a
coming
day
when
we
drop
Java
11
support
entirely
from
Jenkins
and
Java
17
becomes
the
new
required
version
and
the
more
people
we
get
onto
Java
17
before
that
date,
the
happier
the
users
are
right,
dropping
dropping
Java,
17
support
forces
them
onto
Java
17.
I'd.
C
Rather
they
go
there
willingly
at
their
Pace
over
the
course
of
the
next
9
or
12
months,
and
then
we
drop
Java
11
support
in
a
and
that's
one.
That's
missing
actually
from
this
proposal
is:
when
does
Java
11
support
cease?
We
know
it's
well.
It
ceases
in
at
least
at
October
of
2023,
but
I
don't
have
that
assigned
to
a
version
number
Kevin
if
you'll
scroll
to
the
bottom.
Maybe
we
can
use
this
as
an
excuse
to
look
at
it
so
further
down
a
page
or
two
there's
a
list
of
releases
and
their
dates.
C
There
we
go
that
one
okay.
So
if
we
look
at
this,
it
would
likely
be
September.
4
2024,
oh
yeah.
Okay,
it's
listed
here
actually
September
4
2024,
the
462
approximately
release
is
when
Java
11
would
no
longer
be
supported.
It
will
just
you
can't
even
run
with
Java
11
at
that
point,
which
means
a
weekly
four
to
six
weeks
prior
to
that
would
be
the
one
that
would
drop
Java
11
support.
A
A
C
So
so
that's
sort
of
now
there
was
one
more
question
raised
by
Damian
de
portal
and
and
I
like
it's
good
that
people
think
okay,
we
talked
about
Job
11,
Java,
17
and
Java
21.,
but
what
about
Java
8,
exactly
Kevin's
got
it.
So
what
about
Java
eight
and
the
question
is
well,
but
wait.
A
sec
Jenkins
doesn't
support
Java
Aid,
that's
true!
Jenkins
core
does
not
support.
Java
8.
Jenkins
tooling
does
not
support
Java
8..
C
However,
we
still
have
Jenkins
infrastructure,
that's
supporting
Java
8,
because
we
don't
want
to
break
these
old
plugins
that
haven't
yet
updated
Kevin.
If
you
just
change
the
styling
from
heading
2
to
text,
you
get
the
right
right
size,
the
there
we
go
okay,
so
so
we
get
the
benefit
so
Java
8
is
still
available
from
our
infrastructure
and
the
infra
team
updates
the
versions
to
be
sure
that
their
latest
patched
versions,
because
we
don't
want
to
we
don't
want
to
be
keeping
Java
8
if
we're
not
keeping
it
current.
C
C
Well,
certainly,
all
the
all
the
incentives
are
there
that
modern,
tooling
is
much
much
better
than
the
old
tooling
on
which
they're
based,
but
they've
already
had
those
incentives
for
what
15
months
18
months,
and
so
those
incentives
weren't
enough.
So
I
think
the
next
step
for
us
is
to
look
at
in
the
advocacy
and
Outreach
Sig.
C
Should
we
make
a
key
theme
of
hacktoberfest
plug-in
modernization,
especially
for
these
older
plugins,
and
accept
that
some
of
us
who
are
willing
are
going
to
have
to
adopt
those
plugins
in
at
least
long
enough
to
modernize
them
and
release
a
modernized
version,
because
right
now,
we've
got.
We've
got
a
number
of
plugins
they're,
still
using
Java
8
on
ci.jenkins.io
and
unless
we
significantly
reduce
that
number,
it's
difficult
to
say.
Oh
we'll
accept
that
we're
just
going
to
break
Builds
on
ci.jenkins.io
for
these
old
Java
plugins.
A
So
just
to
clarify
Mark,
so
it
really
it's
just
going
to
kind
of
keep
status
quo
for
the
time
being.
Until
we
get
to
the
point
of
saying
this
needs
to
stop
or
we
need
to
move
everyone
forward.
C
C
It
doesn't
help
us
and
an
adopter
needs
to
be
able
to
start
to
adopt
the
plug-in
from
a
place
where
it's
successfully
building,
which
means
Java
8
for
some
of
these
old
plugins
and-
and
so
let's
keep
it
at
least
until
the
point
where
the
infra
team
says
this
is
becoming
too
expensive.
We
have
to
stop.
A
I,
don't
have
any
other
questions.
You
did
a
really
nice
job
of
explaining
all
that
Mark
I'm
walking
through
everything,
and
it
looks
like
we're
in
a
good
place
to
be
for
what
the
next
steps
are
going
to
be
so
yeah.
Thank
you
very,
very
much.
A
Great,
so
next
up
so
open
pull
requests
of
Interest,
so
the
administering
Jenkins
on
kubernetes
and
scripting
and
security
page
are
ones
that
we've
discussed
previously
we're
not
going
to
go
into
them
necessarily
right
now.
I
I
would
like
to
take
the
time,
however,
to
look
at
Bruno's
pull
requests
that
we
discussed
earlier.
A
B
Yes,
the
it's
using
a
bit
Chilli
to
make
these
PRS
but
yeah
the
proof
that
it's
somehow
working
more
or
less
with
some
errors
here
and
there
I've
already
submitted
a
corrective
PR
that
has
been
merged,
but
there
are
still
some
things
to
work
on,
for
example,
I'm
using
the
latest
node
LT,
not
LTS,
the
latest
node
image
whatsoever,
and
we
have
to
see
if
it's
still
working
after
the
update
or
not
some
voices
say
it
would
be
better
to
keep
LTS
some
voices
say
no
we'd
like
to
have
the
latest
version
I'm
in
the
middle
of
the
bridge.
C
Yeah,
so
so
Damien
Damien's
point
is
valid.
He's
I
think
he's
right,
I'm
persuaded
that
he's
right
and
I'm
wrong,
so
that
one
he's
he's
he
absolutely.
We
should
stay
with
LTS
if
we
possibly
can.
B
A
Definitely
I
mean
in
I
mean
yesterday
alone:
we've
got
a
handful
merged
and
stuff
like
that.
Taken
care
of
so
definitely
is
working.
Definitely
yeah
I
mean
it's
working,
it's
done
it's
it's
done
its
job.
It's
you
know
it's
it's
getting
it
done,
and
updating
some
stuff
after
the
facts
make
sure
it's
more
accurate
sounds
like
just
kind
of
normal
work
to
be
done.
Normal
updates
to
be
had
so
I
I
mean
this
is
a
great
and
thank
you
very
much
Bruno.
This
is
yeah.
This
is
great,
that's
fantastic!
Thank
you.
A
Great
just
want
to
make
sure
thank
you
and
then
so.
Last
on
the
agenda.
I
had
is
just
again
reminder
for
devops
World
Tour
registration
is
now
open.
It's
a
different
format
this
year
than
it
has
been
in
years
prior
where
this
year,
it's
going
to
be
several
small,
smaller
dates
and
locations,
New,
York,
Chicago,
Silicon
Valley
for
the
U.S
Singapore
and
China
and
London
for
the
UK
and
so
Mark's
actually
going
to
be
giving
a
talk
at
the
New,
York,
Chicago
and
Silicon
Valley
ones.
A
Thanks
to
him
for
doing
that,
and
coming
up
with
this
talk
you
it's,
it
looks
really.
It's
he's
been
getting
a
lot
of
work
done
on
that,
so
really
excited
to
see
what
that
looks
like
and
if
I'm
not
mistaken,
so
Olivia
Lane
has
has
agreed
to
the.
A
Okay,
got
it
I,
had
it
backwards.
So
thank
you
for
clarifying
that,
but
yeah
so
registration's
open.
Now
the
idea
is
it'll.
Allow
us
to
get
to
more
folks
and
more
places
with
out
having
a
vegan
concentrated
in
one
place
in
in
like
a
few
days.
Time
span
so
a
little
different,
but
the
idea
and
the
goals
are
the
same,
so
it'll
be
interesting
to
see
how
how
it
shapes
out
but
really
exciting
right,
and
so
that
is
all
I
had
on
the
agenda
for
today.
B
A
Oh
darn,
okay,
well,
that,
let's,
let's
table
that
for
now
then
and
we'll
put
it
on
the
agenda
for
next
week-
and
we
can
do
a
demo
and
I'll
give
you
some
time
that
way.
We
don't
have
to
do
it
on
the
fly
or
anything.
I
know,
that's
not
an
issue
for
you
Bruno,
but
yeah.
If
we
can
give
you
a
little
time,
that'd
be
nice.
Thank
you,
I!
Don't
want
to
rush
through
it
and
not
give
it
the
attention
it
deserves.
A
Thank
you.
So
all
right,
I'll
make
sure
yeah
recordings,
and
here
it
will
be
available
24
to
48
hours
and
until
next
time.
Thank
you
very
much
for
coming
as
always
take
care
and
and
have
a
good
rest
of
your
day.