►
From YouTube: 2023 07 13 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
Movement,
hello
and
welcome
to
the
Jenkins
documentation
office
hours
today
is
July
13th,
and
this
is
the
EU
US
edition.
Today
we
have
myself
in
Kirkwood
Bruno's.
A
Please
enjoying
that
today,
on.
A
I
have
a
couple
blog
posts,
I
posted
that
were
published
this
week,
the
weekly
release
LTS
releases
for
upcoming
and
Future.
There
was
a
security
advisory
published
yesterday.
Google
summer
of
code
is
in
full
screen.
We
just
had
the
midterm
presentations
and
some
great
check-in
points
from
all
of
our
participants.
There.
A
The
Java
17
transition,
open,
call
requests
of
Interest
just
a
note
on
devops
World
Tour
and
note
about
the
next
two
asia.com
meetings.
They
are
canceled
Mark's
unavailable,
so
the
decision
has
been
made
to
just
not
have
those
they
have
been
removed
from
the
calendar.
So
for
anyone
watching
this
in
the
future,
anything
else
to
add
to
the
agenda
here
Mark
or
does
that
cover
things
for
you.
B
A
Oh
for
yeah.
A
Yeah
yeah,
of
course,
no
worries
and
yeah
I'll
be
hosting
it
no
matter
what
so
all
right,
then
so,
first
things.
First
of
all
the
blog
posts
we
just
posted
our
June
newsletter
at
the
beginning
of
the
week.
So
this
is
great
updates
from
June
from
the
Jenkins
teams,
thanks
to
all
of
these
Sig
leaders
for
contributing
their
updates
and
getting
this
out
out
onto
the
Vlog,
and
then
we
recently
had
an
infrastructure
outage.
A
Damian
de
Cortel
who's
part
of
the
infrastructure
team,
helped
and
manage
that
and
has
created
a
postmortem
kind
of
just
going
over
what
happened,
their
actions
to
resolve
and
background,
and
some
next
steps
for
us
to
take
as
far
as
making
code.
These
sort
of
things
don't
happen
in
the
future
or
if
they
do,
what
kind
of
actions
can
we
take
to
mitigate
that
even
better?
A
So
thanks
to
him
for
creating
this
and
writing
this
up
and
thanks
to
everyone
that
is
listed
here
for
all
of
their
help
and
assistance
in
getting
them
resolved
the
yeah.
So
it
looks
like
it
was
only
four
hours
long.
So
that's
great
in
the
grand
scheme
of
things.
Obviously,
no
downtime
this
past,
but
that's
also
a
pipe
dream
so
great
job.
A
The
weekly
release
of
2.414
for
Jenkins
has
was
released
successfully
change
log
has
been
merged
in
this
person
as
well.
The
next
LTS
is
2.401.3
and
that
will
be
released
in
two
weeks
on
July,
26th,
changelog
and
upgrade
guide
are
present
and
available
as
pull
requests
right
now,
but
we're
leaving
things
open
for
a
little
bit
just
to
make
sure
that
any
new
entries
or
any
other
backwards.
A
The
next
LTS
Baseline
discussion
has
been
started
in
the
developer
mailing
list
right
now.
The
discussion
is
between
2.413
and
2.414.
2.414
seems
to
be
the
front
runner
at
this
time.
Just
it's
got
all
the
updates
and
fixes
that
we've
had
in.
As
of
its
release,
there
haven't
been
any
issues
or
complaints,
so
things
are
looking
up
to
2.4
and
that's
that's
special.
It
happened
and
once
we
have
that
Baseline
selected
we'll
share
it
now,
there's
a
security
advisory
published
yesterday
for
plugins.
A
Specifically,
it's
not
Jenkins
score
affected,
and
just
something
to
be
aware
of
is
there
are
some
unresolved
issues
down
here
towards
the
bottom
of
the
security
advisory.
Just
be
aware
of
that,
if
you
run
into
any
issues
with
any
of
these
plugins,
there
will
be
notifications
or
a
warning
regarding
that,
and
if
anything
too,
that
they
could
be
up
for
adoption,
which
would
be
a
great
opportunity
to
step
up
and
take
that
on.
If
that's
something,
that's
really
crucial
and
needed.
A
If
they're
also
it's
just
one
last
thing:
if
there
are
any
other
issues
or
if
anything
comes
up,
if
anyone
finds
anything,
please
report
them
obviously
to
the
security
team,
the
more
we
know,
the
better.
We
can
do
to
help
fix
these
issues
before
they
get
too
fine.
So.
B
There
is,
there
is
one
item
of
note:
there
you'll
see
it
it's
on
your
screen
right
now.
There's
the
link
to
Rebuilder
plugin,
that's
about
three
quarters
of
the
way
down
the
the
list.
Rebuilder
plug-in
is
one
that
was
include
has
been
included
in
the
Jenkins
Setup
Wizard
as
a
an
optional
but
visible
plug-in.
So
when
you,
when
you
run
the
setup
wizard,
you
can
choose
to
install
the
suggested
plugins
or
you
could
take
the
alternate
path
and
choose
your
own
and
in
the
choose
your
own,
it
lists
the
rebuild
plugin.
B
B
A
Right
right,
thanks
for
adding
that
in
appreciate
the
context
mark.
Thank
you
so
much
up
next,
so
Google
summer
of
code
is
something
that's
been
going
on
now,
since
May
the
midterm
presentations
were
completed
just
last
week,
huge
thanks
to
Vandy,
jaggery,
harsh
and
ashitosh
for
presenting
and
sharing
and
all
of
their
work
on
this.
A
The
recording
is
actually
available
here
in
webinar,
and
so
it's
about
an
hour
and
40
minutes
long,
maybe
roughly
maybe
a
little
bit
shorter
than
that,
but
so
much
great
great
content,
great
Insight
and
just
a
chance
to
meet
the
participants
which
is
really
really
nice
and
and
puts
a
face
to
this,
which
is
really
lovely.
A
Lots
of
updates
lots
of
great
progresses
made.
The
midterm
evaluations
are
also
due
from
the
lead
mentors
by
tomorrow.
So
I've
had
a
chance
to
by
all
means,
make
sure
you
do
that,
but
that's
just
something
I'm
sure
everyone's
been
working
on
anyway,
so
so
under
for
Google
smart
code.
So
one
of
the
projects
is
the
docker
quick
start
project.
A
So
this
is
the
one
that
ashaposh
is
working
on
and
during
the
webinar
it
was
his
first
time
presenting
to
a
group
in
an
online
meeting
did
really
well
shared
some
really
lovely
and
really
great
Insight
to
the
project
and
what
he's
been
able
to
accomplish
this
far
and
you
can
actually
see
his
portion
right
here.
A
Mark
and
Bruno
also
submitted
some
requests
to
provide
various
updates
and
tests,
which
is
really
great.
This
is
the
idea
of
Google
summer
of
code
is
that
new
contributors
can
work
with
experienced
developers
and
experienced
contributors
to
just
build
their
own
and
get
that
get
that
put
in
the
door
and
leverage
and
understand
open
source
in
this
case,
in
our
case,
Jenkins.
A
And
then
Avanti
was
it
has
been
working
on
the
building
jenkins.io
with
alternative
tools
project,
so
they're
using
antora
and
have
a
prototype
site
that
has
been
built
in
is
displaying
a
lot
of
the
visual
updates
and
differences.
That
would
be.
That
would
exist
in
a
different
version.
A
B
A
Yeah-
and
it
looks
like
there's
also
another
one
up
there
in
the
right
hand,
corner
to
mark
So,
multiple
points
of
access,
multiple
ways
for
people
to
navigate,
but
yeah
the
documentation
site
is
working
really
well.
It's
color
coding
and
shading
things
a
little
differently
to
offset
that
better.
I
think
this
looks
a
lot
nicer
and
a
lot
cleaner
as
far
as
just
the
presentation
of
the
documentation
itself
goes,
which
is
great
and
then
I
know
that
there
are
I'm
trying
to
think
of
where
they
might
be.
B
You
click
on
one
of
the
really
long
sections
like
installing
Jenkins
over
on
the
left.
Okay,
it's
fine
and
then
do.
Let's
see
it
was
managing
Jenkins
I,
think
that
is
also
long
and
again
doesn't
look
bad
on
your
screen.
Good,
okay,
so
much
better
than
the
the
vertical
scroll
bar
that
we
get
on
the
left
today.
Very
good,
okay
and
show
me
pipeline
I
think
it
is,
is
the
other
one
yep,
okay
and
then
managing
Jenkins.
B
All
right
and
system
administration,
the
very
last,
the
second
to
last
or
third,
one
yeah,
okay
great.
So
this
is
definitely
rendering
much
better.
A
Yeah
and
I-
something
I
just
noticed
here
so
even
like
the
subsections-
are
collapsed
and
uncollapsible,
which
is
not
the
case.
Currently
you
have
to
actually
click
on
the
reverse
proxy
configuration
link
to
then
see
the
list
of
multiple
proxies,
so
this
is
this
is
great,
so
yeah
that
looks
awesome,
big
thanks
to
Vandy
for
working
on
that
and
again
all
mentors
all
of
the
org
admins
everyone.
That's
been
part
of
the
Google
summer
of
code
experience.
None
of
this
is
possible
without
you.
A
So
thank
you
to
literally
everyone
working
on
this.
It's
it's
incredible
so.
A
And
just
one
last
note
on
the
Google
summer
code,
so
jabruti
has
actually
written
a
blog
post
describing
a
lot
of
her
experiences
thus
far.
That's
actually
that
should
be
ready
to
emerge
once
she's
gotten
a
chance
to
check
my
final
review,
but
it's
minor
stuff
and
I
yeah
as
soon
as
she's
ready,
we'll
merge
that
and
get
that
published
as
well.
A
So
thanks
again,
the
transition
to
Java
using
Java
17
and
the
Jenkins
documentation
has
been
underway
for
some
time,
with
the
Debian
release
and
of
W12
and
no
longer
offering
KDK
11
for
delivering
jdk
11.
A
we've
been
I've,
been
working
on
making
sure
that
our
documentation
matches
that
and
Pro
and
uses
Java
17
as
our
examples
as
our
image
containers,
so
that
when
people
are
seeing
the
documentation,
that's
what
they're
going
to
be
encouraged
to
use
Java
17
is
fully
supported
by
Jenkins
at
this
point
in
time.
So
there's
no
reason
not
to
provides
better
and
more
testing
and
just
better
and
faster
development
environments.
Then
General
living
does
so
I've
been
able
to
go
through
the
documentation.
At
this
point,
I've
gone
through
the.
A
What
I
would
call
regular
documentation
so
things
like
the
installation,
documentation
the
pipeline
documentation
using
managing
Jenkins
those
types
of
documentation
and
have
gone
and
updated
them
accordingly.
So
far,
these
are
the
ones
that
I've
found
that
needed
updates
and
have
received
them.
Mark's
gone
through
and
verified
all
of
these
as
well,
and
has
helped
me
with
testing
and
making
sure
that
everything
is
correct
and
valid.
So
everything's
going
really
well
right.
Now,
we've
made
a
lot
of
Headway
right
now.
A
The
next
step
is
tutorial
pages
and
making
sure
those
are
all
set
and
making
sure
that
we
have
a
page
similar,
if
not
exactly
like
the
Java
8
to
Java
11
upgrade
instructions
right.
Now,
though,
that's
still
valid,
we
want
to
make
sure
that's
still
available,
but
we
do
need
one
for
the
job.
11
pajama
17
transition
as
well
I
started
working
on
that
found
some
gaps
there
and
some
things
that
we
weren't
aware
of
at
the
time.
A
Moving
on
so
a
couple
of
pull
requests
of
interest
that
we
have
open
right
now
so
as
before,
we
have
the
pull
request
from
tanu
about
administering
Jenkins
on
kubernetes
he's
added
some
more
content.
There's
a
lot
more
here.
We
just
need
some
confirmation
from
subject
matter
experts
or,
if
there's
anything
yeah,
could
you
jump.
B
To
the
bottom
of
that,
one,
because
I
wasn't
sure
that
tanush
had
made
any
changes
since
the
last
time
we
met
so
so
whoops
you're
a
little
too
far
down
now
so
out
of
whoa
right
there,
perfect,
okay,
so
two
weeks
ago
was
the
last
change.
Okay,
so
tanush
has
been,
has
not
been
active
on
the
pull
request
since
our
comments
and
Corrections
great
okay
and
and
that's
up
to
tanush.
B
A
Next
step
on
the
list,
so
Jeffrey
Chen
originally
submitted
a
full
request
for
moving
the
best
practices
page
from
the
Jenkins
Wiki
to
james.io.
So
we've
been
working
on
this
Mark's
converted
a
lot
of
it
here
and
has
put
together
our
best
practices
page.
That
we
feel
is
really
well
done
at
this
point
and
recognizing
that
best
practices
or
some
our
discussion
to
be
had
not
hard
and
fast
locked
in
play
sort
of
thing.
A
The
best
practices
page
is,
you
know
what
has
been
found
to
work
really
well
and
what
we
recommend,
and
even
if
it's,
not
one
million
percent
complete
in
that
sense.
You
know
this
where
we're
at
is,
is
really
good
and
solid,
and
we
have
a
lot
to
share.
B
A
B
We'll
scroll
up
a
little
up
just
whoa
right
there,
okay
view
changes,
view
deploy.
Okay,
so
the
deployment
doesn't
have
the
fixed
typer
link
yet
okay,
so
maybe
we
come
back
to
it
before
end
of
meeting
or
visit
it
later
I
think
it's
ready
to
merge
if
that
last
change
was
successful.
So
if
the
broken,
if
that
broken
hyperlink
is
fixed,
then
I
think
it's
at
least
better
than
nothing
and
one
more
wiki
page.
That's
been
converted
and
converted
in
a
way
that
we
think
makes
sense.
A
Absolutely
and
that
we
do
have
like
I,
have
the
preview
for
the
best
practices
page
that
we
had
right
before
that
making
change.
So
a
lot
of
free
content's
already
been
put
here,
a
lot
of
videos
that
Darren
Pope's
taking
the
time
to
record
and
make
for
us
that
just
really
does
an
amazing
job
of
helping,
explain
and
clarify
some
of
the
Jenkins,
an
open
source
ideas
that
could
be
did
it
be
stronger
for
someone
or
you
know,
just
something:
that's
a
little
bit
more
foreign.
A
This
is
great
and
yeah
once
that
fixes
all
done,
and
this
is
ready
to
deploy,
we
can
check
it
out
and
go
from
there.
A
B
No
progress
on
this
one
for
me
either
and
I
won't
have
a
chance
to
discuss
it
with
Meg
for
another
three
weeks,
because
I'll
miss
Asia
office
hours,
12
hours
from
now
and
I'll
miss
Asia
office
hours
a
week
from
now.
So
the
next
time,
Meg
and
I
will
talk,
will
be
two
weeks
from
two
weeks
and
about
12
hours.
From
now.
A
B
A
Next
up
so
devops
world
tour
this
year
is
a
little
different,
so
registration's
open
right
now
and
the
idea
behind
devops
world
this
year
is
that
it's
going
to
be
multiple
smaller
sessions
globally,
as
opposed
to
one
larger
conference
in
one
location.
The
idea
is
that
this
will
be
able
to
reach
more
and
more
people,
give
flexibility
in
terms
of
dates
and
being
able
to
connect
and
go
and
there's
going
to
be
Jenkins
representation
and
and
talks,
we're
figuring
all
that
out
still.
A
So,
nothing
really
to
note
there
yet,
but
registration
is
open.
You
can
check
out
on
the
site
what
locations
look
like
what
the
dates
are
so
New
York,
Chicago,
Silicon,
Valley,
Singapore
and
London,
so
this
is
going
to
be
really
great,
really
fun,
and
so
hopefully
this
will
make
it
a
lot
more
accessible
to
folks,
since
it
does
have
that
reach.
B
A
Then
was
it,
what
was
the
third
one
or
is
it?
Are
you
just
doing
New,
York
and
Chicago
New.
A
Nice,
that's
awesome,
exciting,
okay,
very
cool,
so
that
so
there's
plenty
to
look
forward
to
there
and
plenty
of
reason
to
go
just
to
hear.
Just
if
anything,
to
hear
Mark's
talk.
A
We
mentioned
at
the
beginning
of
the
hour
Mark
centerpie
out
of
office
for
this
evening
today,
tomorrow's
Asian
docs
office
hours
and
next
weeks
as
well.
So
the
next
meeting
for
Asia
doc's
office
hours
will
be
July
27th.
A
Okay,
and
that
covers
everything
I
had
on
the
agenda
for
today,
Mark
anything
else
to
note
or
quickly,
nothing.
A
Let's
see
if
this
now
has
the
deploy,
no,
it
does
the
deployment.