►
From YouTube: 2022 01 24 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
Welcome
to
jenkins
documentation,
office
hours,
it's
the
24th
of
january
reminder
that
we
abide
by
the
jenkins,
go
to
conduct
great,
to
have
meg
here
and
we'll
add
other
attendees
as
they
arrive
so
topics
on
the
agenda.
For
today,
news
review,
the
weekly
changelog
poll
request
open,
pull
requests
and
there
are
several
that
meg's
done
pre-review
on
and
then
I
think
we
may
have
one
other
topic,
which
was
the
let's
see
improve
a
plug-in
pull
request.
A
I
haven't
made
nearly
enough
progress
on
it,
but
that
feels
like
a
good
one
and
then
I
think
we're
settled
we
need
we
need.
We
have
some
action
items.
Maybe
I
should
put
a
section
for
action
items
here,
because
I'm
behind
on
my
action
items,
okay,
one
of
them
is
action
items
is
that
create
the
community.jenkins.io
post.
C
Yeah,
do
we
have
anything
else
with
gsoc
or
she
code,
africa.
C
A
A
Okay,
great
all
right,
so
let's
talk
news
first,
so
there
are
15
or
so
plug-ins
that
have
been
suspended
from
distribution
or
will
be
suspended
within
a
day
or
two.
These
are
plug-ins
that
rely
on
the
relatively
non-standard
jruby
based
run
time
that
was
created
many
years
ago
in
the
jython
run
time.
A
C
A
C
A
C
Yeah,
but
not
over
just
dropping
j
ruby.
There
hasn't
been
anything
no.
A
No
it's,
and
even
if
there
was
there's
truly
nothing
we
can
do
about
it.
If
someone
wants
to
bring
a
lot
of
engineering
skill-
and
I
mean
jesse
glick
worked
on
that-
so
that's
the
keller
engineering
skill
you'd
have
to
bring
so
no
it's.
It's
not
changing
all
right.
Next
topic:
lps!
Oh,
go
ahead!.
B
I'm
sorry
to
interrupt
so
I
I
realized
that
I
think
I
can
discuss
more
about
plug-in
health
score
project
as
well
little
bit
more
good.
A
A
The
project
will
choose
the
next
baseline
for
the
march
2022
lts,
and
it
looks
to
me
like
331
that
was
released
last
friday
or
332
due
to
release
tomorrow
are
the
most
likely
candidates.
A
B
A
A
great
discussion
to
have,
and
thanks
to
every
lemur
there
is
a
whole
bunch
of
chapter
headings
on
this
thing
that
if
you
hover
in
the
right
place,
I
forget,
if
you
look
at
these
things
down
here
or
hover
someplace
along
here,
it
will
actually
show
here.
It
is
here,
are
the
chapters
and
these
chapters
give
you
titles
for
the
the
sub-sections?
A
C
A
Good
question
doc's
update
reviews.
A
A
A
A
So
so
good
good
question:
we
could
that's
one
where
we
could
consider
she
code
africa
project
to
review
the
documentation
for
outdated
screenshots
right
I
mean
that's
something
that
would
be
a
real
help.
A
C
B
A
C
A
All
right
next
next
piece
of
new
news
of
news
is
that
infrastructure
issue
tracking
has
now
moved
to
jira
from
jira
to
github
issues.
So
there's
a
repository
called
help
desk
and
this
repository
has
in
it
the
jenkins
infra
issues
and
we're
seeing
all
sorts
of
positive
side
effects
from
this.
So
I
submitted
a
request:
hey
we
need
to
use.
A
We
need
to
use
the
latest
jdk.
They
just
released
it
a
few
days
ago
and
guess
what
it
gives
us
an
automatic
link
into
somebody
else's
tool
where
they
track
this,
and
you
see
that
this
is
the
eclipse
project,
that's
building
it
and
now
we're
coupled
to
each
other.
So
a
jenkins
issue
is
mentioned
in
their
issue.
Tracker
big
win.
A
B
A
A
That
will,
let
me,
for
instance,
say:
hey,
here's
a
documentation
issue
and
it
has
forms
built
into
it.
That
will
let
me
prompt
for
exactly
what
we
need.
Okay,
the
the
thing
that's
affected
is
cia
get.jenkins.io,
and
it's
affected
this
way,
and
this
kind
of
has
this
has
improved
the
quality
of
issues
we're
receiving
from
people
who
are
reporting
it,
and
it
doesn't
require
that
they
have
a
jenkins
dot.
Io
account,
oh
cool,
so
so
no
need
to
go,
get
an
account
in
order
to
report
a
bug.
A
Okay
yeah.
So
next
topic
for
this
friday's
platform,
special
interest
group
I'll
be
bringing
a
draft
of
the
java
8
end
of
life.
Jenkins
enhancement
proposal
haven't
started
it
yet,
but
I
got
to
get
it
ready
for
then
the
right
now
the
idea
is
either
june.
2022
or
september.
2022
lts
release
will
drop
java,
8
support.
A
C
A
A
Okay,
next
news
item:
this
is
the
long
news
section,
sorry
for
being
so
long
and
boring
here.
Internet
explorer,
11
official
end
of
life
from
microsoft
is
june
of
2022.
A
A
D
C
A
A
A
C
B
Yes,
so
I
had
some
doubt
about
this
topic
and
I
asked
in
the
community.jenkins.io
for
this
project
and
jake
was
very
kind
enough
to
explain
it
to
me
in
depth.
So
I
understood
the
idea.
I
just
wanted
to
see
if
you
have
anything
else
to
add,
so
my
understanding
of
this
project
is
if
we
want
to
create
the
end
goal,
is
that
in
the
plugins.io
site
there
will
be,
as
we
know,
we
get
some
small
tabs
for
each
plugin.
B
So
on
each
tab
of
a
plugin,
there
will
be
a
section
like
a
score
which
will
be
there
to
signify
how
healthy,
let's
say
a
plugin
is
so
and
that
will
be
calculated
calculate
based
on
some
factors
that
can
be
picked
from
the
contributing
to
the
open
source
document
and
and
the
project
I
think,
just
stops
there.
We
will
not
be
attempting
to
solve
it
by
ourself.
B
It's
just
a
way
to
show
the
developers
or
users
that
how
healthy
a
plugin
is
and
it
how
much
help
it
needs
from
the
users
or
developers.
That's
it
right.
A
A
It
could
instead
be
some
sort
of
a
score
or
a
a
letter
grade
or
a
numeric
or
a
pie
chart,
or
you
know
some
hint
some
indicator
hey.
This
is
how
good
or
healthy
or
unhealthy
this
thing
is,
and
then
what
are
the
things
that
get
involved
in
deciding
how
healthy
something?
Something
is
things
like?
Is
the
plugin
up
for
adoption?
Okay,
that's
less
healthy
than
if
it's
not.
A
A
B
Yes,
so
this
process
of
calculating
the
score
will
be
fully
automated
right
for
all
the
plugins
right.
Okay
right!
So
do
you
have
any
specific,
like
not
specific,
any
rough
idea
like
how
we
can
achieve
this
kind
of
any
technology,
as
suggested
by
bazel
as
well.
We
can
use
refaster
to
automatically
change
the
code
based
on
some
pattern,
something
like
that.
A
A
A
C
A
A
C
A
B
A
But,
but
showing
a
demonstration
of
it,
I
think,
is
a
cool
idea.
It's
like
hey.
This
is
here's
something
that
that
went
very
rapidly.
Somebody
put
together
very
quickly.
That
gives
us
a
high
level
view,
and
it
already
highlights
some
things
about.
Oh
wow,
I
didn't
expect
that
plug-in
to
be
red.
Why
is
that
plug-in
red
based
on
the
scoring
algorithm.
B
A
Exactly
yeah,
so
now
one
of
the
things
that's
been
requested
is
if
they
would
like
that,
it's
it's
extensible
by
others,
so
that
if
someone
wants
to
add
their
own
attributes
and
use
it
for
scoring,
that
would
be
a
preferred
thing.
I
I'd
like
to
add
the
following
additional
attributes
and,
and
they
may
not
be
suitable
for
the
the
general
display,
but
more
for
some
specific
need.
Somebody
has
inside
their
company
or
in
some
other
place.
A
B
A
A
Exactly
well
and-
and
I
could
even
see
potentially
things
like
hey-
I
want
a
multi-attribute
score.
I
don't
want
to
simplify
this
to
a
simple
color
or
to
a
simple
letter
grade.
I
want
something:
that's
got
more
attributes
than
that
because
there
may
be,
I
may
say,
look
I'm
giving
this
thing
an
f
in
security
and
an
a
in
these
other
things.
A
A
B
A
A
A
A
C
Oh
and
fold
into
some
of
your
test
coverage
numbers
that
you've
got
mark.
A
B
B
A
B
A
C
Was
thinking
we
seem
to
have
some
people
there
that
are
interested
not
in
coding
and
not
in
documentation,
but
in
project
and
product
management,
and
you
put
in
a
tremendous
amount
of
work
running
she
code
africa
last
year
and
it
may
be
worse
this
year.
Had
you
thought
about
taking
on
sort
of
the
equivalent
of
a
ta
or
an
assistant,
and
you
could
maybe
I
mean
I
don't
I
think.
Oh,
you
could
save
market
time.
B
C
But
you
could
go
over
with
them.
You
know
deciding
the
agenda,
how
you
decide
what's
in
the
agenda,
possibly
even
by
later
in
the
project,
we
might
have
some
meetings
that
you
let
them
run
with
you
they're.
You
know
ready
to
take.
You
know
you
have
like
the
driver
instructor
that
has
their
own
set
of
controls,
that
they
can
grab
control
of
the
car
fast.
C
But
that's
what
I
mean.
It's
a
legitimate
need
and
there's
some
people
who
seem
pretty
interested
in
getting
involved
in
this.
That's
their
interest,
and
I
wondered
if
that's
something
I
mean
that
really
becomes
a
question
for
you
because,
but
it
one
thing
too
might
be.
Like
I
know
last
time
one
of
the
disasters
was
having
me
run
some
of
the
meetings
I
mean
everybody
wanted
mark.
C
A
That's
I
I
think,
that's
an
interesting
idea
so
that
that
sort
of
reshapes
the
concept
as
hey,
look
we're
going
to
do
an
entire
project
and
we're
going
to
have
one
of
your
people
be
a
mentored
project
manager
and
others
will
be
the
developers
on
it.
Maybe
others
are
the
documentation
writers
for
it.
Yeah
interesting.
C
B
C
A
C
A
C
A
I
mean
we,
I
guess
we
could.
Should
we,
let's
take
a
different
same
angle.
Should
we
invite
someone
to
be
a
mentored
tester.
C
C
A
C
Code
or
something
I
mean
it's,
you
know
I
I
kept
forgetting
there
that
the
point
the
the
goal
of
this
project
was
not
to
improve
jenkins.
C
Okay,
mark
click
on
the
first
one,
it's
our
old
favorite,
okay,
daniel's
been
looking
at
it.
I
I
really
for
the
rest.
I'm
gonna
have
less
time
to
devote
to
jenkins
in
a
few
weeks.
So
I'd
really
like
to
get
this
one
done
and
the
preview
the
last
time
I
checked.
Yes,
the
preview
is
good.
C
We
have
a
couple
of
things
that
have
shown
up
and
I
realized
for
remind
the
the
reason
we
started.
This
was
first
of
all,
I
was
sitting
on
a
whole
bunch
of
information
that
I'd
gotten
from
daniel
some
years
ago
for
another
purpose
that
wasn't
here
and
wanted
to
get
that
captured
before
it
get
like,
because
I
thought
it
was
good.
The
other
one
was
that
daniel
wanted
one
place
where
he
had.
C
And
so
then
I
started
thinking
that
we
were
going
to
pull
everything
into
this
chapter.
Well,
we're
not
so
what
we've
ended
up
with
is
the
list
on
the
left
is
way
too
long.
We
may
not
be
able
to
do
anything
about
that
if
you
scroll
down
here
mark
this
is
the
index.a
doc
file.
I've
got
a
list
of
everything,
that's
over
there
in
the
left
and
that's
where
daniel
first
said
this
is
too
long.
C
Okay,
now
what
I
see
is
and
then,
when
I
looked
at
it,
it's
like
yeah
the
I'll
go
back
up
to
the
top.
The
topic
here
is
the
global
configuration.
I'm
sorry
scoot
a
little
bit
down
where
we
go.
C
Configure
global
security
now
to
me,
what
I
want
is
I
want
a
place.
That's
a
big
screen
that
I
can
go
and
it's
going
to
go
item
by
item
and
tell
me
what
it's
for
and,
if
there's
something
more
to
be
said,
give
me
a
link
to
it.
The
next
several
sections
are
all
within
that.
C
Words
if
we
had
a
third
level
heading
I'd,
put
them
underneath
there,
since
we
don't
what
I'm
thinking
is
that
all
of
that
other
stuff
should
be
pulled
out
and
it
will
show
up
in
the
global
security,
but
all
those
links.
Now
that
means
that
the
chapters
would
show
in
the
left
frame
and
would
not
be
discussed
here,
but
everything
down
through,
I
think,
csrf
protection,
I
think
rendering
units
user
countdown.
I
can't
remember,
but
most
of
those
would
disappear
from
this
listing,
but
they
would
still
be
in
the
left.
A
Okay,
so
the
so
this
this
then
becomes
a
higher
level
view
of
think
about
these
things
and
not
just
a
a
copy
of
the
table
of
the
contents,
with
good
descriptions
of
the
of
the
chapters
that
are
there.
C
Going
to
be
very
brief
because
the
meat
will
be
in
the
pipeline,
but
it
will
be
a
place.
We
can
look
here
and
see
what
have
we
flagged
and
what
are
we
linking
to,
and
you
know
to
check
it
going
forward
and
to
make
it
because
mark
because
we're
all
the
old
structured
like
daniel
said
when
he
had
something
new
to
add
it
was
hard
to
add.
He
had
to
you
know,
trip
over
the
structure
trying
to
find
the
right
place.
C
A
A
A
A
C
A
A
C
That
are
on
and
that's
enough
that
this
is
what
jenkins
does
to
protect
you
and
and
then
they
go
on,
and
also
this
actually
reads
because
this
whole
thing
begins
with
a
talk
about
the
distributed
process,
and
you
know,
keeping
your
agents
and
your
control
separate
from
your
controller
is
a
good
thing
and
then
we
say,
but
we
got
one
more
thing
and
then,
and
I've
already
modified
it,
even
though
it's
not
yet
released
so,
but
you
like
being
ahead
of
it,
the
the
note
down
there
says
releases
prior
to
right
after
a
week
of
reading
through
all
of
the
stuff
where
we
say
we're
changing
this,
it's
like
no,
it's
already
changed
now.
C
C
D
A
C
And
then
we
could
actually
make
this
chapter
just
be
security
principles
rather
than
background
concepts
which
is
kind
of
a
weak
title.
Anyhow,.
A
C
C
Okay
and
we
can
scroll
down
mark,
we
don't
have
to
do
it
here
in
real
time.
This
also
I'd
gotten
I'd
been
drinking
pipeline
kool-aid
and
it
was
all
about
how
it
executes
a
pipeline
and
daniel's
like
freestyle,
but
it
was
almost
the
same,
so
we
kind
of
did
it.
I
took
a
crack
at
it,
but
if
you
had
a
because
I
don't
understand
how
freestyle
execute,
I
don't
understand
freestyle
as
much
as
I
do
pipeline.
C
Okay,
okay,
that's
my
biggie!
If
we
can
go
on,
though
the
others
and
just
glance
at
them
and
see
what's
going
on
yeah.
A
Next,
sorry,
are
you,
okay
with
this
next
one,
three,
four:
zero?
Six?
Okay,
what
does
the
tag
of
chore
mean
on
this
thing?
It
means
this
so
chore
is.
Is
a
poor
poor
label
to
say,
reduces
the
maintenance
burden
or
improves
the
maintainability
of
this
thing?
It's
it's
just.
Let's
do
this
because
it
helps
overall.
A
B
A
C
D
A
B
A
Well,
that's
fascinating,
so
he's
providing.
This
is
another
style
of
the
pipeline
step
stock
generator
work.
This
is
doing
something
similar.
A
C
Okay,
go
down
to
the
bottom
of
the
comments
and
see
because
there
was
a
big
discussion
like
just
and
then
it
just.
C
A
A
So
here's
here's
the
hint
as
his
goal,
so
what
what
he
was
trying
to
do
is
get
easily
referenced,
easily
referenced
locations
that
were
constant,
where
he
could
point
to
here's.
What
the
help
says
for
this
and
and
make
those
on
jenkins
that
I
owe
instead
of
pointing
inside
the
github
repository
of
an
individual
plugin.
A
A
To
oops
to
this
okay
got
it.
D
Yeah,
because
I
was
almost
seeming
like
is
this
trying
to
solve
one
particular
problem
and
making
it
hard,
because,
as
soon
as
you
have
like,
you
know
some
type
of
documentation,
you
have
to
make
sure
it's
current
and
updated
and
just
randomly
pulling
out
all
that
deli.
Kelp
dock
that
doesn't
seem
to
make
sense
and
in
context
is
maybe
not
what
we
really
wanted
to
solve.
So
I
think
that's
kind
of
like
what
are
we
trying
to
get
like?
What
are
we
trying
to
do
to
figure
out
if
we
need
to
do
something
else?
If.
A
Yeah,
so
so
the
the
technique
he's
using
in
the
pull
request
is
he's
reading
from
the
released
the
released
stuff.
Okay.
So
what
he
does
is
he
downloads
the
released
stuff
with?
Let's
see,
let's
go
look
at
the
thing
that's
being
downloaded:
it
is
here
he
and
this
would
be
the
current
version
number.
Instead
of
that
version
number,
he
downloads
the
release
stuff
and
then
uses
that.
D
A
C
D
B
C
A
A
D
It
yeah
that
sounds
like
it
and
even
still
like
some
of
the
help
is
going
to
be
so
context
specific
or
it's
just
not
going
to
make
any
sense
whatsoever.
I
feel
like
the
only
or
like
I
think,
the
only
help
that
would
be
really
helpful
are
the
ones
where
people
write
paragraphs
explaining
like
what's
going
on
in
the
background
and
that's
why
it's
like.
A
Yeah,
the
one
that
I
was
thinking
of,
okay,
that
I
I
could
see
how
this
one
would
have
helped
me
is
unstable.
Return,
probably
has
some
really
good
verbiage
to
describe
what
the
concept
of
unstable
is,
but
is
this
that
valuable
that
I
would
want
the
other
things
cluttering
and
risking
negative
comments
and
hostile
remarks,
etc?
C
A
Yes,
and-
and
I
guess
conceptually
there
then
you
could-
we
could
even
consider-
is
there
a
way
from
the
resulting
page
to
take
them
back
to
the
source
file
so
that
they
could
propose
a
pull
request
to
the
plug-in
that
they
were
where
they
were
correcting
that
yeah?
So
that's
good
good
insight
that
this
might
be
a
vehicle
to
encourage
people
to
improve
the
online
help.
C
I
mean:
could
we
do
this
and
publish
this?
Like,
maybe
not
part
of
the
it's?
I
don't
know
you
know
some
some
place
with
daniel
anybody
else
who
wants
to
get
to
it.
A
C
D
Just
it's,
I'm
not
yeah,
so
I'm
not
really
understanding,
because
I
look
at
the
the
plugin
or
the
site.
Kind
of
is
a
little
bit
more,
maybe
level
or
some
other
stuff,
I'm
just
not
seeing
how
inland
help
is
useful
in
this
particular
case.
It
feels
way
too
close
right.
I
don't
under.
Like
I
mean,
maybe
my
thing
is
like
you
can't
just
point
them
to
if
it
isn't
its
own
file,
like
I
mean
you
could
just
point
them
to
github.
It
doesn't
really
hurt
that
bad,
but.
D
A
And
I
think
I
think
oleg's
point
is
well
taken
that
that,
if
we
need
this
a
separate
and-
and
we
have
experience
creating
those
kinds
of
separate
sites-
as
an
example
here
is
one
that
was
just
created
by
erwe
lemire.
A
C
Okay,
cool,
you
know
who
this
would
be
useful
for
we
don't
have
us,
we
don't
have
a
formal
support
organization
for
jenkins
io,
but
there
are
support
people
out
there
who
are
having
to
support
customers
who
are
using
jenkins
and
it
could
be
very
useful
for
them
in
that
regard,
rather
than
trying
to
say
go
to
this
screen.
You
know
with
three
three
levels
down
to
get
to
this
screen
and
look
for
this
block
and
then
click
the
question
mark,
and
sometimes
it's
an
obvious
question
mark,
but
I
can
see
for
some
of
these.
C
A
A
C
Right,
I
could
see
us,
I
mean
personally,
I
wouldn't
mind
seeing
that
say
something
that
we
think
oh
like.
If,
if
we
think
we
need
this,
that
oleg
suggestion
is
the
way
to
go
right
or
something.
A
A
A
C
This
is
just
a
list
and
I
didn't
see
what
you
did
shall
we
shall
I
delete
all
the
ones
we
did
not
discuss
and
just
move
them
into
the
next
agenda.