►
From YouTube: 2023 06 15 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
A
Hello
and
welcome
to
the
Jenkins
documentation
office
hours
today
is
June
15th,
and
this
is
the
EU
us
session.
Today
we
have
myself
Mark,
Waite
and
Bruno
Marsden
welcome
and
just
as
an
aside
thanks
to
everyone,
who's
helped
out
with
any
documentation,
Jenkins
wise
since
I've
been
out
for
the
last
month.
It's
much
appreciated.
Yeah
just
makes
me
feel
great
about
being
part
of
this
community.
A
So
thanks
today
on
the
agenda,
we
have
some
notes
about
Google
summer
of
code
and
where
it's
at
a
couple,
there
were
some
errors
in
the
previous
change
logs
that
have
been
caught
just
an
update
on
the
next
changelog
in
LTS
2.401.2.
A
There
was
a
pull
request
submitted
recently
from
James
Chen
that
needs
a
review.
Magnus
should
she'll,
be
she's
willing
to
review
I'm
back,
so
I
can
review
as
well,
and
the
web
notifications
are
now
present
in
Jenkins
core
and
will
be
as
part
of
the
LTS
release.
Next
week,
container
controller
end
of
life
going
alongside
that
container
agents
ends
of
life.
A
Whether
or
not
the
operating
systems
that
are
tested
should
be
documented
for
Jenkins
release,
which,
with
the
new
version,
documentation,
could
be
possible
and
the
main
newsletter
has
been
submitted,
as
a
draft
just
needs
to
be
reviewed
in
approved
anything
else
that
we
want
to
put
on
the
docs
office
hours
agenda
today,
or
does
that
seem
like
it
covers
everything
that
anyone
had
on
mind.
B
Is
it
about
oh,
yes,
removing
outdated
plugins
when
using
a
Docker
container
and
I
have
a
PR
which
is
still
I
guess
in
draft
regarding
the
use
of
update
CLI
in
order
to
keep
the
documentation
up
to
date?
Regarding
the
examples.
A
Okay,
do
you
know
what
I
can
actually.
A
Give
you
the
link:
okay,
perfect,
yeah
I
can
just
start
in
here
too,
as
well
bro,
so
no
problem
there
and
yeah
okay,
I'm
gonna,
get
that
link
for
that.
Let
me
just
put
that
in
there.
A
Okay,
all
right!
So
then
we'll
get
started
here.
So
first
off
Google
summer
of
code
is
in
progress.
We've
seen
some
work
being
done
on
the
projects.
Thank
you
to
the
contributors
and
participants
for
the
docker
quick
start
project.
We're
not
at
a
draft
pull
request
yet,
but
should
be.
There
just
need
a
little
bit
more
push
so
that'll
be
addressed.
A
The
buildingjenkins.io
with
alternative
tools
has
been
making
good
progress.
Vandeet
has
shared
a
Google
doc
here
that
shows
previews
for
what
the
current
and
updated
version
look
like
everything
looks
really
great
here.
It's
really
nicely
presented.
A
There
are
questions
and
concerns
about
stuff,
such
as
accessibility
for
something
like
this,
where
the
backgrounds
change
in
color
may
or
may
not
be
an
issue,
we
that's
something
that
needs
to
be
considered
and
addressed,
or
just
at
least
discussed,
and
then
various
things
like
the
admonitions
changing
to
be
more
of
a
highlight
than
kind
of
an
offset.
So
some
really
great
stuff
here
I
think
there's
a
lot
of
good
visual
updates
for
the
for
the
site
itself
and
the
UI.
A
So
that
looks
wonderful
and
some
of
the
things
that
have
come
up
and
that
we've
been
that
have
been
getting
worked
through,
so
there
have
been
suggestions
made,
as
this
is
being
prepped.
So
big
thanks
to
Gavin
Mogan
for
getting
that
first
implementation
of
the
preview
sites
put
together.
There
are
a
couple
yeah,
so
the
question
so
like
accessibility
for
the
light
blue
background
navigation
is
going
to
be
stickied
on
the
left.
Is
it
going
to
be
sticky
down
the
right?
Is
that
something
that
we
should
do?
A
Does
it?
How
does
it
work
on
other?
You
know
indoora
sites,
so
lots
of
work
still
to
be
done,
but
lots
of
progress
and
lots
of
great
topics
are
coming
up
as
a
result
of
the
progress
being
made
there
thanks
to
everyone
for
their
work
on
the
alternative,
jenkins.io
build
options,
really
exciting,
Mark
and
or
Bruno
anything
else
on
Google
summer
of
code.
Before
we
move
on
to
the
next
topic,.
A
Great,
thank
you
very
much
so
for
the
next
topic,
Mark
I'm,
just
going
to
ask
you
real
quickly
is
I
I
know
we
talked
about
these
errors
that
were
caught.
Have
these
already
been
fixed
and
resolved,
or
is
this
going
to
be
something
or
this?
These
changes?
Have
they
been
fixed
already.
C
A
Okay,
great
so
that'll
that'll
be
done.
The
2.40,
1.2
changelog
and
upgrade
guide
have
been
created,
I've
added
the
pull
request
here
in
that
link
and
also
submitted
it
to
the
issue
for
the
release.
This
this
changelog
is
different
than
normal.
Thanks
to
the
success
of
the
previous
release,
we
haven't
had
any
issues
or
anything
that
really
constitutes
a
proper
back
Port.
A
So
right
now,
130
half
people
are
very
happy
with
everything,
so
this
upcoming
changelog
is
going
to
include
the
fact
that
we
now
have
the
end
of
life
system
notifications
available
as
part
of
the
LTS.
A
A
So
I've
made
sure
to
include
that
as
one
of
the
references
here
so
that
this
will
be
really
nice
and
clear
and
go
a
long
way
in
showcasing
how
much
work
has
been
done
with
that
and
how
that
went
from
a
suggestion.
Just
a
couple
months
ago,
to
being
implemented
now,
which
is
great.
A
A
So
there
was
also
a
new
pull
request
submitted
recently.
This
isn't
necessarily
new,
as
it
has
been
a
few
weeks
now,
but
several
suggestions
to
update
the
UI
and
just
changes
to
things
like
font
text
still
means
a
lot
of
review
and
some
work
done
on
it.
As
we
said,
name,
McRoberts
has
been
reviewing
and
working
on
it
and
providing
suggestions.
Now
that
I'm
back
and
available
I
will
be
able
to
review
and
provide
feedback
as
well.
A
C
Signs
at
least
yeah,
so
Kevin
there,
the
complication
on
that
one
is
the
content.
That's
been
provided
in.
A
number
of
cases
is
already
already
exists,
Elsewhere
on
the
site,
and
so
we
don't
want
to
duplicate
it.
C
The
that's
that's
one
of
the
challenges
of
bringing
content
from
the
wiki
into
the
wiki
that
has
not
been
maintained,
modified
or
updated
in
many
years
into
the
currently
active
Jenkins
iocyte,
because
because
there
are
many
times
when
that
material
already
has
a
better
home
somewhere
else
and
the
challenge
for
this
kind
of
pull
request
is
finding
those
Better
Homes
and
putting
the
content
in
those
Better
Homes.
So
it's
it's
not
that
Jeffrey's
work
is
not
appreciated.
C
It's
very
much
appreciated,
but
rather
it
requires
a
lot
more
work
than
probably
Jeffrey's
ready
to
do,
and
so
someone
who
really
understands
the
site
and
how
it's
laid
out
can
recommend
this
piece
goes
here.
This
piece
should
be
deleted.
Etc
this
piece
should
be
rephrased,
so
your
review
and
Meg's
review
are
both
very
valuable.
A
Great
thanks
for
just
clarifying
that
a
bit
more
Mark
I
really
appreciate
that
I
definitely
can
see
where
that
would
be
a
difficult
task
for
someone
to
take
on
if
they're,
not
as
familiar
with
one
versus
the
other
or
just
kind
of
coming
from
one
to
the
other.
There's
a
lot
of
places
where
that
information
can
go.
A
Like
you
said
you
know,
I've
been
working
in
the
Jenkins
documentation
since
I
started
with
cloudbase
a
year
ago
and
yeah
there's
a
there's,
a
good
chance
that
there's
information
somewhere
that
we
can
go
back
and
forth
and
get
to
so
yeah
I'm
more
than
happy
and
really
really
excited
to
take
a
look
at
that
and
see
what
we
can
figure
out
in
terms
of
the
content
there.
A
Yes,
all
right,
all
right
so
moving
on
to
the
next
one
and
actually
before
you
just
thank
you
Bruno
for
also
reviewing
and
sharing
feedback.
There
appreciate
it,
something
that
we've
announced
previously,
but
just
want
to
share
again
the
end
of
life.
Notifications
are
available
in
Jenkins
core,
so
that
was
in
weekly
2.407
and
it
will
be
part
of
the
next
LTS
which
is
2.401.2.
A
So
you
can
expect
to
see
these
notifi.
These
sort
of
notifications
appear
in
your
Jenkins
instance,
and
the
idea
is
that
it
will
be
a
warning
of
sick
within
six
months
of
its
end
of
life
date.
A
We've
also
announced
some
of
the
different
OS
end
of
life
that
are
going
to
happen
for
Jenkins
and
what
alternatives
and
changes
you
can
make
ahead
of
time
to
make
sure
that
your
this
isn't
a
catching
off
guard
or
that
you
have
to
even
worry
about
it
in
the
first
place.
So
cento7
is
something
that
we've
been
discussing,
increasing
or
sorry
not
increasing,
but
bringing
to
end
of
life
sooner
than
later.
So
this
is
our
opportunity
to
say
hey
that
we
got
what
we
wanted.
A
This
side
of
life
notification
helps
facilitate
that
and
just
lets
people
know
where
they're
at-
and
this
is
just
fantastic.
This
is
something
that
again,
we
discussed
started
talking
about
a
couple
months
ago,
already
implemented
and
will
be
able
to
provide
users
with
even
more
information,
insight
and,
frankly,
control
over
their
Jenkins
instance
that
just
it
makes
everything
a
lot
easier.
B
Yeah
well
done
marked
Kevin.
Do
we
have
a
look
sometimes
at
the
Jenkins
IO
website
statistics?
Do
we
know
there's
a
has
been
a
peak
recently
on
the
blog
post
of
Mark
blog
post
I.
Don't
know
because
I
don't
see
any
information
on
community
Jenkins
IO
about
you
know,
detecting
the
fact
that
you're
running
an
outdated
OS,
so
I
don't
know
if
people
are
reading
the
article
say
oh
crap,
to
move
to
something
else,
and
everything
is
crystal
clear.
So
there
is
no
need
for
any
question
or
I.
Don't
know.
C
Yeah
so
I've
I've
not
looked
at
the
I've,
not
looked
at
the
the
statistics
for
the
the
web
page,
so
I
haven't
worried
about
it.
I
wasn't
I
wasn't
overly
concerned,
if
only
because
it
hasn't
reached
LTS
yet
and-
and
there
are
significant
portion
of
the
users
that
are
running
on
LTS,
so
I
expect
more
noise
in
two
or
three
weeks
got
it.
Thank
you
and
the
tragedy
is
this.
The
sad
part
is
that
there
are
many
times
when
users
just
ignore
our
administrative
monitors.
B
A
I,
don't
think
scary,
skull
and
crossbones
are
going
to
win
anyone
over
probably
effective,
but
yeah,
not
in
the
way.
We
wanted
to
drive
away
cool
all
right,
well,
yeah.
Thank
you,
Mark,
for
getting
all
that
kind
of
sorted
and
taken
care
of
implemented.
That's
really
fantastic
and
yeah.
Alongside
that
again,
cento7
are
already
is
already
being
displayed
as
approaching
end
of
life,
so
the
monitor
should
be
working
and
just
and
sharing
that
information,
and
that
means
the
central
seven
end
of
life
is
approaching
sooner.
A
We've
gotten
through
the
discussion
and
points
that
we
had
been
talking
about
the
last
few
months
and
where,
where
we
want
to
be
the
container
agent
of
life,
this
is
going
to
be
a
little
bit
more
involved
and
will
require
more
work
than
address
the
controller
so
to
some
examples
of
what
that
might
look
like
or
what
that's
going
to
entail
from
stuff
like
Arch
Linux,
the
versions
node
monitor
plugin
and
the
platform
labeler.
A
B
It's
sorry
for
interrupting,
but
in
the
last
platform
seek
meeting
Damien
shared
with
us
Excel
sheet
of
some
sort
with
all
the
data
from
Docker
Hub.
So
we
can
make
a
wise
decisions
because
we
have
the
numbers
now
we
know
what
kind
of
image
are
totally
ignored
and
what
are
pretty,
which
one
are
pretty
popular.
B
C
A
C
A
Thank
you,
something
that
came
up
with
the
versions
documentation
pages
is,
should
we
be
documenting
the
testing,
the
operating
system
being
used
for
testing
the
Jenkins
releases,
so
it's
not
necessarily
as
easy
to
document
with
the
current
setup
of
the
documentation
in
jenkins.io,
however,
having
the
version
documentation
available
and
that
functionality
would
allow
us
to
switch
documentation
depending
on
the
operating
system
itself,
and
therefore
texting
can
reflect
that
specifically
as
opposed
to
a
more
General
sense
of
it,
and
this
would
just
give
users
the
confidence
in
what
they're
doing
is
safe
and
secure
and
has
been
vetted
by
our
team,
and
we
can
even
include
further
versions
like
the
job
versions.
A
We
already
have
a
lot
of
testing
in
place,
but
if
that
could
be
even
expanded
or
just
put
out
there
and
documented
clearly
for
everyone
that
much
better
for
the
user.
Experience
that
much
better
for
upgrading
Jenkins
going
on
to
the
next
release.
The
next
version,
the
next
LTS,
whatever
it
might
be,
if
you're
a
weekly
user,
so
that
just
gives
that
much
more
confidence
to
that
to
the
user
base
foreign
next.
So
again,
the
mail
newsletter
was
submitted.
A
Yesterday
so
I'll
be
reviewing
that
today
and
hopefully
we
can
get
that
published
before
the
end
of
the
week.
Bruno
has
also
submitted
another
blog
about
removing
updated
plugins
while
using
Docker,
so
that
that
also
needs
another
review
and
then
the
as
Bruno
was
saying
at
the
beginning.
There's
a
draft
PR
regarding
the
use
of
updates,
yeah
CLI.
B
Yeah,
thank
you.
The
thing
is,
we
already
are
using
renovo
I
think
so,
as
v-neck
asks.
Why
would
you
use
a
bit
CLI
instead
of
winova
boat
and
the
only
valid
answer
I
got?
Is
that
I
know
just
a
little
bit
more
about
a
dirty
line
than
I
know
about
Renova,
but
I?
Don't
know
renewable
at
all,
but
I'm
a
newcomer
with
ability
line.
B
So
that's
why
and
it
kind
of
works
for
what
I
propose
kind
of,
because
there
are
still
some
bugs
which
all
linked
to
the
way,
for
example,
Ruby
proposes,
creates
its
release
on
GitHub
or
the
way
that
updating
light
treats
what
is
perceived
as
a
release
on
GitHub
by
Ruby
whatever.
So
it's
not
a
PR
that
I
hope
to
be
merged
quite
fast,
but
it's
a
discussion,
an
ongoing
discussion
and
maybe
one
day
we'll
see
it
work,
but
no
rush.
A
Thanks
for
the
thanks
for
the
background,
Bruno
I
appreciate
it
and
I
I
think
it's
great.
If
it's
a
it's
a
bit
of
a
good
discussion,
we're
having
the
communities
engaging,
there's
good
back
and
forth
and
we're
getting
things
from
it.
I
think
it's!
You
know
more
than
okay
to
just
leave
these
things
open
without
merging
them.
Have
that
discussion
make
sure
that
everyone
is
heard
so
yeah
good
great
to
know.
Thank
you
very,
very
much.
A
Okay,
that
covers
everything
that
I
had
on
the
agenda
today.
Is
there
anything
anyone
else
wanted
to
add,
share.
A
C
A
And
it's
already
enabled
so
great
fantastic.
Okay,
then
so
that
takes
care
of
everything
for
today
then
I'll
go
ahead
and
stop
the
video
recording
video
will
be
posted
in
24
48,
Hours
yeah
thanks
everyone
again
for
joining
and
I
appreciate
it.
Thank
you.