►
From YouTube: 2023 01 12 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).
B
Welcome
to
the
Jenkins
documentation
office
hours
today
is
January
12
2023..
Today
we
have
myself
Mark,
Waite
and
Bruno
marsman
joining
us.
Thank
you
all
for
being
here
today
on
the
agenda,
a
couple
things
in
the
action
items,
one
we
have
archive
the
docs
knowing
list
so
just
a
quick
update
on
that
blog
posts.
We
have
an
update
on
Debian
12
and
what
it
will
deliver
and
Mark.
Would
you
be
able
to
share
more
about
that
or.
A
Sure
yeah,
this
is
one
that
Bruno
and
I
will
probably
talk
as
well
about
in
the
platform
Sig
meeting,
but
it
has
a
documentation
impact,
so
I
discovered
just
yesterday
that
the
next
release
of
Debian,
scheduled
for
2023
will
not
include
open,
jdk
11
at
all.
Okay,
the
package
won't
be
available
in
it,
they're
offering
Java
17,
which
means
they're,
really
preparing,
also
I'm
sure,
once
Java
21
is
available,
they
will
include
it,
but
that'll
happen
what
six
months
or
a
year
from
now,
so
their
Debian
is
correctly
saying.
Look
Java
8
is
done.
A
That
was
done
for
them
a
while
ago.
Java
11
is
really
also
done.
The
the
impact
for
us
is
that
when
they
release
in
roughly
April
of
2023,
our
Linux
install
instructions
will
have
to
be
yeah.
So
what
you
see
here
is
they
they
don't
commit
to
a
final
delivery
date.
What
they
commit
to,
though,
is
they're
currently
planned
for
March
12th
to
be
frozen.
A
Exactly
hard
freeze,
full
freeze
is
where
they
reach
the
final
release.
Usually
it's
a
month
or
more
between
hard
freeze
and
final
delivery.
So
I'm
not
expecting
this
before
April
I.
Once
they
release
it,
we
will
probably
switch
the
Jenkins
Docker
containers
to
use
this
new
version
of
Debian.
That
makes
sense,
but
users
who
are
installing
with
the
APT
package
or
who
are
using
our
default
instructions,
won't
be
able
to
do
that
anymore
because
they'll
it
our
instructions,
tell
them
to
install
Java
11..
B
A
B
A
Users,
right
and
and
if
they
choose
oh
I'm,
going
to
install
Java
11
instead
of
java
17
great.
It's
just
that
about
that
time
we
switched
to
where
we
say
we're
going
to
recommend
Java
17,
not
because
that's
the
only
thing
we
support,
but
because
it's
simpler
to
give
those
instructions
in
this
case
and
we
do
fully
support
it-
got.
B
It
wonderful,
okay,
awesome!
Thank
you,
so
much
Mark
that
helps
clarify
all
that:
okay,
okay
for
the
rest
of
the
agenda
archive
website
tickets,
small
update
on
that
handling
regression,
how
we're
going
to
handle
regressions
on
the
jenkins.io
site
itself.
Some
pull
requests
of
note
from
the
community
and
just
a
small
discussion
short
discussion
about
one
of
the
the
using
agents
page
and
Jenkins.
B
B
Right,
thank
you
very
much.
Okay,
so
first
thing
on
the
list,
the
docs
mailing
list
has
been
archived
It's
Made
made
read
only
and
now
the
main
idea
is
we're
using
the
docs
Jenkins
docs
getter
for
communication.
B
B
Just
kind
of
any
ideas
here
and
community.jenkins.io
will
be
the
second
location,
and
this
is
going
to
be
for
more
in-depth
and
involved
conversations
if
there
needs
to
be
research,
work
done
anything
that
is
more
than
you
know.
A
short
conversation
would
be
best
had
here,
and
the
nice
thing
about
having
it
on
community.jenkins.io
is
that
it's
available
for
everyone
to
see
much
easier.
Everyone,
not
everyone,
might
be
using
gitter
or
the
chat,
but
if
they
have
an
account,
they
have
the
ability
to
see
community.
B
So
let's
do
another
good
place
to
have
it
and
we'll
make
the
transition
to
the
Future
seamless
a
couple
of
things,
a
couple
blog
posts
to
highlight
sorry.
So
today
we
just
published
our
2022
recap
newsletter
for
Jenkins,
so
huge
and
massive
thanks
to
everyone
for
their
work
on
this.
The
entire
Community
team
came
together
and
really
made
this
something
special
there's
a
lot
of
great
great
updates
on
here.
Thank
you
to
Roxanne
from
CD
foundation
for
providing
these
image
headers.
B
This
is
a
everyone's
hard
work
is
on
display
here,
and
this
is
truly
a
test
example
of
the
love
and
care
and
work
that
the
that
Jenkins
has
been
getting
for
since
for
2022..
Sorry,
by
all
means,
take
it
take
a
moment
to
look
it
over.
Read
it
we'll
be
tweeting
it
out
and
posting
about
it
online.
So
this
is
everywhere
now
and
it
will
be
even
more
places
by
the
end
of
meeting
okay.
B
And
then
a
couple
other
blog
posts
that
were
recently
published
Bruno
had
a
blog
post
recently
on
running
your
Jenkins
agent
of
service.
Again,
a
nice
tutorial
alternative
methods
of
using
your
Jenkins
agent,
great
instructions
here
and
a
really
nice
just
breakdown
by
Bruno.
B
And
the
other
one
here
is
John
Mark
missense
blog
for
the
Google
cover
up
so
Google
summer
of
code
mentorship.
We
are
getting
a
lot
of
participants,
we're
about
20
or
so
participants
already
signed
up
we're
looking
for
mentors
we're
looking
for
co-mentors
Etc.
Anyone
that
is
interested
is
more
than
welcome
to
come
on
and
sign
up
help.
You
know,
contribute
if
they
have
that
desire.
The
blog
post
here
mentions
more
about
what
mentorship
looks
like
what
it
requires.
B
B
We
did
already
talk
about
the
Debian
12
release
and
what
that
means
for
Jenkins
and
the
Jenkins
documentation
and
yeah.
Is
there
anything
else
on
that?
One
mark
that
you
want
to
mention
or.
A
No
actually
I'm
a
little
embarrassed.
You
you
asked,
should
it
be
on
the
agenda
I
wasted
the
time
describing
it
it's
done.
I
think
we
have
a.
We
have
a
good
decision.
We
will
plan
for
as
Debian
12
arrives,
there
are
going
to
be
a
bunch
of
activities
that
will
happen.
Docker
container
updates,
documentation
updates,
Etc
and,
as
part
of
that,
we'll
switch
to
Java
17
for
sure.
For
that
platform,
yeah.
B
Perfect
time
great
I'll,
be
there
no
worries.
Thank
you.
Thank
you
and
then
the
next
on
the
agenda
here.
So
we
had
a
list
of
issues
that
were
in
jira
still
that
were
assigned
with
the
website
label.
These
were
issues
relating
to
the
jenkins.io
site.
We
have
now
officially
closed
out
all
of
the
website
tickets.
Anything
that
was
irrelevant
at
this
point
in
time,
since
there
were
some
from
2017
and
earlier
to
the
ones
that
have
come
in
recently
have
been
migrated.
B
B
B
A
Yeah
you've
got
to
open.
You've
got
to
open
those
two,
because
those
two
are
yeah
are
somewhat
sources
of
Shame.
Okay,
this
is
the
mark.
The
first
one
is
the
mark
weight
source
of
Shame
okay.
So
so
what
we
see
here
is
the
Jenkins,
what
we
call
the
Jumbotron.
It's
the
this
thing
that
rotates
down
at
the
bottom
of
the
Big
Orange
block.
However,
it
stopped
rotating,
apparently
in
November,
late
November
of
2022
yeah.
So
so
we
regressed
the
site,
and
we
haven't
it's
taken
us
almost
eight
weeks
to
detect
this
regression.
A
So
so,
apparently
it's
and
and
thank
you,
keep
scrolling
down
Kevin,
because
it's
a
good
story,
special
thanks
to
vandit,
who
did
the
bisect
to
find
out
which
commitment
caused
the
cause.
The
thing
to
first
appear
exactly
good
job,
using
a
bisect
and
and
figuring
out
hey
this
is
it
that's.
That's
work
that
wow
none
of
us
had
to
do
so
very,
very
grateful
to
him.
Now
the
question
is
all
right:
what
do
we
do?
A
Next,
with
it
and
and
the
I
like
the
technique
that
Jenkins
core
uses
where,
if
a
detection,
if
a
regression
is
detected
in
Jenkins
core
Basel
Crow,
has
been
guiding
people,
we
will
give
a
very.
We
will
give
a
time
where
the
original
regression
is
identified
and
the
author
of
the
original
regression
is
given
a
reasonable
amount
of
time
to
either
resolve
it
or
we
revert
because
we
want
to
be
functional
right.
A
We
want,
we
want
to
retain
functionality,
and
in
this
case
the
the
embarrassing
part
for
me
was
because
it
took
us
eight
weeks
to
detect
the
regression
I
propose
that
we
need
it
fixed
within
one
or
two
weeks,
because
of
just
how
long
it
took
to
detect
it.
It
I
think
the
answer.
Is
it
can't
be
that
serious
of
a
regression?
A
If
we
didn't
get
a
bug
report
on
it
for
eight
weeks
now,
there
are
others
where,
for
example,
if
the
pipeline
steps
documentation
disappears
because
of
a
of
a
commit,
that's
an
for
me
that
one
is
critical.
Lots
of
users
depend
on
it.
We
revert
that
thing
in
24
hours
or
less
right.
We
revert
that
very
very
quickly,
so
that
was
that
was
my
thinking
on
it.
B
And
so
I
can
share
my
own
little
bit
of
Shame
here.
So
when
we
I
went
to
add
some
updated
logo
images
and
they
weren't
all
exactly
the
same
size
and.
B
Now
there
we
figure
that
out
and
again
Vandy.
Thank
you
again
for
all
of
your
work
figuring
this
out
wonderful
and
yeah,
but
this
is
something
that
is
Visual
and
functional.
To
that
end,
so
again,
is
it
affecting
users
so
much
that
this
isn't
this
needs
to
be
resolved
immediately,
reverted
immediately,
or
is
it
something
that
we
can
take
the
time
to
look
into
and
figure
out
and
understand
and
resolve?
You
know
in
due
time.
A
This
one
for
me,
is
more
severe
because
of
its
perception.
Potential
perception
by
sponsors
right
I
would
not
want
jfrog,
who
is
a
major
contributor
to
the
Jenkins
project
or
GitHub,
a
major
contributor
to
feel
that
they
were
dwarfed
by
Cloud
bees
just
because
we
we
size
the
image
wrong
so
so
that
that
was
the
my
concern
on
this
one
I
think
this
one
is
more
severe
than
the
other
one
again.
It's
it's
not
an
instantaneous.
We
must
revert
it,
but
rather
this
one
has
higher
risk
than
that.
Other
one
did.
B
Right-
and
it's
pretty
a
lot
of
that
in
this-
is
the
perspective
of
course
in
how
that
varies
from
each
issue
and
yeah,
no,
absolutely
so
Mark,
and
should
we
should
we
revert
anything
right
now
or
should
we
leave
these
be
for
the
time
being.
A
Well,
this
one
actually
has
a
proposed
fix
from
vandeed,
so
Vandy
proposed
a
fix
in
another
poll,
request:
okay,
yep
and
and
I.
Think
this
one
is
the
I
think
this
one
is
the
fix,
and
so
so,
but
I
would
prefer
to
bring
this
one
forward.
If
we
can,
if
we
can
confirm
yes,
it
really
worked
and
maybe
view
the
deployment
Kevin.
Let's
look
at
it
while
we're
here,
okay,
so
first
we
notice
that
the
the
Jumbotron
is
not
scrolling,
yep,
okay,
now
going
onwards,
so
that's
not
fixed,
so
that
looks
closer.
A
A
B
A
C
A
Well,
and-
and
that's
that's-
that's
the
nature
of
these
regressions
in
general.
Right,
no!
Shame
in
that.
That's
the
nature
of
a
regression
is,
is
oh
I
missed
something:
okay,
I
missed
it,
not
a
big
deal:
We're
Not
Gonna,
not
gonna,
worry
about
it.
Okay,
so
I
just
merged
it.
I
said
hey
approved
and
merged.
A
C
You
are
thinking
of
something
to
automate.
You
know
when
you
make
a
PR
for
Jenkins
IO,
which
would
look
at
the
images
and
propose
a
new
version
of
the
images
which
would
be
compressed
by
a
tool
whatever
and
recite
before
compressing
which
I
tend
to
forget.
You
know
that
Mark,
it's
okay.
A
B
All
right,
then,
we're
all
in
the
same
boat,
good
yeah,
so
that's
progression
handling
is
definitely
gonna
be
better
when
we
can
sit
down
and
look
at
them
and
revert
when
needed
and
address
everything
appropriately,
and
this
just
helps
us
have
those
conversations
and
discover
more
of
these
little
nuances
that
we
can.
We
can
expand
upon
and
make
things
better
by
so.
A
So
now
the
the
open
question
for
one
of
the
questions
that
was
open
for
me
was:
how
long
should
we
wait
before
we
revert,
we
talked
about
if
it's
a,
if
it's
that
somehow
it
should
be
matched
to
the
severity
of
the
problem,
any
guidance
there
on
how?
How
do
we
match
that
you
know?
Is
it
I'm
open
for
suggestions.
B
Yeah
and
is
there,
is
there
a
way
that
we
could
create
a
label?
Maybe
for
someone
to
add,
saying,
hi,
severity,
low
severity
or
something
like
that.
A
A
B
And
Bruno
Walla
Mark's
finding
knows
what
I
cut
you
off
earlier.
C
Yeah
Kevin
I
was
just
thinking
out
loud.
Would
it
be
possible
to
add
a
GitHub
action
of
some
sort
or
something
else
that
would
propose
to
revert
in
certain
amount
of
time
when
it's
tagged
with
regression
or
major
regression?
You
know,
even
if
it
doesn't
revert
by
itself,
just
I
don't
know,
put
a
comment
somewhere
saying
we
have
to
close
that
before
that
time
frame
that
you
know
am
I
making
myself
clear
enough
to
be
understood
or
not
at
all.
Yeah.
A
A
So
so
I
do
see
in
the
labels
I
see
major
bug,
major
rfe
bug
and
rfe
on
the
on
the
on
Jenkins
core
they
and
they
have
regression
Dash
fix.
A
So
maybe
we
should
maybe
we
should
adopt
the
same
thing
and
say
regret:
they're
they're,
not
using
the
Jenkins
core,
does
not
use
GitHub
issues
to
track
and
therefore
we
might
want
to
say
regression
as
a
label
and
then
regression
fix
as
a
label
to
use
their
their
labeling
as
a
way
to
tell
people
what's
happening.
What
do
you
think?
A
A
B
And
Bruno
I
like
your
idea,
a
lot
of
having
the
GitHub
action,
maybe
like
you're
saying
just
have
it
like
comment
in
the
ticket
or
something
to
say
like
hey.
This
needs
to
be
reverted
by
this
time,
because
it's
Mark
major
or
something.
A
A
A
A
A
A
B
B
Yeah,
no,
no
yeah,
of
course,
I
just
wanted
to
put
them
in
here
at
least
foreign
all
right.
We
are
coming
up
on
time,
so
I
would
like
to
just
kind
of
move
through
the
next
couple
items
here,
mostly
just
some
pull
requests
that
have
come
through
recently.
This
one
here
is
an
update
to
or
adding
the
updating,
Jenkins
section,
this
one
is
actually
also
from
Vandy.
So
thank
you
again
to
vardy
for
all
the
work.
This
is
a
lot
of
content
to
add,
update
and
review.
B
So
this
will
take
a
little
bit
longer
and
we
do
need
to
take
our
time
with
this
make
sure
everything's,
correct,
verified
and
ready
to
go
to
be
put
into
this
section.
Updating
Jenkins
is
very,
very
important,
action
and
process
to
take
in
having
guides
and
information
that
will
help
users
to
perform.
Those
actions
is
amazing
and
goes
a
long
way.
B
90.
It's
already
added
his
author
file,
Chris
Stern.
Others
have
commented
on
here
for
updating
and
reviewing,
if
there's
anything
that
anyone
else
would
like
to
add
or
find
out
more
about
what
we're
doing
here
by
all
means
check
it
out,
share
interact
if
you
want
to
submit
a
feed
review
or
con
comment
by
all
means.
B
The
second
one
here
is
a
new
reverse
proxy
Edition,
it's
for
light,
ttpd,
something
more
simple
or
not
as
much
content
but
needs
to
be
tested
and
verified
before
adding,
if
you
feel
like
joining
in
and
doing
any
testing
by
all
means,
and
then
finally
there
is
the
idea
of
uninstalling
uninstalling
a
plugin
from
Docker.
So
this
right
now
is
currently
being
documented
in
the
docker
repository.
C
I'm
trying
to
help
with
this
one
but
I'm
having
some
problems
with
the
existing
documentation.
You
know
using
the
Java
client,
you
know
the
jar,
Java
client
and
the
list
of
comments
that
were
available
on
all
available
these
days.
For
example,
you
can't
remove
a
plugin
with
a
Java
client
these
days,
or
maybe
the
command
is
hidden
whatever
it
doesn't
work,
rendering
what
to
do.
C
I
don't
know
if
the
documentation
was
written
as
if
this
was
existing,
so
I
suppose
that
one
time
it
existed
but
I
have
no
proof
I.
Just
don't.
A
B
Yeah
and
anyone
else
who
wants
to
check
in
share
input
try
some
stuff
out
Jason
testing,
whatever
have
you
ultimately
yeah?
B
This
is
a
community
project,
as
always
so
great
and
yeah.
This
might
be
something
we
need
to
talk
to
the
docker
experts
about.
So,
if
that's
the
case,
we
will
do
so
outside
of
that.
It's
being
you
know,
addressed
and
investigated,
and
Bruno's
already
done
a
bunch
of
late
work
on
there.
So
we'll
see
what
happens
outside
of
that
I.
B
Don't
think
we're
going
to
get
to
the
using
agents
page
today,
which
is
fine,
we'll
just
ignore
that
for
the
time
being
and
I
want
to
make
sure
we
end
on
time.
So
with
that
being
said,
thank
you
all
for
coming
and
participating
and
sharing
here.
I
really
appreciate
it
and
I
hope
that
everyone
has
had
a
wonderful
start
to
the
new
year
and
just
continuing
all
the
prosperity
that
we've
had
in
the
last
few
months.
B
So
thank
you
as
always,
and
this
recording
will
be
available
in
24
to
48
hours.