►
From YouTube: 2023 06 22 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
topics
on
the
agenda,
blog
posts
Google
summer
of
code-
that
one
can
be
deleted.
Changelog
for
20.401.2
pull
request
from
Jeffrey
Chen
that
we
should
talk
to
more
update
CLI
for
Jenkins
documentation.
Do
you
want
that?
One
on
the
list?
Bruno?
If
you
don't
mind,
just
a
few
minutes,
great
discussion
and
review
of
java
11
to
Java
17
changes
in
the
documentation.
This
one
I
think
I
would
delay
one
week
until
Kevin's
available.
A
And
then
devops
World
Tour
that
one
I'm
going
to
just
drop
from
the
list
for
now,
because
I
don't
think,
there's
much,
we've
got
to
say
here:
no
and
releasing
a
plug-in.
This
is
one
I'd
proposed
that
Bruno
and
I
have
been
collaborating
on
a
particular
plug-in.
Maybe
it's
worth
us
doing
a
session
here
where
we
do
a
release
of
the
plugin,
show
the
steps
that
are
required
and
why
anything
else
that
we
need
on
the
agenda.
I,
don't
think
so!
Okay!
B
B
Everything
like
but
I.
Just
don't
remember
the
highlights.
Maybe
you
should
just
have
a
look
at
the
key
takeaways.
Why
was
that?
So?
Yes,
plugins
updates
to
fix
a
security
vulnerabilities
on
May,
the
16th
gdka
8,
finally
has
been
dropped
in
favor
of
gdka
11
for
the
running
Jenkins
agent.
B
At
least
it's
been
what
a
year
or
so
yeah
cool
SSH
agent
has
released
5.00
now
in
at
5.5.0,
and
there
has
been
some
breaking
changes
related
to
the
Alpine
version,
I
guess
so,
if
you're
using
that
you'd
better,
have
a
look
at
the
documentation
at
the
changelog.
A
Were
the
things
that
I
I
think
those
are
fine,
the
rest
are
covered,
we've
got
the
the
governance
topic
had
some
things
in
terms
of
prototype.js
being
removed
and
html3
HTML
unit
3
and
guava
32,
and
we
I
continue.
Let's
see
on
UI
ux
prototype
and
accessibility
and
those
are
cool
things
and
then
end
of
life
is
coming
for
for
some
operating
systems,
and
this
is
warning
users
about
it
and
on
we
go.
B
A
B
You
know
intuition
is
not
always
helping
I
thought.
I
knew
how
to
get
rid
of
deprecated
plugin
just
by
following
what
was
in
the
UI
and
I
was
wrong
plenty
wrong.
So
I
took
some
time
and
wrote
too
long.
Didn't
read
a
section
so
that
people
who
are
in
a
hurry
have
the
correct
at
least
I,
guess,
I
hope
a
way
of
getting
rid
of
duplicated
for
plugins
when
using
Docker
and
then
I
detail
the
intuitive
way,
at
least
my
intuitive
way
of
trying
to
get
rid
of
Darker
plugins
and
why
it
fails.
B
So,
if
you
are
courageous
enough
to
read
that
up
to
the
end,
you'll
see
that
the
progress
makes
sense
until
the
end.
When
you
see
it's
not
right,
it
just
doesn't
work
and
I
explain
I,
try
to
explain
why
it
doesn't
work,
it's
just
because
you
are
trying
to
work
against
the
flow
like
a
Solomon.
You
know
in
the
river
and
why
you
should
begin
to
remove
everything
from
the
awkward
context.
First
of
all
and
then
work
with
the
UI.
B
B
Yeah
I
should
maybe
have
explained
this
one
because
I
think
it
gets
re.
Let
me
know
if
I'm
wrong,
but
I
think
it
gets
rid
of
all
the
volumes
in
use
or
something
like
that
or
I.
Just
can't
remember
right:
oh
that's
a
good
thing
I.
Should
we
try
and
maybe
make
another
article
about
that
one?
Do
you
have
any
hint
about
why
I.
A
A
B
B
A
Great
all
right,
then,
on
Google
summer
of
code,
so
vandit
Singh's
preview
site
is
available.
Now
that
shows
this
is
one
way
that
Jenkins
documentation
might
look
when
hosted
under
antora.
Looking
here's
the
version
number
Choice
here
are
the
version,
number
choices
and
different
components
that
can
be
selected
at
those
different
version
numbers.
So
this
is
this
is
just
a
prototype,
but
the
Prototype
is
at
least
for
me
quite
interesting.
It
is
so
he's
got
the
concept
of
user
documentation
and
it's
versioned
and
then
separately
version.
A
A
B
B
The
goal
is
to
simplify
as
much
to
can
the
existing
documentation
about
Docker
by
providing
examples
that
work
out
of
the
box,
and
it
would
not
really
the
case,
but
now
from
this
week
on,
we
have
a
working
example,
fully
automated
just
one
shelf
file
to
launch
and
you're
good
to
go,
and
hopefully
we
will
have
other
more
meaningful
examples
in
the
weeks
to
come,
we'll
see.
But,
fourth
time
being,
it
has
proved
working
on
Linux,
wsl2,
Mac,
OS
and
gitbot.
A
Okay,
so
the
WSL,
you
said:
Linux
WSL
gitpod.
What
was
the.
A
B
B
A
Good
excellent,
okay,
good,
then
the
other
two
Google
summer
of
code
projects
really
don't
have
documentation
impact
so
I'm
just
going
to
take
that
note
out
anything
else
on
Google
summer
of
code.
No
thank
you.
Okay,
so
2.401.2
changelog
Kevin
noted
in
his
preparation
of
the
notes
that
it's
been
prepared
and
merged
and
I
think
it
was
quite
simple.
It's
got
just
the
one
item
that
says:
hey
we're,
warned
administrators
when
their
Linux
operating
system
is
approaching
end
of
life
and
next
week,
Chris
Stern
is
the
release
lead.
A
A
So
I
split
it
into
two:
oh
back,
okay,
I
I
couldn't
push
back
to
his
reposit,
his
branch
and
so
I
I
split
and
the
split
went
to
this
one
convert
the
administering
page
and
to
this
one,
which
is
add
a
best
practices,
page
and
I've
I-
think,
let's
take
a
look
to
see
if
they've
got
feedback
on
either
of
them.
That
say,
we
need
to
block
this
thing.
Okay,
so
Kevin's
given
his.
A
A
A
A
A
Copy
rename
and
move
projects
which
is
functionality
Jenkins,
has
had
for
a
very
long
time,
but
has
never
documented
that
fact,
so
this
one
this
one
I
think
give
and
actually
since
we're
here,
why
not,
let's
just
call
it
Kevin's
feedback
is
resolved,
I'm
going
to
go
ahead
and
just
squash
merge.
It.
A
B
Oh
yes,
indeed,
it
doesn't
work.
Yet
the
thing
is
I'm
trying
to
replace
all
the
references
to
Docker
images
and
plug-in
versions
in
the
documentation
and
I
had
done
things
wrong.
You
know,
I've
just
been
discovering
a
live
for
a
few
weeks
now
and
I'm
doing
newcomers
errors,
of
course,
so
I
had
a
refactor
recently
and
I
stumbled
onto
limitations
or
bugs
within
update
CLI.
B
So
I
submitted
two
issues,
I
think
yesterday
to
update
CLI,
and
one
of
them
has
already
been
sold
and
I
hope
to
see
a
new
release
of
update
CLI
soon,
so
that
I
can
get
something
better
and
I
also
asked
for
some
new
features
on
update
CLI
to
get
things
faster.
For
example,
you
know
it
works
with
sources
and
conditions,
then
targets
and
for
some
reasons,
I
need,
at
the
same
time,
Ruby
and
Alpine
python
in
Alpine
to
compose
a
tag
with
the
version
of
Ruby.
B
The
version
of
Alpine,
for
example
and
I,
do
that
for
several
files
and
it's
a
waste
of
time,
because
I
need
Alpine
in
most
of
the
files,
so
I'd
like
the
channel
I
to
do
something
you
know
with
the
sources
and
keep
them
up
to
date
for
all
file
that
it
will
process
frightened.
But,
yes,
it's
still
progressing
and
for
some
of
the
documentation,
the
committee
removed
the
pinned
versions
in
the
documentation
for
very
valid
reasons,
but
I
put
them
back.
Oh
good,
okay,
yes,
I'm,
afraid
I
did
that
after
you
Mark
I'm.
A
B
Felt
your
pain
when
reading
your
PRS,
how
can
I
do
such
a
boring
work?
Well,
I
have
to
do
something
about
it
anyway,
and
it
doesn't
work
for
the
time
being
just
because
the
pinned
versions
are
not
in
the
master
Branch.
You
know
they've
been
removed,
so
my
update
tli
check
doesn't
work,
but
that's
not
a
mandatory
step.
So
whenever
we'll
merge
it,
that
should
be
fine,
but
it's
not
ready
yet
sorry
about
that.
I
am
still
waiting
for
new
versions
of
update,
live
to
get
it
to
work
perfectly.
A
B
A
A
Else
anything
else
on
your
use
of
update
CLI.
No
thank
you
Mark,
okay.
So
next
topic
was
Java.
11
to
Java
17
upgrade
changes
this
one.
Let's
link
to
the
pull
request,
because
Kevin
has
created
a
draft
pull
request
that
we
can.
We
can
reference,
and
the
draft
pull
request
has
already
a
few
notes
in
it
in
terms
of
what
what
we
have
to
do.
A
A
A
A
those
kind
of
things
all
right
anything
else
on
Java
11
to
Java
17.
No,
thank
you
more.
Okay.
Next
topic
was
releasing
a
plug-in
all
right,
so
Bruno
and
I
have
are
have
been
contributing
to
oh,
dear
Bruno,
which
plug-in
was
it.
It
was
oh
HTTP
request
right,
I,
think
so!
Yes,
okay!
So
let's
go
to
the
HTTP
request,
plugin
and
here
what
we
see
is
that
we
had
a
pull
request
from
Christoph
bexer,
Christoph,
ER,
yeah
right,
proposing
a
new
feature
and
Bruno
and
I
reviewed
it.
A
A
Well,
quite
a
number
of
things
that
have
been
have
been
collected
since
August
of
2022
when,
when
this
the
last
release
was
done
of
this
plug-in,
it's
got
lots
of
component
updates
right,
the
upgrade
to
HTML
unit
three.
It
removes
some
old
junk
from
jelly
files.
It
improves
a
number
of
things
in
documentation,
fixes
one
bug:
let's
look
at
that
bug
just
to
be
sure,
okay
and
then
it
has
three
new
features,
one
of
which
is
required,
Java
11
and
Jenkins
2.361.4.
It's
it's
a
reasonably
significant.
A
B
A
B
A
Not
because
the
version
of
java
that
someone
chooses
depends
on
their
on
their
preferences,
of
course,
so
us
mandating
you
need
to
use
well,
it
depends
on
the
on
the
plug-in
itself.
This
plug-in,
because
it
now
requires
Java
11
would
have
to
be
released
with
at
least
Java.
11.
I
could
do
the
release
with
Java
17
and
it
would
generate
Java
11
bytecode,
but
I'm.
A
conservative
and
I
like
to
generate
releases
with
the
same
Java
version
that
I've
been
testing
with,
of
course,.
A
So
it's
offering
the
it's
asking
me
the
question
interactively
what
version
do
I
want
to
release
and
I'm
going
to
open
up
my
page?
That
was
telling
me
what
version
this
is.
The
page
we
were
looking
at.
The
draft
is
1.17,
so
that's
the
right
version.
This
is
generated
by
release
drafter
automatically
so
because
release
draft
is
configured
we'll
use
1.17
and
that
tag
now.
B
Let's
check
something
to
interrupt:
that's
because
it
guessed
that
there
was
nothing
major
that
would
have
necessary
a
bigger
you
know,
not
a
major
update
or
whatever
it's
just
a
new
version.
Yeah.
A
It
to
be
to
be
precise,
what
it
does
is.
It
reads
the
Palm
file
that
has
this
number
in
it,
and
so
that's
that's
great
we're
going
to
say
the
next
version
will
be
1.18
snapshot
and
now
it's
going
to
start
the
build,
and
this
will
run
all
the
tests
and
once
the
tests
have
passed,
it
will
then
publish
the
build.
It
actually
runs
the
build
in
two
steps.
It
runs:
that's
what
release
colon
prepare
was
that
prompting
phase,
and
then
it
runs.
This
set
of
tests
and
I
believe
release.
A
B
Because
there
may
be
a
build
with
debug
information
and
maybe
something
without
debugging
yeah.
A
I,
don't
think
that's
what
they
do,
but
I'm,
not
sure
and
again
I,
don't
know
the
details
of
Maven
release
process.
It's
good
enough
for
me
that
this
process
works
now,
while
it's
running,
let's
go
look
at
at
the
instructions.
Okay,
some
of
the
things
that
might
fail.
We
could
get
a
failure
to
upload
right
and
that
might
have
been
might
happen
in
this
case.
A
We
may
see
that
because
I
requested
permission
to
perform
that
upload
a
few
hours
ago,
but
if
we
were
too
fast,
it
might
be
that
the
permissions
have
actually
not
been
granted
yet.
So,
if
we
look
at
at
that
pull
request,
let's
go
look
at
the
pull
request.
I
submitted
to
repository
permissions
updater.
This
is
where
I
submitted
a
request.
B
A
A
There's
no
there's
a
difference
and
that's
that's
an
interesting
one
right,
because
you
and
I
both
have
permissions
on
the
GitHub
repository
yep
and
we
have
those
permissions.
However,
some
months
ago,
I
had
revoked
our
release.
Permissions,
oh
yeah,
by
submitting
this
pull
request
that
says:
hey
stop
these
people
from
releasing
plugins.
It
didn't
revoke
our
GitHub
permissions.
All
it
did
was
revoke
our
permissions
to
release,
so
we
were
still
allowed
to
contribute
to
the
plugin
still
allowed
to
merge,
pull
requests
help
it
along,
but
what
we
couldn't
do
was
deliver
a
new
release.
A
Okay
right
and
so
this
basic
what
this
pull
request
that's
on
screen
now
is
doing.
Is
it's
reverting
a
small
part
of
this
pull
request,
yeah
and,
and
then
I
may
still
go
back
eventually
and
say:
I'm
not
really
ready
to
stay
on
as
an
HTTP
request
maintainer,
but
this
particular
this
particular
release
feels
like
it's
a
worthwhile
release
right
upgrade
to
Java
11.,
add
a
new
method,
add
credential,
credential
tracking,
which
I
like
a
lot,
because
it
helps
me
know
which
jobs
are
using
a
particular
credential.
A
So
so
we
hope
that
this
is
all
positive
for
its
consumers
yeah
and
now,
let's
see
how
the
build's
going.
Oh,
it's
finished.
Okay,
so
what
we
see
here
is
uploaded
to
repo
to
maven
jenkinsci.org
to
this
location,
and
so
here
is
the
data.
Here
is
the
plug-in
and
if
I
open
that
page
in
my
web
browser,
we
can
actually
go.
Look
at
it
and
see
now
really
people
shouldn't
bother
browsing
the
artifact
repository
like
this,
but
there
it
is.
A
Well,
yeah:
now
the
release
itself
won't
appear.
It
takes
from
minutes
to
as
much
as
an
hour
or
two
for
it
to
become
visible
in
the
Jenkins
Update
Center.
So
if
we
go
to
updates.jenkins.io
here,
we
can
see
there's
a
link
that
says
latest
releases
of
Jenkins
war
and
all
plug-ins.
So
let's
open
that
page
and
now
here
if
we
go
to
http
requests.
A
I
want
the
link
because
I'm
going
to
use
it
to
query
the
mirrors.
So
if
I
do
this
and
do
a
question
mark
mirror
list,
this
will
ask
Update
Center
to
give
me
the
list
of
mirrors
and
the
version.
So
right
now
the
version
is
still
1.16
and
we
can
see
that
it's
it's
available
on
eight
different
mirrors,
but
what
we
released
was
1.17.
A
B
A
The
answer
is
it
won't,
so
what
did
appear
automatically
was
not
the
tag
1.17
has
appeared
here.
That's
good
right,
that's
the
tag
that
was
created
by
Maven
release,
prepare
and
release
perform,
and
this
is
letting
me
use
that
page
that
already
existed
and
now
I'm
going
to
go
ahead
and
publish
it
as
the
release.
A
So
the
release
is
now
published
and
now
other
users
can
see
that
release
on
the
GitHub
page
and
plugins.jenkins.io
over
the
course
of
the
next
four
to
eight
hours
will
detect
this
release
as
well
and
we'll
insert
the
documentation
from
this
release
onto
its
page.
So
if
we
go
to
plugins.jenkins.io
for
right
now,
we
will
see
that
it's
still
showing
1.16.