►
From YouTube: 2023 01 19 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
Hello
and
welcome
to
the
Jenkins
documentation
office
hours.
This
is
the
EU
US
edition
for
January
19th
2023.
today
looks
like
myself.
Bruno,
Brockton
and
Mark
weight
are
joint
rounding
out
the
group
here
and
for
the
agenda
a
couple
action
items
to
highlight:
updates
about
the
most
recent
weekly
and
next
LTS
release
update
about
Debian
12
and
what
that
means
for
Jenkins
documentation
and
usage.
A
Just
a
reconfirmation
on
the
website
component
being
completed
returning
to
order
session
from
last
week
about
handling
regressions
on
jenkins.io
and
how
that
can,
if
there's
any
nuances
or
additions
to
that
something
I
was
discussing
with
Mark,
is
creating
documentation
for
detached
plugins,
maybe
even
a
specific,
detached
plug-in
plugins
page
where
we
can
house
all
these
there's
been
a
couple
recently:
WM
Windows,
wmi
agents
being
most
recent
and
others
and
eventually
over
time
things
will
grow
old
and
need
to
be
removed
or
removed
and
separated.
A
So
some
discussion
on
that
and
a
few
pull
requests
of
note
that
again,
we
had
a
couple
last
week
to
highlight
and
just
added
a
couple
more
to
make
sure
that
we
have
no
discussion
if
it
needs.
A
B
I
just
realized
one
that
we
may
want
to
put
on
a
future
agenda
is
the
the
Google
summer
of
code
project
ideas
for
docs
that
are
affecting
docs,
so
I
wouldn't
put
it
on
today's,
because
I've
not
not
adequately
prepared,
but
I
think
we
ought
to
put
it
on,
because
we
owe
it
to
ourselves
to
look
at
the
project.
Ideas
discuss
them,
think
about
them
and
and
be
sure
that
they're
well
vetted
so
that
if
a
a
new
contributor
wants
to
offer
a
plan
for
that,
we
give
them
a
good
starting
point.
A
Yeah
definitely
and
I
know
that
there
are
there's
a
couple
projects
specifically
for
documentation
like
moving
to
the
site,
generator
and
screenshot
automation
and
I.
Actually
I'm
planning
on
being
part
of
the
mentor
group
for
these,
so
yeah
I
also
have
vested
interest
in
it
and
making
sure
that
it
goes
well.
So
we
should
definitely
talk
about
that
next
week
for
sure
cool.
Thank
you
very
much
Mark
onto
the
agenda.
So
as
far
as
the
docs
mailing
list
goes,
this
has
now
been
archived.
A
It's
read
only
and
we
have
the
docs
getter
channel
for
communication.
That
is
shorter
communication.
Questions
need
help
anything
like
that
and
we
also
have
community.jenkins.io,
which
is
for
more
discourse,
conversation
discussion,
in-depth
topics
that
we
really
want
to
add,
share
on,
and
collaborate
and
expand
on.
So
there
are
multiple
places
to
still
get
in
touch
and
the
mailing
list
is
still
available.
It's
just
in
a
read-only
format.
So
if
there
are
any
reasons
to
check
that
out,
you
still
can
and
then
for
blog
posts.
A
We
recently
had
our
2022
Recap
blog
posts,
published
I,
know
we
mentioned
it
last
week,
but
just
again,
thank
you
to
everyone
that
worked
on
this.
This
is
a
lot
of
work
and
a
lot
of
collaboration
that
resulted
in
a
really
nice
highlight
of
Jenkins
in
2022.,
thanks
to
Bruno,
thanks
to
Alyssa
Tong
and
several
other
contributors
who
worked
on
all
of
the
information
that
was
in
there
and
getting
it
together.
A
And
then
speaking
of
Google
summer
of
code,
jean-mark
Nissan
has
written
a
blog
post
on
being
a
mentor
for
Google
summer
of
code.
That
outlines
a
lot
of
what
goes
into
being
a
mentor
some
expectations
and
thoughts
behind
it.
It's
a
really
great
resource
to
consider
and
check
up
on
for
any
sort
of
mentorship,
whether
it's
Google
summer
of
code
or
something
else
so
definitely
take
a
minute.
A
If
you
have
and
if
you're
interested
at
all
in
Google
summer
of
code,
we
still
are
definitely
accepting
applications
for
mentorship
and
other
other
aspects
of
it
where
we
still
have
plenty
of
time
to
go,
and
the
summer
of
code
doesn't
officially
start
until
the
end
of
April.
The
end
of
may-ish,
so
we
have
lots
of
time
to
work
on
these
things,
contribute
get
familiarized
with
stuff.
So
again,
anytime,
you
have
it's
a
good
idea.
A
Next
up
we
have
the
releases,
so
we
had
weekly
release
2.387
this
week,
which
released
successfully
so
everything's
all
good
and
fun
there
mark.
Thank
you
again
for
handling
the
change
log
on
that
and
then
for
our
next
LTS
release.
We
have
2.375.3
that'll,
be
happening
on
February,
8th
I've,
already
created
the
chain
blog
and
upgrade
guide,
so
that
link
is
available
here
for
any
reviews.
A
It's
a
smaller
update,
just
as
in
previous
ones
that
were
0.2.3,
so
not
a
ton,
but
still
there
and
I
would
still
appreciate
any
feedback.
A
A
So
this
isn't
an
issue
in
that
sense
and
with
Java
17
being
the
future
and-
and
you
know
current
recommendation-
we're
we're
going
to
move
towards
that
as
well
and
make
sure
that
the
Jenkins
documentation
is
highlighting
Java
scene
17
as
the
way
to
go
and
the
best
method
for
usage,
so
that
all
the
functionalities
are
there
proper
steps.
Proper
actions
are
taking
Instructions,
make
sense
and
apply
correctly
across
the
board.
Just
all
the
benefits
that
would
come
along
with
having
that
update
available
will
be
felt
across
the
documentation
as
well.
B
Well,
on
that,
one
that
that
Red
Hat
Universal
base
image
topic
there,
maybe
you
could
go
ahead
and
open
that
yeah,
a
contributor
from
Red
Hat,
has
submitted
a
proposal
recommending
that
we
add
a
Docker
container
image
for
the
red
hat
Universal
base
image.
Nine
we
already
ship
one
for
Universal
base
image.
Eight
and
nine
has
now
released.
It's
been
released
for
quite
a
while
we're
now
on
9.1
and
and
so
I
think
it's
a
good
idea.
B
I
think
this
is
the
right
approach,
but
the
question
to
the
contributor
was:
is
it
intentional
that
you're
doing
Java
11
shouldn't?
We
consider
here
doing
Java
17
as
the
container
image
and
and
the
one
of
the
key
sponsors
Oliver
goncha
is?
Who
also
was
our
release
officer
mini
for
many
years,
so
very
experienced
with
Jenkins
Etc
said:
oh
yeah
we'll
probably
need
Java
17
pretty
soon.
Maybe
we
should
just
make
this
one
Java
17..
B
So
for
me
my
preference
is:
let's
make
this
one
Java
17,
not
that
it's
required
not
that
it's
mandatory
but
doing
Java
11
on
the
brand
new
red
hat
operating
system.
Ubi
9
feels
backwards.
Let's
do
Java
17
as
the
first
preference
that
way
it's
it's
leading
out
so
that
when,
as
we
make
the
transition
in
April
or
May
to
more
actively
documenting
Java
17
in
more
places,
it's
just
a
natural
part
of
that.
A
B
A
And
yeah
no
I
appreciate
that
Mark
thanks
for
providing
all
the
context,
and
that
kind
of
background
to
that,
so
amazing
and
yeah
keep
an
eye
out
for
that
next
up
here
on
the
agenda.
Just
to
note
again,
the
website
component
on
jira
has
been
completed,
so
there
are
no
more
jenkins.io
website
tickets
on
the
Jenkins
jira.
Those
are
in
GitHub
now
being
in
in
the
GitHub
issues
tracker
and
from
here
on
out.
A
That's
where
they'll
be
submitted
to
so
that's
taken
care
of
we're
already
yeah,
let's
go,
let's
taken
care
of
next
on.
The
list
is
how
we
handle
regressions
on
jenkins.io.
This
is
something
that
we
discussed
last
week,
talking
about
how
the
Jenkins
core
team
handles
regressions
and
how
they
go
about
resolving
them
or
reverting
them
depending
on
what
needs
to
happen,
and
we
checked
out
some
examples
recently.
The
Jumbotron
is
not
currently
rotating
and
these
sponsor
images
had
been
sized
a
little
incorrectly.
A
So
these
are
things
that
may
not
have
been
sight
breaking
or
impactful
to
many
users.
They
did
take
a
little
bit
longer
to
come
onto
our
radar,
but
the
fact
of
the
matter
is
these
are
regressions
that
were
that
people
are
experiencing
and
we
have
to
make
sure
that
we're
taking
care
of
these
properly.
We
went
and
created
labels
for
major
regression
and
regression
so
that
when
these
are
submitted
in
the
issue
tracker,
we
know
just
how
severe
it
could
be
if
it's
absolutely
breaking.
A
If
it's
super
minor,
if
it's
you,
you
know,
and
anything
in
between
so
also
talked
about
using
the
same
process
as
core
where,
if
it
is
breaking
reverting
it
within
a
couple
hours
less
than
a
day,
I
want
to
say
Mark
if
I'm
not
mistaken,
and
then,
depending
on
the
severity
of
the
issue
we
can
assess
from
there,
we
can
figure
out
what
needs
to
happen
and
prioritize
accordingly,
it's
not
something
that
is
set
in
stone
right
now,
because
we
are
just
starting
to
adapt
this
so
yeah.
A
This
is
super
open
for
feedback
and
ideas,
and
if
anyone
has
preferences
or
previous
experiences
that
might
lend
themselves
to
this
sort
of
thing,
I'm
more
than
happy
to
hear.
B
I
think
I
think
we've
got
a
a
good
plan
there.
We
may
ultimately
want
to
document
that
in
the
contributing
guide,
in
fact,
I
think
we
will
want
to
put
it
in
the
contributing
guide
for
jenkins.io.
That's
that's
where
it
ultimately
belongs,
I
think,
but
for
right
now,
let's
keep
working
out
what
we,
what
we
agree
on
and
then
we
can
put
it
into
the
contributing
guide
later
is
the
contributing
guide?
Is
the
formal
documentation
location
for
it?
A
Great,
that's
how
that
makes
sense.
That
sounds
like
a
good
plan,
so
yep
awesome
next
up
on
the
agenda,
so
this
is
something
I
was
talking
to
Mark
about
just
prior
to
the
meeting.
There
are
detached
plugins
that
exist
within
Jenkins
Windows,
wmi
agents,
Oracle
jdk
Tool,
and
there
are
more
on
the
list
here.
Of
course,
you
can
see
software
configuration
management,
plugins,
authentication,
plugins,
miscellaneous,
build
tool,
plugins
like
there's
a
lot.
A
There
are
a
handful
of
detached
plugins
that
could
be
more
noticeable
to
folks
than
others,
depending
on
their
use
case.
But
ultimately,
if
these
are
detached,
folks
or
users
are
going
to
be
curious
as
how
they
can
remove
themselves
or
separate
those
things
out
themselves.
If
they're
running
an
older
version
of
Jenkins
as
their
Baseline,
they
may
not
have
noticed,
but
the
second
they
update
they're
going
to
notice.
A
C
B
B
It's
doing
exactly
what
I
want
I
use:
Windows
Active
Directory
for
Authentication,
but
I
can't
uninstall
the
Pam
authentication
plugin,
because
I'm
dependent
on
another
plugin
that
has
an
old
jenkins-based
version,
an
old
Jenkins
minimum
version,
and
it
makes
the
Pam
authentication
plug-in
an
implied
dependency.
So
now,
I'm
stuck
with
Pam
off,
which
is
a
very
Unix
thing
right,
I
know,
I
will
never
use
it
on
my
windows.
Controller.
B
Never,
but
I
can't
uninstall
it
because
the
implied
dependency
on
these
other
plugins
that
are
have
an
old
Baseline
but
I
need
them,
and
and
so
that
that
story
is
a
bad
story
for
the
user
or
I,
absolutely
know
I'm,
never
going
to
use
subversion.
I,
Know,
It
And,
yet
because
I
have
some
old
plug-in
installed.
I
have
to
I
have
to
also
install
so
I
have
to
also
have
subversion
installed.
B
B
So
it's
it's.
That's
that
story
of
detached
plugins
and-
and
there
are
lots
of
complications
hiding
there,
that
wmi
agents
is
just
the
first.
If
someone
were
to
deprecate
the
CBS
plug-in,
there
would
be
a
lot
of
wmi
agent
style
angst
out
in
the
world.
They
would
say,
but
CBS
is
actually
not
used
very
often
anymore,
as
a
source
control
system
right
there
just
aren't
many
projects
that
use
it.
So
so
you
could
say:
hey
somebody
might
deprecate
it.
B
They
may
say
we're
not
maintaining
this
thing
or
maybe
a
critical
problem
is
discovered
that
it's
got
a
security
issue
in
it
and
no
one
fixes
it.
Now.
You
get
a
report
in
Jenkins
that
says
this
plugin
has
a
known
vulnerability.
You
try
to
remove
it
and
it
says
I'm.
Sorry,
you
can't
remove
it
because
there's
this
implied
dependency.
So
there
are
lots
of
dangers
in
this
in
these
split
plugins
that
haven't
shown
yet
wmi
agents
is
only
the
first,
but
this
place
has
some
has
some
risks
in
it.
A
Oh,
that
makes
sense
that
helps
clarify
it's
better
way
better
to
give
some
real
context
to
it
in
a
real
situation
that
someone
might
find
themselves
in.
That's
not
boring,
that's
real,
that's
more
important,
so
yeah,
no
I
appreciate
it
and
yeah
and,
like
I,
said
that
this
is
still.
A
This
is
very
much
just
preliminary
ideas,
there's
other
plugins
or
anything
that
anyone
has
they've
run
into
something
they
have
an
idea,
for
they
have
maybe
some
Insider
knowledge
of
what
might
be
going
on
as
far
as
the
application,
like
anything
at
all,
the
discussion
is
here,
we're
more
than
happy
to
listen
and
share
and
again
open
to
anything.
A
And
then
last
thing
on
my
list
here
on
the
agenda
is
just
pull
requests
of
note
again.
A
couple
of
these
were
we
talked
about
last
week.
The
updating
Jenkins
guide
that
vandit
has
submitted
and
thank
you
to
Vandy
for
all
these
submissions.
Lately
a
lot
of
work
being
taken
on
and
it's
it's
kind
of
impressive
in
every
sense
of
the
word,
but
Wendy
wanted
to
add
a
guide
on
how
to
actually
update
Jenkins
on
Linux,
mostly
I,
think
there
might
have
been
a
couple
yeah
Windows
as
well.
A
A
Anyone
else
is
welcome
to
review.
The
pull
request
is
open.
Any
ideas
or
feedback
is
appreciated
on
there
and
then
another
user
I
forget
who
exactly
Hector
Vito
had
submitted
a
pull
request
about
adding
a
light.
Tpd
reverse
proxy
I
reviewed
a
documentation,
wise
I'm,
not
an
expert
in
Reverse
Boxes
by
any
means.
A
A
B
And
what
the
author
has
done
is
they've
documented
how
to
uninstall
plugins
in
multiple
with
multiple
techniques.
The
challenge
is
that
the
technique
I
haven't
I,
got
to
review
it
again,
but
the
technique
they
used
for
Docker
has
has
failure
modes
where
it
doesn't
work
as
expected
and
and
it's
because
uninstalling,
a
plug-in
and
Docker
container
is
more
complicated.
B
C
Yeah,
so
it
yeah
sorry
and
even
worse
than
that,
it's
also
describing
a
technique
with
the
Jenkins
client,
which
is
supposed
to
remove
plugins,
except
that
the
commands
which
are
listed
do
not
exist
to
my
knowledge,
so
I
don't
know
what
to
do
with
that.
B
Well,
yeah
and
I
I
think
I,
believe
the
author
has
removed
that
reference,
so
I
think
I
think
that
part's
okay
now
because
saying
saying
that
there's
a
command
line
that
is,
it
doesn't
exist.
Okay,
that's
bad,
but
but
the
other
it
just
needs
more
more
review
and
yeah
somebody
who's
familiar
with
Docker.
To
try
it
and
see.
Does
the
instructor
do
the
instructions
work
as
given.
C
A
No
worries,
Maria
and
I
think
the
main
thing
that
I
wanted
to
mention
on
this
is
that
if
this
you
know
if
this
does
work
out-
and
this
is
submitted
emerged
eventually,
that
is
documentation
that
would
have
to
make
its
way
over
to
jenkins.io
as
well,
so
not
immediate
effect,
but
down
the
line.
That
will
be
something
that
we
should
consider
and
plan
on
moving
over,
or
at
least
including
in
the
Jenkins
documentation.
A
And
then,
ultimately,
this
pull
request
was
actually
well.
It's
still
open,
but
it's
closer
to
being
approved
emerged
than
not.
A
We
were
taking
Vandy
again
had
submitted
another
pull
request
to
add
some
content,
this
time
to
the
pipeline
syntax
reference,
and
when
adding
this
parameter
information
we
looked
at
it
and
said
this
seems
like
it's
getting
a
little
more
than
what
the
syntax
page
should
represent
or
share,
and
so
Mark
made
the
suggestion
that
hey.
Why
don't
we
take
that
and
put
it
somewhere
else?
Where
would
be
able
to
put
it?
A
Where
can
we
add
that
in
because
that
does
help
give
insight
to
this
so
I'm
talking
about
maybe
having
a
parameter
page
or
a
page
specifically
for
these
sort
of
things,
because
while
I've
found
documentation
for
things
like
the
environment
variables,
not
so
much
as
parameters
and
so
well,
obviously,
we
want
to
make
sure
this.
This
is
well.
The
Jenkins
documentation
is
thorough
and
informative.
So.
B
B
So
I
add
a
twice
all
right.
That's
that's
a
don't
do
that,
but
if
you
do
what
happens
and
and
those
kinds
of
things
that
are
much
broader
than
just
pipeline
syntax
right,
that's
any
parameterized
job
has
that
characteristic,
and
there
are
other
cases
what
happens
if
I
Define
a
parameterized
job
in
the
Jenkins
file.
B
A
Okay,
great
great,
thank
you
very
much
Mark
that
helps
explain
the
the
idea
and
everything
a
lot
more
and
yeah
like
I,
said
I
and
we've
talked
about
this
too,
and
that
the
syntax
page
should
be
a
quick
reference,
not
an
extended
book
about
these.
These
matters,
that's
what
the
rest
of
the
documentation
is
for,
so
we
can
utilize
that,
to
its
fullest
extent,.
A
Okay,
and
that
actually
covers
for
the
agenda,
I
had
just
to
make
sure
there
anything
anyone
else
wanted
to
talk
about
mention
and
share
nope.
B
A
Right,
great
okay,
then
I
will
go
ahead
and
stop
the
recording
it'll
be
available
in
about
24
to
48
hours,
and
thank
you
again
for
oh.