►
From YouTube: 2021 11 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
All
right
welcome
it's
the
22nd
of
november.
This
is
documentation
office
hours.
Let's
see
meg,
it's
just
you
and
me
for
right
now,
so
we'll
miss
that
I've
got
news
from
plugins
development,
3.322
changelog,
our
2.322
2.319.1
upgrade
guide
and
changelog
triage
team
and
plugin
installation
manager.
Latest
news.
A
A
B
A
Excellent
okay,
so
latest
news
from
the
world
of
plugins.jenkins.io
gavin
is
investigating
other
generation
techniques
and
it
may
allow
links
to
be
embedded
inside
the
page
for
github
markdown.
B
A
B
A
A
End
of
the
change
log,
okay,
got
it
good
and
then
we've
got
an
rfe.
Add
descriptions
to
this
to
administrative
monitors,
and
I
like
this
one
so
daniel's
comment
was
add
descriptions
or
not.
It
could
be
easily
considered
too
minor,
and
I
thought
I
I
personally
like
this
pull
request
a
lot
and
would
like
it
to
be
in,
but
let's
test
with
you
meg,
so
here,
let's
look
at
how
he
he
provided
a
a
very
nice.
If
I
remember
right,
he
gave
us
a
there.
It
is
a
screenshot
that
shows
how
it
looks.
A
B
A
Labels
that
highlight
the
the
a
specific
tag
for
a
thing
in
this
case
security
and
then
a
small
description
beneath
it.
Now,
let's
look
for
administrative
monitors
here
we
go
when
I
click
this.
Here's.
What.
A
A
A
A
B
B
B
A
B
B
A
A
A
Okay,
so
what
he
was
modifying
is
the
old
way
of
looking
at
it.
Oh
no!
This
is
the.
This
is
the
new
way
now,
with
the
current
current
ui
notice,
the
notice,
the
rounded
corners
here
and
the
the
font
etc
so
and
all
uppercase
here,
instead
of.
If
I
look
at
the
same
thing
in
the
current,
it
looks
like
this
okay
notice
that
compared
to
this.
B
A
Right,
this
is
very
much
trying
to
to
the
continued
effort
to
improve
the
look
of
the
user
interface.
Absolutely.
A
B
A
B
B
A
B
A
A
It
needs
a
it
needs,
a
regression
since
2.xxx.
B
A
A
Nope,
okay,
so
I'll
have
to
go
looking
for
it
separately
it.
This
definitely
was
previously
showing
okay
show.
Well,
let's,
let's
go
look
at
it.
So
it's
if
we
look
at
manage
jenkins
and
manage
users
mark
waite
here
is
the
user
id,
not
the
username.
If
we
edit
that
thing
you'll
see
that
the
name
should
be
mark,
wait,
mark
space
weight,
and
so
it's
we
we
regressed,
we
switched
now,
it's
it's!
It's
stating
it
correctly.
It's
telling
us
it's
showing
user
id,
but
it
previously
was
showing
username.
A
A
A
A
A
So
this
is
fixing
that
right
now,
the
question
is:
how
should
we
phrase
that
setting
icon
shows
in
the
drop
down
menu
is
again
visible
in
the
drop
down
menu.
A
So
the
the
setting
it's
using
is
configure
system.
So
maybe
the
word
setting
is
a
mistake
as
well.
B
A
A
A
A
A
And
and
as
you
look
at
the
text
there,
you
can
probably
see
why
it's
four
separate
entries,
but
his
his
recommendation
was
hey.
Should
we
first
consider
making
this
third
entry?
Add
the
system
property,
something
or
other
put
that
into
the
upgrade
guide,
not
in
the
change
log,
because
upgrade
guide
is
probably
the
more
detailed
location
for
that,
and
then
we
could
link
from
here
to
the
upgrade
guide.
A
A
A
B
Choked
on
my
diet,
coke,
so
I
muted
myself
and
I
just
kept
talking
so
this-
do
we
have
a
blog
about
the
building
node.
We
have
that
blog
explaining
the
terminology,
change.
A
We
do
yeah
well,
we've
got
not
only
do
we
have
not
only
do
we
have
a
blog
for
it.
We
also
have
a
a
page
on
jenkins.io
for
it
dedicated
to
it.
B
A
It
is
but
well,
it
is,
but
I
want
to
be.
I
want
to
be
sure
that
we
mention
the
the
specific
term
here,
built-in
node
as
part
of
this,
because
they
need
to
understand-
and
this
must
be
tight-
should
use
the
label
built
dash
in
and
this
link
to
the
built-in
node
name
label.
Migration
thing
is
maybe
that
should
be
a
link
to
the
to
the
upgrade
guide.
A
B
B
A
A
B
A
Yes,
well
so
with
controller
okay,
that's
a
good
question,
replace
the
term
master
with
controller
for
the
main
jenkins
application
for
the
main
j.
So
here
it
is
for
the
main
jenkins
application,
so
don't
even
need
to
parenthesize
it.
B
A
B
A
A
B
A
We
look
at
the
agents,
you
see
master
here
uh-huh
and
here
it's
called
built-in,
okay,
okay,
so
that's
and
then,
when
I
edit.
That
thing
I
see.
Okay
here
are
the
jobs
tied
to
it
when
I
edit
this
thing,
no
job's
tied
to
it,
that's
healthy,
when
if
I
want
to
build
something
on
this
note,
that's
an
anti-pattern,
but
let's
say
I
have
some
very
specific
reason
why
I
want
to
like
in
my
case
here
there
are
some
things.
B
A
A
B
A
C
A
There's
a
there's
a
migrate
button
and
that
migrate
button
is
described
here
as
well.
Add,
basically,
it's
add,
add
a
migration
or
what
it
really
does
is
there's
now
a
button
or
a
link
that
will
perform
that
will
migrate
you
from
using
master
as
your
the
name
of
the
node
on
your
controller,
to
using.
B
A
Now
allow
how
about
the
let's
try:
a
new
phrasing:
okay,.
B
B
A
A
A
B
Not
at
all,
not
at
all
and
another
question
is
this:
only
on
the
ui
would
this
affect
my
jks
files.
A
B
A
A
B
A
A
A
A
B
A
B
A
C
C
A
A
A
A
A
B
B
A
B
A
B
B
A
B
A
Okay,
so
back
to
our
editing
the
text
all
right,
so
I
I
guess
other
questions
before
we
go
back
to
the
text.
Is
that
so
we've
seen
that?
Oh,
oh
and
I
should
okay,
we
I
haven't
applied
the
migration
yet
so
first,
let's
confirm
this
shows
it's
named
built-in
node.
Even
now
before
I
apply
the
migration.
A
I
don't
okay,
I
don't
have
a
way
to
just
a
minute.
I
want
to
see
this
because
I
need
to
be
sure
I
understand
it
so
new
node,
no
new
agent,
let's
this
is
james
bond.
That's
what
it
is.
Okay,
good,
all
right.
A
A
C
A
A
B
A
A
It
built
and
the
console
output
tells
us
building
on
the
built-in
node
all
right,
but
that
means
that
the
label
master
was
there.
Now,
if
I
edit
this
job,
configure
it
and
say
instead
of
master,
if
I
say
built-in,
it
will
tell
me
nothing
matches
it:
aha,
okay!
So
I'm
going
to
save
it
with
that
non-matching
and
now
I'm
going
to
perform
the
migration.
A
B
B
B
A
B
B
A
A
Do
not
very
good
yes
right,
dude
yeah,
present
tense,
okay,
yeah
and
instead
of
since
I'm
negating,
I
have
to
use
an
or
right
so
existing
installations
do
not
change
the
node
name
or
label
of
the
built-in
node
until
an
administrator
explicitly
performs
the
migration
okay
new
installations,
and
should
I
put
this
before
existing.
A
A
B
A
B
A
Yeah,
so
the
the
the
jenkins.org
link
is
up
here.
Okay,
but
the
trick
for
me
is:
I
want
to
get
that
text
the
system
property
text
into
the
upgrade
guide
so
help
me
with
this
for
just
a
minute:
2-303,
19..
A
B
A
A
Built-In
node
name
and
label
migration.
So,
as
part
of
this
there's
a
as
heading
for
affected
features,
there's
a
heading
for
migration,
there's
a
heading
for
plug-in
compatibility
and
then
that
ends
should
I
put
something
here
for,
and
I
don't
know
how
we
call
escape
hatches.
Should
I
put
a
new
a
new
heading
at
the
same
level
as
plugin
compatibility,
which
says
just
in
case
or
override.
B
B
Could
that
be
an
information
or
note
or
something
under
the
migration
section?
Oh.
B
A
B
B
A
B
A
A
B
B
A
A
A
A
B
A
C
C
B
C
B
A
B
B
A
C
A
B
B
Okay,
so
after
existing
installations,
not
change
the
node
name,
etc
until
explicitly
performs
the
migration,
could
that
and
then
could
we
have
a
sentence
after
that?
That
says
administrators
are
warned
if
the
node,
if
they
change
a
node
name
to
maybe.
B
Everybody
writes
that
way
and
then
yet
it's
an
editing
job
but
wait
a
minute,
but
it
you
got
warnings
in
both
directions.
A
B
Go
back
to
the
text,
I'm
almost
wondering,
but
god
do
we
even
need
to
put
the
ones.
Do
we
or
just
say
that
administrators
are
warned
if
they
use
a
label,
that's
wrong.
B
A
A
A
Right,
that's
that's
the
idea!
So
what
we
just
completed!
Thank
you
for
your
patience
with
this
was
we
have
successfully
compressed
four
things
into
one?
The
way
tim
had
asked,
so
that's
great
uh-huh,
okay,
so
I've
got
to
do.
I've
got
to
do
some
more
rework
of
this
before
submitting
it
sorry
that
I've
burned
all
of
our
time
on
this
one
topic,
we've
got
other
topics
on
our
list.
Do
we
want
to
what
were.
A
B
A
To
have
tim
jacom,
one
of
the
maintainers
of
the
plug-in
installation
manager
yeah
on
on
the
platform
signating
last
week
and
asked
him
hey
here's
this
large
pr.
How
would
you
like
it
and
tim's
guidance
was
hey
concepts
and
maybe
a
few
simple
use
cases
should
be
on
www.jenkins.io,
but
the
bulk
should
go
on
to
the
into
the
the
actual
readme
of
the
of
the
repository,
because
it's
it
needs
to
travel
with
the
code,
okay
and
and
that
pull
request.
I
think
you
remember
it
that
we
had
looked
at
it's.
A
It's
got
lots
of
deep
information,
but
the
danger
is
if
it's
on
jenkins
jenkins.io
on
www,
it
will
get
out
of
date
as
the
plugin
is
updated.
So
if
we
put
it
into
the
readme,
it's
closer
to
our
plugin
as
the
tool
is
updated.
So
so
I
think
he's
right
and
I
intend
to
rework
it
to
eventually
close
that
pr
and
submit
it
as
a
pr
to
the
to
the
to
the
plug-in
required
to
the
tool
repository
right.
C
C
Bring
up
a
really
interesting
point
about,
and
I
do
agree
that
we
usually
keep
our
documentation
like
living
close
to
the
plug-ins
and
stuff.
B
C
A
Right
well,
and
maybe
maybe
what
we
do
is
something
like
ask.
Okay,
this
is
this
is
sort
of
a
one-of-a-kind
right
now
there
aren't
many
other
things
like
this,
which
are
command
line
tools,
but
we
could
always
ask
gavin
mogan:
hey.
Could
we
find
a
way
to
act
as
though
plug-in
installation
manager
was
a
plug-in,
even
though
it's
not?
C
C
Exactly
no,
no
I'm
just
trying
to
think
if
there,
if
there's
like
a
easy
way
for
us
to
be
able
to
kind
of,
I
guess
the
easiest
way
for
us
to
do
it
now
is
to
just
have
a
this
is
a
very
basic
something
that
will
probably
never
change
like
how
to
use
the
tool
and
then
for
more
details.
Please
see.
Thank
you.
A
C
A
That's
it,
and
certainly
we
we
have
that
potential.
If
we
were
to,
if
we
wrote
the
plugin
installation
manager
docs
in
asciidoc,
we
could
pretty
trivially
trivially
slurp
it,
but
right
the
other
is.
I
think
we
may
want
to
put
basic
use
cases
scattered
in
multiple
locations,
because
we
need
this
same
thing
for
docker.
We
need
it
for
kubernetes.
A
C
B
B
All
these
sample
file
snippets
and
then
it
there
is
a
whole
demo
or
something
there
is
a
whole
directory
or
on
the
plugin
site
or
on
the
github
site
for
stuff.
But
it's
but
I'm
looking
the
snippets
that
are
on
the
file,
I'm
pretty
sure
like
slave
shows
up
a
couple
of
times,
so
those
are
probably
out
of
date
right.