►
From YouTube: 2023 07 27 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
Good
afternoon
welcome
to
Jenkins
documentation
office
hours
today
is
July
27th.
Let
me
just
fix
that,
and
today
we
have
myself
Bruno
Brockton
and
Mark
White
joining
us
and
if
others
come,
we'll
welcome
them
in
for
the
agenda
today,
some
blog
posts
have
been
published
recently.
The
next
LTS
Baseline
discussion
has
been
started.
A
Some
just
notes
on
the
weekly
and
LTS
release
we
had
yesterday
and
Tuesday,
respectively
security
advisory
that
was
published
yesterday
as
well
just
some
notes
on
Google
summer
of
code,
the
Java
17
transition
for
the
documentation,
some
open
pull
requests
of
interest
that
we've
discussed
previously
and
finally
devops
World
Tour.
Is
there
anything
else
we
need
to
add
or
if
that.
A
For
me,
okay,
thank
you
very
much.
So,
first
things.
First
so
again,
the
blog
post,
so
traguti
has
been
participating
in
the
Google
summer
of
code
and
she's
posted
and
created
these
blog
posts
describing
and
providing
some
more
insight
into
the
probes
that
have
been
getting
worked
on
during
summer
code.
A
They
just
provide
some
nice
insight
there
and
then
we
also
have
a
full
midterm
recap
for
a
Google
summer
of
code
from
all
the
participants
here,
so
they've
got
their
own
respective
sections
and
providing
some
insight
into
what
they've
been
working
on
really
great
info,
and
this
goes
right,
along
with
the
midterm
presentation
that
they
just
had
recently,
which
you
can
find
the
recording
in
the
slides
here
next
item
on
the
list
here
is
the
next
LTS
Baseline
discussion
has
been
started
and
has
been
making
progress
in
the
developer
mailing
list
right
now.
A
2.414
is
the
front
runner.
Many
people
are
supporting
it.
Jimmy
Combs
accepted
that
as
far
as
what
we
can
use-
and
there
have
been
discussions
about
some
security
issues
or
backboards
that
need
to
be
made
into
this.
So
the
discussion
is
happening.
Alexander
Brandis
is
going
to
be
the
release
lead.
So
thanks
to
Alex
for
stepping
up
and
taking
that
on
that
role
and
the
change
login
upgrade
guide
need
to
be
created,
but
that's
something
I'll
be
working
on
in
the
coming
days.
So
that
should
be.
A
A
On
top
next
up,
so
both
the
weekly
and
LTS
release
this
week
were
security
releases,
so
the
changelog
was
published
by
the
security
team
and
they
made
sure
to
include
the
security
advisory
that
was
published
as
well.
So
this
was
published
yesterday
and
the
security
advisory
affects
both
plugins
and
Jenkins
core
itself.
So
this
is
important
to
keep
in
mind
and
be
aware
of.
A
Next,
up
again,
so
Google
summer
of
code
is
making
great
progress.
We've
reached
a
halfway
point
and
we
are
now
heading
into
the
last
half
the
second
half
of
Google
server
code,
so
figuring
out
the
the
rest
of
the
way.
What
next
steps
to
have
to
take
and
any
kind
of
pivoting
or
any
changes
that
have
are
happening,
are
all
being
done
in
the
best
interest
of
the
project
and
and
the
progress
being
made.
A
Next
up,
so
the
Java
17
transition
is
something
that
we've
been
discussing
and
working
on
for
some
time
now,
with
the
Debian
12
release
back
in
June,
open
jdk,
jdk
11
is
not
delivered
so
we've
transitioned
to
using
Java
17
and
Java
17
supported
images
in
the
documentation.
So
for
things
like
the
installation
documentation
on
Linux,
specifically
because
it
uses
Debian,
we
we've
updated
that
to
now
use
the
Java
17
and.
A
Corresponding
images
so
Eclipse
Tamarin
3.93-17
Etc,
so
this
is
happening.
This
has
been
going
on
thanks
to
everyone
for
helping
out
with
us
and
proving,
and
getting
this
really
well
taken
care
of.
We
also
have
Java
11
to
Java
17
upgrade
instructions
as
its
own
separate
page,
so
this
is
available
and
includes
a
really
nice
walkthrough
that
they're
invoke
created
for
us
that
walks
you
through
that
process
exactly.
A
Working
on
tutorials
right
now
to
get
those
updated
for
the
most
part,
it's
formatting
and
making
sure
that
everything
is
aligned,
but
at
this
time
I've
only
completed
the
building
a
Java
app
with
Maven
tutorial.
There
are
others
that
still
need
that
review
in
the
last
piece
that
we
still
that
still
needs
to
be
updated.
Is
the
Windows
installation
instructions
here.
A
The
reason
being
is
that
the
Windows
installation
instructions
are
majorly
outdated
compared
to
what
we're
using
for
the
rest
of
them.
It's
showing
Jenkins
2.263.4,
the
only
complication
I've
been
having
is
that
I
don't
have
a
Windows
machine,
so
I've
been
trying
to
use
VMware
and
other
alternate
options
to
try
and
get
it
working
I
haven't
had
too
much
trouble,
but
that
one's
a
little
bit
beyond
my
basic
skill
sets
model.
Okay,.
B
If
ever
you
want
some
help
with
that,
I
could
help
because
I
have
a
Windows
machine.
So
let
me
know
if
I
can
help.
A
A
But
okay,
I'm
still
figuring
that
one
out
we'll
see
they
have
some
alternative
options,
but
I
wasn't
aware
of
where
to
go
for
some
of
them,
so
I
have
to
follow
up
with
it
and
just
talk
to
them
about
it,
but
yeah
cool
and
then
one
of
the
other
items
that
I'm
working
on
for
the
Java
17
transition
is
also
a
blog
post.
Announcing
this.
The
transition
has
been
happening
kind
of
behind
the
scenes
and
getting
the
documentation,
updated.
A
I
want
to
make
sure
that
this
is
not
surprising,
or
you
know
alarming
to
anyone
so
I'm
working
on
that
as
we
speak
and
I'm
sourcing
through
the
Oracle
release,
notes
and
other
various
postings
blogs
pages
that
have
been
going
through
and
compare
and
contrasting
Java
17
to
11,
so
that
I
can
provide
some
good
insight
and
some
ideas
as
to
why
Java
17
is
preferred.
A
Yeah
next
up,
some
open
pull
requests
of
Interest,
so
these
are
ones
that
we
have
discussed
previously.
The
Jenkins
and
kubernetes
for
request
just
needs,
kubernetes
expertise,
review
the
scripting
and
security
page
again.
These
are
this
is
at
a
point
where
we
can
work
on
it
further,
but
it's
a
little
bit
lower
priority
at
the
moment
compared
to
other
projects
that
we're
working
on
other
tasks.
So
we
want
to
keep
that
alive.
It's
valuable
that
page
is
really
important
and
it's
coming
from
the
wiki.
A
So
it's
got
a
lot
of
information
that
is
relevant
to
Jenkins
and
how
and
just
needs
some
more
love.
A
A
Last
week
with
the
different
versions
and
different
I
guess
I'm,
trying
to
remember
what
it
was
specifically
about
I
want
to
say
it
was
one
of
the
places
where
the
Java
17
transition
hadn't
happened
yet,
but
we
know
that
it
will
need
to
be
updated
or
one
of
the
other
versions
will
need
to
be
updated
again
in
the
future.
So
Bruno
was
explaining
kind
of
how
this
would
actually
help
with
that
and
how
this
could
benefit
just
long-term
usage.
We
already
have
renovate
and
dependabot,
so
there
are
existing.
A
B
Yeah,
thank
you
giving
I
hope
it
could
help.
So
for
me,
it's
more
or
less
finished
with
the
latest
feedbacks
from
Damian.
For
example,
I
made
the
latest
adjustments
so
now
the
goal
is
to
have
people
vote,
so
we
can
know
if
we
should
merge
it
or
abandon
it,
and
I
say
that
a
few
weeks
from
now
I
don't
know
if
it's
a
regular
thing
to
do,
but
we
could
merge
it
or
close
it
in,
depending
on
the
results
of
the
votes.
A
Great,
and
is
there
anything
this
is
there?
Is
there
a
specific
comment
or
anything
on
here
that
we
should
be
voting
on?
Oh.
B
Sorry,
yes,
the
equipment
where
I
say
please
vote,
put
a
thumbs
up
or
thumbs
down.
Sorry
for
not
being
clear
with
that.
It's
earlier
in
the
Tokyo
sorry
I
was
thinking
that
it
was
done
at
the
time.
I
wrote
these
comments,
so
I
didn't
expect
more
comments
to
blur
everything
out.
Sorry
repair
that
no
worries.
It's.
B
A
Hopefully
got
it
okay
good
to
know
Bruno.
Thank
you
very
much.
Thank
you
and
then
the
last
item
I
had
on
the
agenda
for
today
is
devops
World
Tour,
so
registration's
open
right.
Now,
it's
different
from
the
last
last
time.
We've
done
it
devops
World
Tour
is
now
a
multi-date
multi-city
event.
So
this
is
more
flexible
and
a
little
bit
more
accessible
for
people
globally.
A
It's
not
all
lumped
together
in
one
location
for
a
handful
of
days
where
it
might
be
harder
for
other
people
to
reach.
So
this
is
done
in
an
effort
to
make
it
more
welcoming,
more
acceptable,
more
accessible
and
just
provide
folks
with
the
ability
to
go
to
devops.
World
Tour
in
you
know
the
backyard
if
they
feel
so
inclined,
there's
New
York,
Chicago
and
Silicon
Valley
for
the
U.S,
Singapore
and
London
are
the
international
locations
respectively.
A
There
and
Mark
is
actually
going
to
be
at
the
three
U.S
event
dates
and
giving
a
talk,
so
lots
of
reasons
to
go
and
see
everything
but
marketing,
there's
enough
reason
to
go,
see
the
Jenkins
stuff.
His
talks
called
benefit
your
business
by
contributing
to
open
source
and
essentially
just
explaining
how
continuing
to
open
the
source
really
does
help
an
impact.
The
company
and
just
what
kind
of
results
you
can
expect
from
contributing
and
utilizing
open
source
and
communities.
All.
A
B
Something
once
again,
it's
newsletter
monthly
newsletter
newsletter
time.
Sorry,
so
if
ever
you
have
a
section
on
the
document
feel
free
to
enter
your
information
whenever
you
can.
Okay,
thanks
for
your
help
and
second
time
we
talked
a
little
bit
about
gstock
I
will
try
to
be
quick
fast
and
not
to
spoil
too
much
but
I
know.
Mark
was
a
real
stakeholder
on
one
particular
function,
which
was
get
rid
of
the
bash
files.
B
You
know
so
that
we
can
only
use
Docker
compose
something
instead
of
launching
bash
files,
which
won't
work
under
Windows,
of
course,
and
we
have
a
PR
almost
ready
to
merge
that
Works
without
these
Infamous
bash
files.
So
now
for
lots
of
platforms,
we
can
already
type
Docker
compose
up
and
it
works
I'm
still
having
some
trouble
on
the
windows
for
whatever
reason,
but
we
are
investigating
so.
A
Okay,
great
good
to
know
and
if
you'd
be
able
to
share
the
link
with
me
either
like
after
our
session
after
the
office
hours
are
over.
We're
not
I'm.
Just
second
excuse
me
add
it
in
here
or
just
keep
track
of
it
in
general,
yeah.
B
Of
course,
of
course,
we'll
do
so
and
I
think
ashutosh
will
join
tomorrow
on
Asia's
doc
office
hours.
Maybe
he
will
make
a
demo
I,
don't
know
I
hope
so
we'll
see
and
we'll
have
to
discuss,
because
earlier
this
week,
I
discussed
with
Mark
about
when
and
how
should
we
integrate
ashutosh
work
into
jenkins.io
or
Jenkins
somewhere?
B
It's
not
ready
to
be
integrated
yet,
but
maybe
one
of
these
days
we
should
discuss.
Should
this
be
part
of
jenkins.io
directly?
Should
it
be
another
repo
somewhere
I,
don't
know.
A
Yeah
I
mean
that's
I,
say
I,
don't
know
what
would
be
I
mean
I
have
to
I'd
have
to
go
through
and
read
up
on
uh's
project
that
you're
working
on
this
is
part
of.
B
B
B
I
forgot,
the
name
of
what
we're
using
now
bad
boy,
but
I
think.
B
Right
spot
on
I
think
we
can
include
some
files
which
are
part
of
the
repo
for
the
time
being,
which
is
already
nice
so
that
we
could
get.
You
know
samples
code
samples
directly
taken
from
code
files.
That's
the
first
interesting
interesting
step,
but
if
ever
the
code
we
use
for
the
tutorials
was
taken
from
another
repo,
would
we
be
able
to
include
the
code
directly
into
the
Jenkins
IO
building?
A
B
Yeah
and
these
days
I'm
using
more
and
more
git
sub
gitsub
modules.
You
know
you
have
a
repo
and
then,
in
this
repo
you
declare
that
you
depend
on
another
git
repo
and
then
somehow
magically
whatever
the
remote
repo
is
updated.
Then
you
get
the
updated
version
directly
in
your
own
git
repo.
So
maybe
we
could
have
a
sub
module
to
include
azutors
to
work.
I,
don't
know
we'll
see,
sorry
being
maybe
too
technical
for
documentation,
office
hours,
just
thinking,
I.
A
Don't
know
you
can
have
audience
it's
good
to
have,
even
if,
even
if
I'm,
not
100
sure
of
what
that
entails,
it's
still
good
to
know
about
you
know
and
it
it's
it
could
affect
documentation
down.
A
lot
like
you
know
like
these
are
all
relevant,
even
even
if
it's
not
yeah,
these
are
all
relevant.
Don't
worry
about
that
partner!
Okay,
thank
you,
Kevin,
but
yeah,
no
and
I've
seen
the
work
that
Bundy
has
been
doing
on
the
alternative,
build
tools
for
Jenkins
that
I
own
looks
really
really
good.
A
I
know,
we've
shown
it
here
in
office
hours
a
couple
times,
so
it's
not
unfamiliar
but
yeah
I
mean
if
there's
multiple
ways
to
get
like
all.
This
work
put
together
or
integrated
into
jenkins.io
and
like
there
The
Works,
the
progress
being
made
so
far
is
really
awesome.
So
if
we
can
get
that
actually
integrated
fantastic,
even
if
it's
a
slower
process,
then
we'd
like
or
just
making
sure
like,
you
said,
making
sure
that
the
files
and
everything
can
be
done.
A
The
way
that
we're
intending-
and
you
know
hammering
all
those
or
finding
all
those
weird
little
inconsistencies
and
wrinkles
that
we
might
not
have
seen
so
yeah
I
can
imagine
it's
not
as
straightforward
and
as
simple
as
you
know,
you
would
dig
because
that's
how
everything
else
is,
but
no
that's
not.
It
sounds
exciting
and
I
can't
wait
to
see
what
we're
able
to
do
with
the
Google
funnel
code
projects
and
like
their
works.
A
Thanks
for
sharing
all
that,
so
that
covers
the
agenda
that
I
have
here.
Just
as
a
quick
note,
so
Mark
is
back,
you
might
have
seen
him
earlier,
but
that
means
doc's
office
hours.
Asia
will
be
back
on
for
this
evening.
So
you'll
see
him
there
outside
of
that
I
think
we're
going
to
wrap
up
here.
The
video
recording
will
be
available
in
24
to
48
hours
and
until
next
time
take
care.