►
From YouTube: 2023 03 09 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
All
right
welcome
to
Jenkins
documentation,
office
hours
today
is
March
9th,
and
this
is
the
EU
US
edition
with
me.
Today
we
have
Mark
White
and
Bruno
Brockton.
Thank
you
for
joining
us.
Always
I
appreciate
it.
Today
on
the
agenda.
We
have
some
action
items,
there's
a
couple:
pull
requests
to
review,
but
nothing
too
urgent.
We
have
a
few
blog
posts
that
have
been
published
one
by
Bruno
about
the
mini
Jenkins
control
controller
that
he
made.
A
There's
the
atlassian
sponsorship
blog
post,
that
Mark
has
written
and
we
have
the
Jenkins
Awards.
Our
the
voting
period
is
now
open
and
the
Jenkins
February
newsletter,
which
is
now
published
on
the
blog
I,
just
need
to
update
the
link
here.
A
Talk
this
we'll
have
a
short
talk
about
moving
the
docs
office
hours
time
to
potentially
earlier
in
the
day.
Just
a
quick
note
on
the
LTS
release
this
week,
weekly
change
log
will
be
reviewed,
documentation,
transition
from
java
11
to
Java
17
with
Debian
12.
This
is
something
we've
been
talking
about
for
a
handful
of
sessions
now
improving
the
end
of
life
notifications.
This
is
something
that
we've
discussed
in
the
last
two
meetings
or
so
and
we'll
revisit
again
today,
prep
for
the
sentos
7
end
of
life.
A
This
is
something
again
that
we've
been
discussing
for
the
last
handful
of
weeks
and
we'll
just
touch
base
on
that,
and
if
we
have
time
or
if
there
are
any
other
questions,
we
can
also
go
into
a
quick
10
minute.
Intro
Jenkins
got
I
think
this
was
a
Remnant
from
the
Asia
docs
office
hours
meeting
previously,
so
I'll
remove
it
for
now.
But
if
we
want
to
take
a
look,
we
can
put
it
back
on
there.
A
Is
there
anything
else
that
I've
missed
or
anything
else
you
want
to
make
sure
is
on
the
agenda
today:
nope.
Okay,
all
right!
So
there
have
been
a
couple
of
plug
pull
requests
lately,
just
from
new
contributors,
adding
a
lot
of
content.
A
It's
somewhat
challenging
and
it's
it's
a
lot
and
they've
done
a
lot
of
work
to
push
this
through
and
submit
it
I'm
doing
my
best
to
get
through
them
and
verify,
but
I'm
still
learning
a
lot
about
Jenkins,
so
sometimes
I
need
a
little
assistance
and
help,
but
that's
why
we
have
a
full
team
and
that's
why
we're
all
working
on
this
together.
A
The
first
blog
post
that
I
wanted
to
highlight
is
again
Bruno's,
blog
post,
that
he
contributed
about
the
mini
Jenkins
instant
that
he
created.
This
is
really
cool.
This
is
something
that
he
brought
to
Boston
as
well,
so
I
was
able
to
show
it
off
to
the
attendees,
which
is
really
neat
Bruno.
Do
you
want
to
speak
to
it
for
a
second
or
give
us
a
little
Insight
here,
yeah.
B
We'll
try
to
equate,
because
we
won't
get
me
started
on
this
contraption.
It's
just
a
Jenkins
instance.
By
instance.
I
don't
mean
to
Cluster
it's
just
three
agents
and
a
controller,
all
of
them
being
screwed
to
strength
things
which
is
3D
printed
and
one
of
agents
isn't
on
32-bit
another
one
is
an
arm
64
bits
and
the
last
one
is
a
risk
5..
That
was
just
an
experiment,
because
risk
5
is
not
a
platform
which
is
officially
supported
by
Jenkins
and
even
not
by
Tamarind,
which
we
use.
B
So
all
of
this
is
very
experimental,
but
I
had
tons
of
fun,
designing
the
3D
thingy
and
install
Linux
on
the
various
boards
and
use
some
Pine
64
power
supply
and
so
on
and
had
tons
of
fun
talking
about
that
at
the
first
time,
Jenkins
boost,
so
all
of
that
I
had
way
too
much
fun
with
this
project
and
it's
not
finished
yet.
I
still
have
to
add
some
displays
and
yeah
lots
of
things.
B
So
I
also
have
YouTube
channel
where
I
do
regular
live
streams
on
this
thing
and
I
write
some
blog
posts
from
time
to
time
and
so
on.
Anyway.
It's
not
finished,
it's
still
in
the
making
until
work
in
progress,
but
I
learned
some
things
about
Jenkins
Tamarind
risk
Farm
other
than
tons
of
things.
So
that's
the
beauty
of
it.
I'm
growing
with
that
small
project.
A
This
is
really
cool
Bruno.
Thank
you.
So
much
I
appreciate
it
and
I
just
I
love
the
fact
that
we're
pulling
back
the
curtain
a
little
bit
to
share
your
kind
of
like
what's
going
on
here
in
the
background
and
your
thoughts
on
it,
it's
really
awesome
and
I
think
is
incredibly
valuable,
even
if
it's
still
a
work
in
progress.
There's
so
much
to
learn,
like
you
said
so,.
B
Well,
thank
you
so
much
for
your
feedback
and
I
have
another
article
in
the
writing
regarding
mini
gen
once
again
and
risk
five
a
little
bit
more
information
about
my
progress
enough
thanks
a
lot
for
the
shootout.
A
Of
course
and
I'm
hoping
that
we
can
have
that
other
mini
gen,
blog
post,
published
and
on
the
site
by
tomorrow
end
of
day
we
do
have
scale
this
weekend.
That's
not
something
that's
on
the
agenda,
but
I
do
want
to
call
out
scale.
2023
is
this
weekend.
A
Mark,
Waite
and
Melissa
Tong
are
going
to
be
attending
and
be
be
representing
Jenkins
and
just
really
excited
and
looking
forward
to
the
next
couple
days
with
that,
and
the
idea
is
we'll
have
that
many
that
other
mini
gen
blog
post
up
so
that
it's
available
during
scale.
A
C
So
you
need
to
scroll
down
a
little
bit.
The
even
more
important
thing
is
the
upgrade
schedule.
Yes,
there
will
be
a
little
bit
of
downtime
while
the
Linux
Foundation
installs,
the
new
thing
interior
upgrades.
It's
a
license
upgrade
if
I
understand
correctly
and
so
the
it.
We
don't
expect
it
to
take
a
lot
of
time,
but
they
have
to
do
some
work
and
the
work
may
have
some
downtime.
A
Great
all
right,
thank
you
very
much.
Mark
appreciate
that
and
again,
thank
you
to
atlassian
for
providing
and
sponsoring
Jenkins
with
all
of
the
resources
that
do
this
is
great
and
makes
our
work
very
possible.
A
Next
item
on
the
list.
The
Jenkins
contributor
Awards
voting
is
officially
open.
Now,
as
of
just
yesterday
and
Wednesday
March,
8th
voting
is
going
to
be
available
and
open
until
March,
28th,
so
the
end
of
this
month,
and
we
have
our
list
of
awards
and
candidates
to
choose
from
all
of
these
people
are
more
than
worthy
of
these
sort
of
awards
and
even
further.
So
this
is
a
great
opportunity
to
share
our
thanks
and
gratitude
and
appreciation
for
them.
A
It's
going
to
take
place
via
a
Google
form
that
is
linked
here
in
the
blog
post.
This
is
only
for
the
Jenkins
Awards,
the
other
projects
and
the
CD
Foundation
themselves
have
a
separate
form
for
their
Awards
and
their
voting
process.
You
can
get
that
information
from
the
CD
Foundation
site
and
repository
where
their
issues
are
being
hosted.
Tecton
are
hosting
their
own
issues
and
then
everything
else
will
be
falling
under
the
continuous
delivery
Foundation.
A
If
I'm
not
mistaken,
so
they
are
the
foremost
authority
on
any
kind
of
information
or
Insight
you
need,
but
for
Jenkins
we
have
all
of
these
hosts
in
our
repository
and
the
Google
form.
A
So
nominations
closed
last
Friday
again
voting
opened
yesterday
and
will
close
on
the
28th
and
then
the
winners
will
be
announced
at
cdcon
this
year
in
May.
So
that'll
be
a
really
nice
time
to
just
look
back
at
everything
and
then
look
towards
the
future
by
sharing
our
gratitude
and
appreciation
and
thanks
to
these
people
and
the
realm
of
security
contributions
advocating
for
Jenkins,
these
are
all
hugely
important
and
we
need.
We
appreciate
and
I
want
to
just
highlight
all
the
work.
That's
done
here.
A
And
then
the
last
item
here
in
the
list
is
the
February
newsletter.
So
again,
this
did
just
go
live
not
too
long
ago,
quick
thanks
again
to
Roxanne
from
the
CD
foundation
for
creating
these
header
images
really
nice
and
make
the
newsletter
pop
a
lot
more
and
yeah.
We
have
some
highlights
from
fostom2023
if
you
haven't
seen
the
blog
post,
some
update
on
Google
summer
of
code
and
Jenkins
mentoring
in
our
participation.
A
Look
at
all
the
lovely
mentors
and
participants,
great
our
Jenkins
Awards,
again,
they're
open
to
vote
lots
of
infrastructure
updates
or
the
platform,
and
some
highlights
of
the
different
blog
posts
that
we
had
last
month
as
well.
A
Some
governance
info
and
a
bunch
of
information
about
platform
updates
and
image
container
image
updates.
So
thank
you
to
Bruno
for
all
of
that.
More
UI
ux
security
and
thanks
Kevin
for
contributing
the
security
update
this
time.
Around
really
appreciate
that
I'm
going
to
need
to
fix
that.
But
that's
okay,
but
yeah
the
federal
newsletter
is
live
now
you
can
go
check
it
out
and
see
all
the
wonderful
highlights
from
the
past
month
from
Jenkins.
A
Next,
up
on
the
agenda,
someone
something
that
Mark
and
I
have
just
been
discussing,
but
with
daylight
savings
time
in
the
US
being
a
thing
we
were
thinking
about
potentially
moving
the
doc's
office
hours
to
an
earlier
time
frame,
mainly
so
that
we
can
accommodate
everyone
appropriately.
If
this
is
be
held
later
on
in
the
day.
For
me,
that's
going
to
be
I,
don't
feel
comfortable
with
that.
That's
too
late
for
anyone
in
the
EU,
such
as
Bruno
that
might
want
to
attend.
B
Sorry,
because
of
a
daylight
savings
time
and
so
on,
so
you
say
that
you
think
of
making
it
earlier,
but
will
it
be
really
earlier
for
me
once
you
have
changed
time
because
of
their
life
savings
and
two
weeks
from
now?
Will
it
be
still
earlier
or
later?
Oh.
C
That's
a
mess,
so
so
that's
why
the
Jenkins
project
States
all
its
meeting
times
in
UTC
so
really
earlier,
because
they
are
unaffected
by
governmental
manipulation
of
times
yeah.
C
The
open,
the
open
question
is,
we
could
go
one
hour
earlier
than
the
current
meeting
time.
We
could
go
two
hours
earlier
than
the
current
meeting
time.
This
meeting
time
should
serve
us.
Those
of
us
who
attend.
There's
no
shame
in
us
saying
we
want
to
meet
an
hour
earlier
two
hours
earlier
three
hours
earlier.
Those
are
all
times
that
work
for
the
people
who
participate.
No
shame
in
us
saying
whatever,
whatever
works
for
us.
C
Yeah
but
but
the
reality
is
we
don't
have
any
california-based
or
any
West
Coast
space.
You
know
California,
Oregon
or
or
Washington
based
contributors.
We
also
don't
have
any
contributors
from
Alaska,
which
is
even
further
west
or
from
Hawaii,
which
is
really
further
west
and
and
so
I
think
it's
perfectly
fine
for
us
to
say.
Let's
pick
a
time
that
works
for
us.
A
Yeah
and
the
idea
like
Mark
said
Bruno
is
more
just
to
move
the
meeting
a
little
bit
earlier
in
general.
It's
not
specifically
because
daylight
savings
time,
it's
just
something
I
noticed
in
my
calendar
thought.
Maybe
we
could
just
avoid
all
this,
but
yeah
we'll
figure
it
out.
It's
an
open-ended
question,
nothing's
guaranteed
right
now,
so
no
worries
yeah
next
on
the
agenda.
So
this
week,
when
yesterday
we
had
LTS
version
2.387.1
release,
this
was
released
successfully.
Big,
thank
you
and
appreciation
to
everyone
that
worked
on
this.
A
This
has
been
a
lot
of
work
over
the
last
handful
of
months
and
a
lot
of
updates
and
changes
made
it
into
this
LTS
Baseline,
and
we
also
had
2.375.4
release
yesterday
as
well
as
weekly
2.394,
and
thank
you
to
the
security
team
because
they
took
the
lead
on
these
changelogs
and
getting
these
releases
out,
since
they
did
have
security
updates
to
push
through
just
super
super
thanks
for
their
work
and
help
on
all
of
these,
and
getting
these
things
put
together,
there
were
tons
of
UI
updates
notification
updates.
A
We
had
we
moved
that
we
transitioned
from
antler
2
to
antler
4,
which
is
a
lot
of
work
and
a
lot
of
just
a
lot
of
future
thought
going
into
this.
So
huge
amounts
of
work.
I
can't
stress
that
enough
and
yeah
there's
plenty
more.
You
can
check
out
the
changelog
on
on
the
Jenkins
site
and
adopt
great
guide
as
well.
There's
lots
of
stuff
to
go
through.
A
A
Got
it
good
yeah
thanks
very
much
Mark,
so
so
that'll
be
a
little
bit
more
work
than
before,
but
I'm
pretty
sure
I
can
handle
that
next
on
the
list,
the
documentation
transition
from
java
11
to
Java
17,
with
the
release
of
Debian
12.,
so
Debian
12,
AKA
Bookworm,
is
set
to
release
in
April
or
May
2023.
A
At
that
point,
in
time
we
are
going
to
transition
the
install
docs
for
Jenkins
from
java
11
to
Java
17.
job
11
is
continue
going
to
continue
to
be
supported.
That's
not
going
to
be
dropped
until
next
year
at
the
very
earliest.
So
there
is
no
stress
or
any
reason
to
worry
here.
We
just
want
to
encourage
people
to
use
Java
17
as
their
own
Baseline.
It
provides
full
functionality,
it's
fully
supported
now
and
just
it
the
end
of
life
is
going
to
happen
for
job
11..
A
So
the
sooner
we
move
towards
Java
17
the
less
concerned
people
will
have
to
have
when
it
does
come
to
that
time.
The
reason
or
go
ahead,
Mark.
C
Go
ahead,
I
was
going
to
venture
a
a
proposal
for
a
possible
change
of
idea.
Okay,
we've
framed
it
as
Debian,
12.
and
Debian
12
was
the
Catalyst
but
realistically
I
think
for
the
Jenkins
project,
doing
it
in
April
or
May.
Whether
or
not
Debian
12
releases
makes
sense
because
we
want
to
make
this
transition.
C
W12
was
the
Catalyst
I
won't
dispute
that
but
I
think
maybe
it's
time
for
us
to
say:
hey
we're
just
going
to
set
a
date
for
the
transition
we're
going
to
do
the
transition
because,
because
we
know
this
transition
is
needed,
would
that
do
any
objections
from
you,
Kevin
I
you're,
the
docs
officer.
So
this
is
me
sort
of
weighing
in
but.
A
No,
not
at
all
I
have
no
objection
to
that
whatsoever.
I
think
it's
I
mean
the
way
we've
been
talking
about
it.
Debian
12
is
kind
of
like
you
said
whether
or
not
that's
part
of
it
is
not
as
big
a
factor.
More
importantly,
moving
to
Java
17
transitioning
the
documentation
to
use
it
I
think
all
of
those
things
are
more
than
enough
reason
to
just
go
ahead
and
transition
in
regardless.
B
Oh
yeah,
of
course
it
was
I
need
time
to
find
the
unmute
button.
But
yes,
of
course
it
does
make
sense.
Of
course,
I
have
not
seen
anybody
complaining
about
Jenkins
does
not
work
with
GDK
17,
so
it
does
work.
It
does
work
for
infra.
It
works
for
CR.
It
was
just
about
everywhere.
So,
yes,
let's
go
and
move
to
GDK
17
in
the
documentation,
great.
A
Perfect
and
just
something
that
we
had
discussed
before
I
didn't
email,
Tim
Jacob
to
let
him
know
he's
aware
of
the
transition
and
totally
on
board
with
it.
So
we
have
the
release
officer,
okaying
everything
we
are
more
than
good
to
go
at
this
point,
so
it'll
just
be
a
matter
of
actually
performing
the
transition
next
up
on
the
agenda.
So
this
is
another
again.
Another
topic
we've
been
discussing
improving
the
end
of
life
notifications.
A
This
has
been
a
topic
because
we've
been
discussing
the
end
of
life
for
various
products
and
platforms.
Ubuntu
18.04
specifically
reaches
end
of
life
next
month,
so
we
are
looking
at
various
ways
to
not
only
make
this
transition
easier
but
alert
everyone
to
the
transition
itself
and
or
the
end
of
life
deprecation
whatever
you
want
to
call
it
at
that
point.
A
A
We
do
have
end
of
life.date
as
a
resource
that
contains
all
the
end
of
life,
dates
or
end
of
life
dates
for
a
lot
of
products,
if
not
most
of
them,
that
we
use
and
work
with
so
great
little
resource
there.
It's
got
an
API
that
can
be
connected
into
a
system,
so
we
can
get
some
kind
of
automation
going
on
there
potentially
in
the
future,
but
the
bottom
line
is
making
sure
that
people
are
aware
of
the
end
of
life
is
coming
and
in
a
way
that's
not
alarming.
A
We
have
been
discussing
a
Jenkins
enhancement
proposal
to
track
all
of
this,
so
discussing
various
deprecations
and
and
of
life
such
as
the
blue
ocean
container
image,
the
Cento
7
container
image,
which
we've
been
discussing
independently
of
this
and
the
Arch
Linux
agent
container.
These
are
all
a
little
bit
older
and
are
going
to
be
hitting
end
of
life
sooner
than
later.
So,
if
so,
the
idea
is
we'll
have
this
proposal.
We
can
track
all
of
that
and,
as
we
move
through,
we
can
note
down
all
the
changes
being
made
yeah.
A
C
I
think
the
next
step
is
the
Jenkins
enhancement
proposal
and
it
it
needs
to
I
think
the
challenge
will
be
expressing
in
a
way
that
it
Dr
identify
the
use
cases
and
address
actually
address
those
use
cases
with
the
proposal,
because
the
container
images
are
quite
different
in
terms
of
how
we
would
solve
them
than
an
operating
system.
Deprecation
right,
a
container
image.
C
We
could
see
a
file
on
the
file
system,
the
operating
system.
We
really
have
to
ask
questions
from
inside
Jenkins
core,
which
operating
system
are
we
on
and,
and
that
may
cause
more
more
concern
or
more
bristling
from
people
saying
hey.
Why
are
we
embedding
that
kind
of
knowledge
into
Jenkins
core?
And
the
answer
is
so
that
we
can
tell
them
that
their
operating
system
that
they're
running
on
is
end
of
life
to
the
Jenkins
project.
A
Great
and
yeah
and
I
can
imagine
that
there's
a
big
difference
between
the
container
images
and
what
they
rely
on
their
dependencies.
All
the
stuff
that
kind
of
make
them
up
are
gonna.
It's
all
gonna
be
very
different,
so
I
don't
see
it
being
a
case-by-case
situation.
C
Well
and
this,
the
agent
container
image
is
yet
another
condition
where
we
don't
the
con
the
code,
the
controller
code
doesn't
naturally
run
on
the
agent.
We
have
to
do
a
remote
call
to
execute
something
on
the
agent
and
so
finding
out
this.
Detecting
that
a
deprecated
agent
is
running
is
may
not
be
a
Jenkins
core
topic
that
may
be
a
version,
node
monitor
topic
and
that's
okay,
too.
A
Got
it
good?
Thank
you
very
much,
Mark
yeah,
all
right
and
the
last
thing
on
the
agenda,
and
this
is
going
off
the
previous
points,
but
we
have
been
discussing
preparing
for
the
Centos
7
end
of
life.
A
Mark
has
been
proposing
this
and
explaining
why
this
should
happen
sooner
than
later
for
a
little
bit
now,
everything
makes
sense.
It's
relying
on
Ancient
versions
of
things
that
we
don't
use.
A
It's
been
in
maintenance
mode
since
2020
and
the
end
of
life
is
going
to
be
happening
next
June,
it's
already
not
supported
by
various
functions
and
pieces,
and
so
it's
time
and
the
idea
that
Marcus
Mark
is
proposing
is
that
we
submitted
jet
to
actually
just
accelerate
this
end
of
life
and
get
this
to
the
point
where
we
can
say
it's
deprecated
sooner
than
later
so
did
Jeff
still
has
to
be
created,
but
it
makes
all
the
sense
in
the
world
based
on
what
Mark
shared-
and
you
know
these
are
very
old
versions.
A
C
To
not
move
forward,
yeah,
Centos,
8
or
Centos
State;
no,
it
doesn't
exist
any
longer,
but
there
are
plenty
of
red,
hat-based
red
hat,
eight
based
systems
that
are
available.
If
you
want
to
go
to
something,
that's
slightly
more
modern,
there's,
also
a
red
hat,
Basin
Red,
Hat
9
that
is
now
available
that
is
significantly
more
modern
and
and
both
of
them
are
a
better
choice
than
centos7
for.
A
Right
and
some
of
those
things
have
been
put
in
the
documentation
as
of
this
moment,
but
a
lot
more
work
needs
to
be
done
to
make
sure
that
it's
across
the
board
that'll
be
something
I
work
on
with
Mark's
guidance
and
we
get
taken
care
of
as
well.
A
So
that
covers
everything
I
had
on
the
agenda.
Does
anyone
have
anything
else
they'd
like
to
share
put
on
the
agenda?
Ask
where
mention
all
right?
Thank
you.
As
always
for
attending
and
and
joining
here
appreciate
it,
the
video
recording
will
be
available
in
24
to
48
hours
and
yeah.
Take
care
have
a
great
rest
of
your
day,
thanks,
as
always.