►
From YouTube: 2023 08 24 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
Okay,
hello
and
welcome
to
the
Jenkins
documentation
office
hours
today
is
August
24th,
and
this
is
the
EU
US
edition.
Today
we
have
myself
Bruno,
Brockton
and
Kristen
joining
us
if
Mark
shows
up
welcome
him.
Otherwise,
let's
take
his
name
off
the
list
for
right
now,
but
I
have
a
suspicion.
He'll
be
joining
us
today
on
the
agenda,
so
some
updates
on
the
Google
summer
of
code
Chris
has
volunteered
to
provide
a
demo
of
the
version.
A
Doc
site,
which
is
one
of
the
projects
that
Vandy
has
been
working
on.
Chris,
has
been
mentoring,
so
we'll
look
forward
to
that
some
blog
posts
that
were
published
recently.
We
had
our
newest
our
latest
LTS
release
yesterday
and
weekly
on
Tuesday
the
process
of
choosing
a
plug-in
bomb.
A
A
Is
there
anything
else
that
we
should
add
to
the
agenda
or
anything
else.
Anyone
would
like
to
discuss
today.
A
Okay,
great
cool,
so
as
far
as
they
don't
know
so
Google
summer
code,
starting
off
with
would
would
you
like
to
do
a
demo
of
the
doc
site,
or
would
we
rather
like
to
come
back
to
that
we
can
discuss
other
things.
First,.
B
Can
we
discuss
other
things?
First,
yeah
yeah,
my
system
is
lagging
I,
think
I
will
reboot
it
and
then
I'll
join
back
yeah
yeah.
A
No
worries
thanks
appreciate
it
I'll
just
stick
it
down
here
for
now,
so
that
it's
out
of
the
way
cool
all
right.
So
let
Gandhi
fix
his
thing,
cool,
so
moving
on
then
so
for
the
blog
post
that
we
recently
published.
So
we
have
the
Linux
containers.
We
need
to
be
rebuilt
recently.
So
this
is
something
that
Damien
and
Mark
worked
on.
Mark
had
had
written
this
blog
post,
announcing
it
and
kind
of
just
sharing
what
happened
and
what
we
did.
A
We
also
had
a
nice
blog
post
from
Andrea,
who
was
who
did
an
internship
with
Jenkins
security
over
the
summer,
and
this
is
a
really
nice
insight
and
recap
of
his
experience.
His
internship
and
you
know
what
things
they
worked
on
learned
it's
like
got
from
it
and
what
he
was
able
to
accomplish,
but
really
nice
insights
here,
real
thanks
so
much
to
Andrea,
Kevin
and
wadik.
For
all.
A
You
know
helping
with
the
internship
participating
in
the
internship
being
such
great
mentors
for
the
internship
Etc.
This
is
impossible
without
the
teamwork
there
and
then.
Finally,
the
last
blog
post
that
we've
published
is
actually
an
update
from
another
one
of
our
Google
summer
of
code.
Participants
from
this
is
from
harsh
in
he
was
part
of
the
gitlab
plug-in
modernization
project
and
again,
a
really
nice
recap
of
the
project.
A
What
things
they
accomplished,
what
things
they
worked
on
goals
and
the
just
their
experience
overall
and
we'll
have
more
of
these
coming
shortly
with
the
Google
summer
code
heading
into
its
final
stretch
and
other
participants.
Kind
of
getting
to
the
wrapping
up
point
of
their
projects
will
be,
though,
they're
submitting
their
blogs
and
they'll
be
published.
Yeah
mark.
C
So
it's
worth
noting
that
we
should
expect
a
blog
post
from
each
of
the
Google
summer
of
code
contributors,
including
vandeed,
because
part
of
the
submission
packet
to
Google.
It
requires
a
summary
of
their
work
and
the
blog
post
is
and
has
been
repeatedly
preferred
as
the
way
to
summarize
the
work.
It
lets
them
point
to
link
to
pull
requests,
link
to
demos
link
to
the
video
of
the
midterm
presentation.
All
those
things
are
very
helpful.
A
Great
thanks
very
much
Mark
yeah
and
I
I
truly
appreciate
just
getting
a
chance
to
read
through
the
blog
posts
and
learn
about
their
experiences
and
what
what
kind
of
progress
and
like
work
they've
been
able
to
do
on
these
projects
because
from
a
documentation,
standpoint
I,
don't
necessarily
get
as
much
in-depth
experience
with
some
of
these.
But
it's
really
great
to
just
see
that
come
across.
So.
A
Okay,
next
up
on
the
agenda,
so
LTS
2.414.1
released
yesterday,
so
our
new
Baseline
has
released
change.
Login
upgrade
guide
are
available
and
thanks
to
Daniel
Beck
for
helping
clarify
protocol
for
the
security
entries,
there
was
one
that
was
added
into
the
changelog
and
upgrade
guide
that
had
been
released
in
a
previous
LTS
but
still
noted
here.
So
there's
a
little
bit
of
determination
needed
to
be
happening
and
make
sure
we're
putting
the
right
information
in.
A
A
A
I'm,
sorry
mark,
would
you
be
able
to
speak
a
little
bit.
C
Sorry
picking
up
here
so
choosing
a
plug-in
bill
of
materials
version
yeah,
okay,
yeah,
so
the
the
story
there
is
we've
got
before
before
I
left
on
vacation.
We
had
a
good
conversation
with
the
one
of
the
developers,
a
plug-in
developer,
who
said:
hey
I,
don't
know
how
to
choose
which
release
of
the
plug-in
bill
of
materials.
C
I
should
insert
into
my
pom
file,
because
they're
sort
of
a
mix
of
all
I've
got
to
combine
two
or
three
different
data
sources
to
get
the
answer
which
one
should
I
include
and
the
the
person
is
exactly
correct.
It's
it's
more
complicated
because
the
plug-in
bill
of
materials
supports
multiple
Jenkins
versions
concurrently,
but
it
can
only
release
a
single
thing
at
a
time
and
so
that
that
combination
of
multiple
Jenkins
versions,
but
releasing
one
one
ver
one
bomb
at
a
time
means
oh
I,
have
to
look
at
things
differently.
C
So
we've
got
some
more
work
to
do
here
to
describe
the
to
give
a
better
description
and
if
you
scroll
further
down
Joseph
Peterson
gives
one
suggestion
right
at
the
top
here
where
he
says:
hey.
Let's
put
it
into
choosing
a
Baseline
and
then
another
user.
Another
developer
puts
in
an
additional
suggestion
that
says
yeah.
You
know
what
we
should
also
consider
this
other
location
and
they're
both
right
right.
It's
every
place.
C
We
can
describe
here's
a
good
place
to
make
this
Choice
all
the
better
and-
and
this
may
be
a
place
where
we
need
Bruno
skills
with
update
CLI
in
order
to
submit
pull
requests
that
automatically
update
the
documentation
to
say
look.
This
is
the
current
version
of
this
thing,
so
it's,
but
those
kind
of
things
are
part
of
this.
More
work
is
needed.
A
C
A
Fair
enough
that
works
okay
next
on
the
agenda,
so
the
ongoing
discussion
about
the
proposal
that
Marx
created
for
Jenkins
and
Java
11,
Java,
17
and
Java
21
support
and
where
we're
at
what
our
next
steps
look
like,
and
plans
for,
supporting
and
ending
support.
Yeah.
C
And
this
one,
this
one
needs
some
further
refinement
because
I'm
I
diagrammed
something
on
my
whiteboard
and
the
diagram
on
my
whiteboard
highlighted
a
surprising
side
effect
of
the
current
proposals
and
so
I've
got
to
bring
I've
realized.
I've
got
to
do
pictures
and
I'll
do
pictures
before
I
bring
this
proposal
to
the
broader
community
in
particular,
because
some
things
I
think
in
the
in
this
proposal
are
too
aggressive
and
I've
got
to
talk
about.
C
Why
they're,
too
aggressive
and
explain
it
to
people
and
pictorial
is
the
pictorially
is
the
way
to
explain
it
saying
look.
This
is
how
the
calendar
looks
if
we're.
If
we
do
this,
it's
it's
too
aggressive
in
this
context.
If
we,
if
we
transition
towards
that
aggressive
posture
and
in
a
year
or
two
get
to
being
that
that
good
great,
so
all
more
work
is
needed
here
and
that
work
will
be
in
the
form
of
pictorially
building.
C
An
explanation
that
I
can
share
with
the
Jenkins
developer
list
probably
will
be
a
Jenkins
enhancement
proposal,
because
it's
really
becoming
a
process
that
will
tie
us
to
the
Java
releases
every
approx
approximately
two
years.
Every
job
is
now
on
this
six
month
clock.
They
release
a
new
major
version
of
java
every
six
months
and
every
two
years
they
release
a
new
LTS.
C
D
Okay,
lately
I've
been
trying
to
write
a
blog
post
about
jdk,
21
and
Jenkins,
and
risk
five
and
I
just
noticed
that
the
paint
was
still
wet
when
it
comes
to
defining,
which
versions
of
java
Jenkins
will
support
in
the
coming
months
and
years.
So
I'll
be
very
prudent.
So
whenever
you
see
the
blog
post
PR,
please
have
a
look
at
that,
so
that.
C
You
can
correct
my
errors
and
your
description
is
right.
The
paint
is
still
wet
right.
The
the
discussions
on
this
thing
started
with
the
Jenkins
board
and
the
Jenkins
officers
we'll
now
bring
the
discussions
to
Jenkins
developers
and
the
Jenkins
user
list.
It
won't
be
a
final
decision
until
after
it's
been
through
discussion
with
the
Jenkins
developers
and
the
Jenkins
users
list
yeah.
So
we've
we've
got
a
lot
of
a
lot
of
discussion
yet,
but
it's
a
big
enough
change
that
I
think
or
it's
a
it's
an
important
enough
change.
C
A
Thanks
Mark
I
appreciate
the
insights
there
and
side
note
on
Java
21.
It
is
available
now,
as
of
yesterday
in
the
LTS
as
a
preview
preview
availability,
so
not
full
fully
there,
but
it
is
available
and
supported.
So
it
is
usable
within
jackets.
Now,
okay,
so
next
up
on
the
agenda,
Vandy
everything
working
on
your
system,
everything
good
to
go
on
your
side,
okay,
Okay
cool!
So
then
I'll
go
ahead
and
stop
sharing
my
screen.
A
If
you
want
to
go
ahead
and
pick
it
up
and
yeah
we'll
go
into
a
demo
of
the
version
doc
site
that
Vandy
has
been
working
on
during
Google
summer
of
code
and.
B
Yeah
yeah,
Yeah,
well
yeah,
so
I
think
the
things
where
I
would
like
to
start
on
would
be
the
version
documentation.
So,
starting
with
how
we
are
versioning,
will
have
a
drop
down
on
on
version
pages,
so
the
version
pages
are
user,
documentation
and
developer
documentation,
and
from
we
can
we
can
change.
We
can
change
the
versions
from
the
page
we
are
on,
maybe
if
maybe
upper
like,
if
a
person
searches
on
Google
and
he
he
comes
to
this
page
and
but
the
version
he
is
using
is
previous
ones.
B
These
are
just
for
demo
right
right
now,
but
they'll
be
LTS
versions,
previous
LTS
versions,
so
he
would
be
able
to
switch
from
here
the
on
the
about
the
version
he
is
on.
Also,
if
he
directly
wants
to
change
the
version
and
the
page
and
like
if
he
wants
to
access
the
solutions
page,
which
contains
the
Jenkins
solution,
he
can
just
go
to
Jenkins
solution
page
and
for
or
you
can
say
he
can
choose
from
here
to
change
the
change.
The
version
after
that
we
have
these
version.
B
Pages
we
have,
we
have
change,
we
have
changed
the
how
we
have
changed,
how
Solutions
Pages
look
in
comparatively
comparatively
to
jenkins.io.
B
B
So
we
have
that
in
the
in
the
UI
ux
meeting
we
have
I
I
also
I
also
say:
I
also
propose
that
we
will
be
changing
the
home
page,
we'll
create
a
home
page
which
will
be
created
with
Gatsby,
and
then
it
will,
it
will
re
and
from
there
you
can
read.
You
can
be
redirected
to
this
all
these
Pages.
B
Currently
we
are
using
the
header
and
the
nav
bar
from
the
Jenkins
IO
components,
repository
maintained
by
Gavin
Morgan,
so
we
are,
since
these
are
used
by
a
plug-in
site
and
all
that,
so
all
these
sites-
that's
currently
these
are
not
mapped
correctly.
So
that
will
be
done
by
the
end
of
the
program.
When
will
be
good
to
go
to
push
everything
into
production
and
we'll
talk
with
inter
team
about
that,
after
that,
we
we
have
changed,
we
have
changed
how
something
how
some
things
were
looking
previously.
B
Well
previously,
if
you
yeah
previously,
if
you
on
some
pages
like
if
you
go
to,
if
you
go
to
the
international
and
you
go
to
this
page
yeah
so
previously
on
pages,
which
were
in
work
in
progress,
it
was
it
there,
it
was.
There
was
a
there
was
a
warning
symbol
somewhere
there
we
can.
We
can
still
add
that,
but
it
was
not.
B
It
was
not
completely
increasing
the
user
experience,
so
I
did
not,
but
we
can
do
that,
and
the
admonitions
blocks
and
on
the
pages
will
look
like
something
like
this.
The
code
blocks
the
code
blocks
will
look
something
like
this
and
if
we
move,
if
we
move
to
some
other
Pages,
if
we
go
to
the
Community
page
where
this
is
how
this
is
how
they
participate
and
contribute
page
looks
like
so
from
here.
We
from
here
we
can,
we
we
can
go
to
other
Pages.
B
Currently,
the
main
problem
in
in
documentation
perspective
is
we
have
a
lot
of
links
that
are
not
that
are
not
working,
because
how
austruct
use
a
references,
link
or
links
to
the
other
pages
is
different
than
how
antora
does
it.
So
we
we
have
completed
a
lot.
We
have
I,
have
already
migrated
a
lot
of
pages
and
fixed
them,
but
still
we
have
we
have
to
we
have
to
test.
B
We
have
to
test
it
before
pushing
it
into
production
that
all
the
links
are
working,
because
that
will
that
will
heavily
influence
the
user
experience
of
the
people
who
use
jenkins.io
as
as
a
place
to
look
into
how
Jenkins
works.
After
that,
we,
after
that
current,
currently
the
components
are
currently
the
components
are
working
well,
really:
well,
the
the
we
the
Json
project,
section
general.io.
B
We
have
a
project
and
projects
your
projects
section,
so
the
project
section
contains
a
previous
year
Jenkins
dot
previous
year,
Google
summary
of
code
in
Jenkins,
section
I
still
have
I,
still
have
to
refactor
all
of
them
because
they
use
a
they
use.
B
The
layout
of
simple
g-soc,
page
and
G-Shock,
page
simple,
esoc
project,
page,
which
these
three
pages
are
different,
so
I
I,
I'm
working
on
that
currently
to
give
it
a
some
type
of
uniformity
in
all
pages
we-
and
if
we
go
to
the
idea
section
if
I
can
find
that
currently.
Currently,
the
sidebar
is
not
well
updated
for
the
Jenkins
project
page
because
there
are
a
lot
of
pages
and
I
need
to
I
need
to
consider
how
I
would
put
that
in
a
hierarchical
way.
B
So
like
it
does
not,
it
does
not
make
the
sidebar
very
long,
and
so
so
we
don't
have
to
scroll
somewhere.
We
don't
have
to
scroll
after
that.
After
that
we
have,
we
have.
We
have
the
accepted
idea
space.
Looking
exactly
how
it
look
looks
on
jenkins.io
I
still
have
to
add
the
images
that
I'm
I'm
I
I
I
have
added
that,
but
it
is
not
working
because
I
I
think
it
is
because
it
is
inside
it
is
inside
a
table.
B
That's
why
it
is
not
working
so
I'll
I'll
find
a
look
around
for
it,
but
these
are
working
and
the
author
profiles.
B
The
author
profiles
are
yet
to
be
created
with
Gatsby
that
won't
take
much
time
and
after
that
we
can
link
the
author
profiles
everywhere
on
on
this
site,
after
that,
if
we,
after
that,
if,
if
we
go
to
the
event
section,
we
asked
we
I'm
still
working
on,
we
are
I'm
still
working
on
fixing
the
e-card,
because
we
get
a
we
get
a
card
on
jenkins.io
I
I
saw
how
to
I
know.
I
now
know
how
it
works.
B
Where
previously
I
did
not
know,
it
uses
a
data.yml
file
to
change
the
events
that
are
listed
on
the
card.
We
have
the
event
calendar
that
that
that
was
in
integrated
with
the
with
by
Chris,
because
Ruby
is
not
something
I
can
handle
pretty
well,
so
Chris
really
helped
me
there
yeah
so
yeah.
This
was
it
if
you,
if
you
guys
have
any
question,
feel
free
to
ask
me.
B
B
C
Because
because
I
have
a
long-standing
action
item,
no
prog
very
little
progress
on
it,
but
I
have
a
long-standing
action
item
to
convert
this
thing
from
the
concept
of
projects
and
project
and
sigs
into
a
single
concept
called
working
groups.
So
so
I'm
not
overly
concerned
about
whether
or
not
the
projects
thing
renders
really
well.
We've
got
to
rework
it
in
a
major
way
to
combine
two
concepts
that
are
currently
described
on
on
the
page.
C
B
Yeah,
and
also
like
you
said,
while
I
was
doing
all
that
I
saw
that
many
many
species
and
projects
were
like
interconnected
yeah,
so
that
could,
if
we
in
future
they
try
to
do
that.
That
would
be
really
easy,
because
we'll
only
have
to
move
the
files
since
I
I'm
I'm,
currently
giving
them
a
uniformity.
So
we
only
have.
B
We
will
only
have
to
change
the
change,
move,
the
files
and
merge
content,
so
that
would
be
that
would
help
it
in
the
future,
because
currently,
if
you
see
when
I
when
I
also
miss
the
Jenkins
projects,
Jenkins
project
docs
docs,
because
I
thought
a
project
and
projects
is
just
one
thing,
but
when
I
was
checking,
I
was
double
checking
if
I
did
not
miss
anything.
That
is
not
migrated.
Yet
then
I
saw
that
oh,
my
the
project
section
is
still
to
be
migrated.
C
C
B
That
could
be
yeah
this
one
this
this.
These
two
really
confused
me
too:
okay,
yeah,
so
yeah.
So
that's
how
we
can
change
the
version
when
that
all
that
the
version
things
are
solution,
page
tutorials
and
user
documentation,
because
the
advisories
The
Advisory
is
a
single
page
generator
via
ml
generated
single
page
like
it
contains
the
change
logs,
which
is
which
is
a
yml
generated
single
page.
So
we'll
we'll
do
that
with
Gatsby,
because
since
it
is
yml
generated,
I,
don't
think
so.
B
C
Vandy,
so
could
you
take
us
back
to
the
top
level
so
on
the
here
on
the
solutions
pages
that
one
should
that
be
version,
so
this
I
understand
if
I
understand
correctly,
is
versioned
and
I
guess
this
is
a
question
to
Kevin
and
to
to
Bruno
more
than
to
more
than
to
anybody
else,
it's
Solutions
seem
like
yeah.
Maybe
they
should
be
versioned,
but
then
again
it's
not
a
hot
high
speed
fast
changing
thing,
but
they
could
be
very
different
between
Jenkins
2.400
and
Jenkins
2.600.
B
Yeah,
like
I,
see
what
I
see
I
see
what
you're
trying
to
convey
I
I
made
them
version,
because
if
we
have
some
solution,
if
we,
if
we
think
of
it
as
a
standpoint
that
someone
wants
to
see
if
Jenkins
is
something
they
can
use
for
their
project
or
their
their
needs,
so
they
can
visit
the
solution
page
and
check
out
the
AI.
It
is
integrated
with
this.
I
can
use
it
from
that
point
of
view.
I
should
not
be
version.
B
I
made
it
versions
version
because
I
thought
and
I
like
I,
just
got
to
realize
that
I
thought
yeah.
Since
on
the
version
we
can,
you
can
like
a
person,
will
a
person
can
see
if
a
solution
related
to
his
problem,
like
his
need
is
version,
is,
in
this
version
or
not,
but
yeah
I,
I
I,
think
if,
from
both
of
these
povs
I
I
think
we
can
it
could
it
should
not
be
version.
I
can
I
can
change
that.
D
I
would
say
version,
but
maybe
not
linked
to
the
version
of
Jenkins.
That's
what.
B
D
Be
difficult
for
me
to
to
Joe,
you
know:
when
should
we
create
a
new
version
of
this
I?
Don't
have
the
answer
well,.
C
A
I
guess
are
the
solution
Pages
intended
to
be
something
as
a
general
statement
for
something
like
Android
or
PHP,
or
is
it
intended
to
be
more
specific
and
where
that
version
of
Jenkins
really
comes
into
play
or
I?
Guess
it
like
in
terms
of
one
of
these
exam
like
python,
for
example?
A
C
There
there
isn't,
and
mostly
that's
because
no
one's
taken,
the
time
to
revise
the
solutions,
pages
and-
and
so
I-
think
for
me
that
that
is
a
problem.
I
would
love
to
have,
but
we
don't
have
but
I
think
we
we
can
conceive
of
how
we
would
have
it,
because
many
of
these
descriptions
won't
work
with
older
Jenkins
versions
and
so
the
descriptions
that
talk
about,
let's
say
Jenkins
and
Ruby.
C
If
it
makes
the
mistake
of
talking
about
Jenkins
plugins
implemented
with
Ruby
that
no
longer
works,
and
so
that
would
be
version
specific
now,
I,
don't
think
it
does
right.
These
are
just
plugins
that
can
help
a
ruby
developer
and
so
they're
they're
they're
they're
perfectly
fine.
But
we
had
a
period
where
you
could
actually
write
plugins
in
Ruby
or
write
plugins
in
Python
and
we've
taken
that
capability
away
because
it
was
impossible
to
maintain.
D
Go
ahead.
Sorry,
go
ahead;
no
no
go
ahead!
I'm
done!
Oh
okay!
I
was
thinking
of
dependencies
outside
of
the
Jenkins
ecosystem,
unfortunately,
for
the
versions
of
the
Android
solution,
for
example,
when
we
had
new
features
in
Docker
that
help
us
with
Android
and
but
also
it's
somehow
tied
to
some
of
the
plug-in
version
that
we
use
for
Android,
for
example,
I'm
thinking
of
the
docker
plugin.
So
it's
not
directly
linked
to
the
version
of
Jenkins,
but
more
of
external
dependencies
or
Plugin
that
we
use
in
the
Jenkins
ecosystem.
C
Fact
well,
but
but
that
one
might
have
a
fun
answer
in
that
we
might
consider
backing
some
of
these
Solutions
with
a
plugins.txt
file
and
a
container
image.
That
says,
because
we
think
we're
going
to
do
that
with
Asher
Tasha's
exam
with
ashitas's
tutorials
right,
where
we
will
have
versioned
can
container
images
that
represent
a
point
in
time.
So
maybe
maybe
this
would
be
a
similar
thing
where
hey.
If
you'd
like
to
see
this
at
that
point
in
time,
here's
the
current
one
and
you
could
go
back
in
its
history.
D
C
Yeah
I
I,
at
least
now,
so
as
our
my
model
in
lobbying
for
that
was
command
line.
Git
has
versions
for
every
every
version
of
git.
That
is
a
every
minor
version
and
they
only
do
minor
versions
every
three
months,
so
they
get
about
four
a
year
that
they
do
and
that's
all
that
they
update,
update
their
documentation
site
typically
on.
D
B
I
I
need
to
go
somewhere.
Can
I
drop
the
call
right
now
if
I
am
not
needed.
A
A
What
a
lovely
demo,
so
that's
great,
really
excited
looking
forward
to
that.
We
are
coming
up
against
time
in
that
time.
If
anything,
so
is
there
any
so
on
the
agenda?
We
still
have
the
additional
platform
information
section
that
I'm
working
on
and
a
couple
mentions
of
val.sh,
which
I
just
started
reading
about
today
in
devops
World
War.
Is
there
anything
on
here
that
anyone
wants
to
discuss
in
depth
or
talk
about
further
right
now.
C
A
Yeah
I
started
reading
up
on
it
after
I
saw
it
in
the
agenda,
so
I'm
actually
very
curious.
I
want
to
find
out
more
thanks,
Mark
great
all
right,
then
we'll
end
the
meeting
here
and
then
until
next
time,
but
the
video
will
be
available
in
24
to
48
hours
and
until
next
time
take
care
thanks
for
joining
and
have
a
good
day
rest
your
day.