►
From YouTube: GSoC 2023 Office Hours - February 28, 2023
Description
Jenkins in GSoC project idea presentation: "Plugin health score probes" and "plugin health score visualisation"
A
So
thank
you
very
much
for
having
joined
us
in
this
discussion
will
have
will
go
the
two
projects,
one
after
the
other
I'll
give
the
word
to
Adrian
and
Jake
I.
Don't
know
how
they
organize
themselves,
so,
first,
a
presentation
of
the
project
so
that
we
get
introduced
and
then
we'll
have
q
a
session
now
in
order
that
the
maximum
time
we're
going
to
spend
on
these
two
projects
is
one
hour
so
on
the
top
of
the
hour,
so
that
will
be
10
pm.
A
B
B
So
if
you
are
not
familiar
with,
let's
start
with
the
beginners
scoring
project,
if
you
are
not
familiar
with
it,
the
idea
behind
that
project
is
to
provide
key
information
to
plug-in
maintainers,
but
also
to
plug
in
users
of
Jenkins
ecosystem
about
the
else
state
of
each
and
every
plugin.
That
is
available
on
the
Ryan
variable
in
the
update
Center.
B
The
idea
is
to
find
key
details
that
we
can
measure
and
that
we
can
assess
to
determine
whether
the
plugin
might
need
some
attention
or
is
in
good
shape
overall
or
is
in
perfect
perfect
shape
all
around
so
that
the
idea
of
the
the
project
and
concerning
it
we
have
two
ideas
for
Json.
One
is
about
adding
new
probes,
because
the
plug-in
the
the
project
is
using
two
key
feature
which
are
pubs
and
scoring
implementation.
The
pubs
are
there
to
gather
data
about
a
plugin.
B
They
are
not
here
to
make
any
judgments.
Add
the
question
quite
a
lot
on
on
guitar
and
I
thought
that
was
key
on
the
documentation,
but
my
bad,
it's
not
so.
The
the
pubs
are
here
to
fetch
data
on
key
details
about
plugins.
So,
for
example,
we
are
currently
Gathering.
We
have
a
pub
to
gather
the
number
of
installation
of
a
specific
of
a
specific
plugin.
We
have
thank
you
Jake.
We
have
a
prob.
The
jab
229
is
about
the
usage
of
set
said
jab,
which
is
a
continuous
delivery.
B
C
B
On
a
plugin
and
all
those
calls
are,
then
we
have
an
average
of
all
those
calls
and
they
they
make
the
the
score
of
a
specific
plugin.
So,
for
example,
ER
check
is
going
to
the
git
page
and
we
can
see
the
score
is
of
96
out
of
100,
because
the
plugin
doesn't
only
has
a
0.75
on
the
repository
configuration.
B
If
you,
if
we
scroll
down,
we
can
see
all
the
prop
results
for
each
of
the
probes
that
are
implemented
and
have
been
around
on
the
plane.
So
we
can
see
put
the
number
of
pull
requests.
The
Jenkins
versions,
whether
or
not
the
plugin
is
deprecated.
Sorry
for
that
the
last
commit
date,
the
jeb229
and
so
on,
and
so
on.
B
So
those
scoring
processes,
the
the
probes,
can
contribute
to
existing
scoring
scoring
implementation,
one
of
those
four
for
example,
or
they
can,
or
we
can
create
a
new
scoring
processes.
A
new
scoring
scoring
implementation
to
use
those
new
probes
to
illustrate
a
specific
apps
aspect
of
a
plugin,
so
the
for
example.
The
deprecation
scoring
implementation
is
only
using
the
deprecation
because
that
makes
sense
there.
It's
a
one
one
relationship,
but
the
scoring
the
repository
configuration
is
using
four
and
soon
enough.
B
Five
probe
results,
because
in
the
repository
configuration
we
want
to
assess
the
presence
of
Jing
inside
the
usage
of
depend
about
and
either
is,
the
usage
is
depend
about
used
correctly
and
does
the
jab
229
was
configured
on
the
repository
and
soon
we
will
also
have
courage,
and
we
will
also
have
on
that
scoring
implementation.
Contributing
guide
presence,
because
that's
part
of
the
repository
configuration
so
in
in
this
first
idea
is
mostly
adding
new
scoring
and
new
pubs.
B
C
B
So,
let's
double
that
question
for
the
second
part
of
the
meeting,
so
we
can
have
a
specific
discussion
about
the
how
we
display
the
the
scoring.
But,
yes,
we
will
have
a
specific
there's,
a
plan
to
have
different
ways
to
display
the
scores,
the
numero,
the
numeric
values
of
the
score
for
each
plugin.
B
The
value
is,
is
whether,
on
the
the
acquisition
is,
how
important
the
scoring
process
the
occurring
scoring
implementation
is
overall
for
the
overall
score
of
a
plugin.
So
we
can
see
that,
for
example,
having
a
security
issue,
not
not
yeah
having
a
security
issue
is
pretty
important
for
the
score
of
of
a
plugin,
which
makes
sense
and
having
a
good
represent.
Configuration
is
Alpha
as
important
as
the
security
issue.
B
B
If
you
get,
if
you
have
a
security
issue
or
you
get
or
you
have
a
one
out
of
one,
if
you
don't
for
the
repository
configuration,
it
depends
on
whether
the
how
many
on
yeah,
how
many
of
the
different
aspects
we
want
to
see
inside
the
Repository
are
actually
configured
inside
for
the
plugin
for
the
adoption.
It's
is
the
plugin
marked
as
adopted
yes
or
no,
and
then
we
are
evaluating
the
last
date,
the
the
the
last
the
the
time.
D
C
B
B
B
A
That's
yeah
to
shed
some
light
there
for
people
who
are
unusual
unused
to
that
process.
So
normally
security
issues
are
not
disclosed
to
give
the
time
to
the
owner
to
fix
them
and
we
give
them
an
appropriate
time
if
we
have
no
response
or
nobody
is
dealing
with
it
at
a
certain
time,
we
have
to
publish
the
security,
we
don't
explain
how
and
where
we
just
say
there
is
a
security
issue
logged
on
that.
So
this.
A
E
B
B
So
no
the
the
project
itself
live
on
its
own.
It's
separate
from
Jenkins
we
will
have
we
can
we
will.
We
have
plans
to
have
different
ways
to
display
the
score
to
users
and
to
plug
in
maintenance
either
on
the
plugin
site,
which
is
the
second
idea
of
for
this
year
Json
and
we
have
other
other
plans
to
also
display
those
scores
inside
the
the
plugin
manager.
So
on
on
the
web.
B
On
the
Jenkins
instance,
when
you
want
to
install
a
new
plugin,
that
is
called
the
plugin
manager
and
you
have
the
list
of
plugins
that
you
have
installed
or
you
have
available
in
the
update
Center
and
we
want,
and
we
have
plans
to
add
the
score
value
there
as
well.
But
the
project
itself
is
not
a
plugin
for
Jenkins,
it
has
a
separate
life
of
from
Jenkins
is
just
contributing
to
the
else
of
the
Jenkins
ecosystem.
B
C
I
have
another
thanks:
go
ahead,
yes,
so
the
weights
of
every
probe
I
mean
it
might
matter.
I
mean
it
differs
from
person
to
person
how
much
weight
a
person
wants
to
go
to
a
certain
probe
and
almost
to
another.
So
how
are
we
deciding
for
them?
So
it's
I
mean.
What's
the
decision
process
behind
the
scoring,
so.
D
D
B
Probably
no
no
I
totally
agree
with
what
you
said.
The
repository
configuration
is
mostly
good
things
to
to
have,
but
the
most
important
thing
is
a
plugin
that
is
moving
forward
and
is
which
is
which,
as
a
plug-in
maintainer
and
as
no
security
issue,
so
in
the
end
not
having
a
Jenkins
fight,
for
example,
is
not
great,
but
it's
not
a
problem
for
the
plug-in
itself.
B
D
Yeah,
it
might
help
I
mean
just
to
speak
from
the
kind
of
user
or
product
perspective
here
about
the
goals
that
we
wanted
to
accomplish
with
this
project
right,
obviously,
the
overarching
goal
is
we
want
users
to
get
better
plugins
right.
We
want
users
of
Jenkins
to
have
quality
plugins
and
we
want
to
help
them
make
decisions
when
picking
a
plug-in
to
use
right,
because
currently,
without
these
scores
it
takes
a
good
a
good
hour
out
of
your
day
right.
D
So
we
want
users
to
have
better
plugins
and
we
want
them
to
make
be
able
to
make
decisions
quicker
and
easier
right
about
which
plugins
to
install
right.
You
go
and
look
for.
You
know
kubernetes
plugins,
there's
seven
of
them,
don't
which
one
do
I
use
which
one's
good,
which
one
you
know.
Obviously
this
doesn't
answer.
You
know
anything
functionally
related
if
it's
functionally
going
to
do
what
you
want.
D
So
there's
still
a
little
digging,
but
then,
of
course
the
the
second
part
is
we
want
to
help
maintainers
make
better
plugins
right
and
a
lot
of
the
times
whether
you
know
you
just
adopted
a
plug-in
and
you
just
became
a
new
maintainer.
This
can
serve
as
a
little
guidance
as
to
okay.
What
can
I
do
to
make
this
plug-in
better
I
maintain
this
plug-in
and
I
just
got
a
65
out
of
100
right.
D
B
To
say
this
is
already
implemented,
but
I,
don't
I,
don't
I,
don't
think
this
is
the
correct
way
to
implement
it.
Okay,
let's
explain
us
why
in
The
Proposal
and
we
we
can
have
a
discussion.
That's
for
sure,
if
you
have
other
ideas
of
probs
things.
That
seems
interesting
to
you
that
that's
also
welcome.
But
you
are.
We
already
have
some
ideas
that
are
listed
on
the
page.
B
A
To
add
a
little
detail
here,
I
strongly
recommend
that
people
interested
in
their
watch
very
carefully
the
series
of
videos
that
were
made
about
modernizing
a
plugin
I
think
it's
referenced
somewhere
here,
but
it
this
is
a
good
reference.
So
you
you
know
what
are
the
things
to
look
for
anyway?
You
did,
you
can
go
ahead.
B
E
B
B
We
can
schedule
them
thanks
to
that
not
scheduling
the
time,
a
timely
manner,
but
in
the
order,
how
they
execute
one
after
the
other,
and
so
the
pop
code
is
really
short
most
of
the
time
here,
for
example,
for
the
just
for
the
jab
two
to
nine,
so
we
are
checking
the
presence
of
a
specific
file.
How
do
we
know
which
file
to
check
it's?
B
Basically,
you
read:
you
read
the
jap229
documentation
and
you
you
see
that
inside
the
GitHub
dot
GitHub
workflows
for
file
folder,
you
have
a
CD
style,
a
CD
workflow
on
on
the
for
Jenkins,
and
so
basically,
what
we
are
doing
is
just
we
have
a
repository
of
code.
We
are
looking
inside
the
repository
whether
there
is
a
GitHub
workflows,
folder
and
inside
that
folder.
We
are
checking
whether
or
not
we
have
the
specific
file.
B
So
that's
how
it
works
for
that
one.
If
we
look
at
another
one,
for
example,
let's
the
known
security
vulnerability,
it's
a
bit
a
bit
more
complex
the,
but
you
see,
even
though
it's
a
bit
more
complex,
it's
still
short
because
the
code
of
the
prod
is
those
are
those
lines
and
only
those
lines
the
others
are
just
decorative.
B
B
If
it's
not
applied
to
the
current
version
of
the
plugin,
which
means
the
latest
version
available
on
the
update
Center,
it
means
the
plugin
doesn't
have
an
active
security
warning.
So
there's
no
security
issue
on
that
plane
doesn't
mean
they
never
was.
It
just
means
that
the
latest
version
of
the
plugin
don't
have
doesn't
have
any,
and
so-
and
in
that
case
we
we
just
say
if
we
don't
find
any
any
issue,
it
means
it's
fine.
E
B
A
D
Of
course,
I
think
this
one
is
a
little
bit
less
complicated,
I
hope,
but,
as
you
know,
we
have
the
plug-in
Dash
Health
site
to
go
check
individual
plugins
and
things
like
that.
However,
we
want
to
make
these
scores
more
apparent,
more
digestible
by
end
users
and
maintainers
like
so
one
of
the
ideas
is
to
display
the
scores
on
plugins.jenkins.io.
Currently,
if
you
go
there
and
check
out
a
plug-in.
D
We
notice
there's
quite
a
bit
of
late
wasted
space
on
these
cards
and
we
think
with
the
wireframes
that
we'll
go
through
in
a
second.
This
would
be
a
great
place
to
display
the
health
scores
of
said
plugins,
and
that's
what
you'll
see
in
this
wireframe
here
you
know
fit
with.
You
know
filtering
based
on
those
scores
right
and,
of
course,
some
explainers
as
to
how
the
scores
are
produced,
and
you
know
what
goes
into
the
scores,
the
different
probes
and
all
that
stuff
right.
D
From
here
right,
you
know
it
has
16
pull
requests.
The
Jenkins
file
is
found
all
that
good
stuff.
The
details
of
helping
people
understand.
You
know
the
importance
of
the
scores
at
a
valuable
score.
What
goes
into
the
score?
We
want
to
provide
that
in
the
details
of
a
plug-in
when
you
go
here,
so
you
can
see
in
this
wireframe
it
lists
out
essentially
what
we
have
on
the
page
there.
The
details
of
the
probes,
the
individual
probes
and
I
think
that
is
the
scope
of
this
project.
D
There's
other
things
we
would
like
to
do,
but
I
think
for
the
scope
of
this
project,
we'll
leave
it
here
at
the
displaying
the
scores
of
plugins.jenkins.io,
so
essentially
the
more
I
think
of
it,
converting
the
plug-in
Health
site
that
we
have
right
now
into
viewable.
Information
on
plugins.jenkins.io
did
I
miss
anything
Adrian.
B
No,
the
the
I
would
just
add
that
the
contribution
to
that
idea
would
be
partly
on
the
plugins
else
scoring
repository,
but
also
on
a
note
on
one
or
two
other
repository
on
GitHub,
which
are
the
plugin
site
and
pluginsight
API,
which
are
the
projects
that
are
used
to
generate
the
data
for
the
plugin
site
API
and
the
plugin
sites.
A
repository
is
the
where
the
UI
is
made
for
the
plugins.jenkins.io,
so
in
in
that
project
idea,
yeah
contribution
will
be
in
two
different,
three
potentially
three
different
places.
B
B
B
Plugins
else
scoring
project
because
we
have
API
or
we
can
have.
We
can
create
new
apis
to
be
able
to
see
score
or
to
have
a
score
representation
of
a
plugin,
or
we
can
say
no
that's
the
problem
of
the
plugin
site
API
and
then
it
means
that
the
plugin
site
API
will
have
to
communicate
with
plugins
else
scoring
before
being
able
to
propose
the
data
to
the
UI
part
of
the
project.
C
Yeah,
that
is
answering
my
question,
so
I
have
another
which
is
linked
to
this
question,
so
I
explored
the
plugin
site.
The
repository
and
I
also
contributed
to
it.
So
I
found
one
thing
that
the
plugins
are
coming
from:
algolia,
which
is
the
search
engine
for
that
site,
and
so
what
I
am
guessing
is
happening,
that
the
plug-in
side
API,
is
feeding
algolia
and
from
there
the
data
is
coming,
so
am
I
right
or
I'm,
not
able
to
I'm.
C
C
B
D
F
E
Test
the
difficulty
of
this
project-
I
guess
this
should
be
beginner
level
right
or
what
else
do
I
need
to
learn
like
I
I?
Think
according
to
me,
this
project
has
the
difficulty
of
beginner
level
and
am
I
correct
or
do
I
need
to
learn.
Most
of,
like
you
said,
the
data
analysis
from
data
and
data
representation
in
all
the
skills
part
where
I
need
to
learn
right,
take
you're
getting
me
know:
okay,.
B
E
According
to
me,
I
don't
have
much
knowledge
about
it
right
now,
but
I
think
the
difficulty
for
this
project.
You
might
be
beginner
level
or
is
it
intermediate?
What
do
you
think?
Because,
according
to
what
the
required
skill
sets
and
knowledge
is
written
on
the
site
now,
according
to
me,
I
Java
is
fine.
I
know
core
Java
I've
worked
on
it
in
professional
piece.
Second
part
they
use.
Can
you
open
that
screen
where
the
task
is
fixated.
E
All
right
data
analysis,
I,
don't
this
might
be
a
big
week.
Can
you
explain
what
part
of
data
analysis
we
are
expecting
here
like
just
that
one
another
getting
data
from
gate
repositories
and
showing
it
over
here
doing
the
all
doing
all
that
process
and
showing
the
plug-in
Health
score
over
here?
That
is
the
only
part
of
the
data
analysis.
Now
or
is
it
something
else
I'm
missing.
B
E
F
F
D
A
C
B
On
on
the
API
part,
either
it's
inside
plugins
sites,
API
or
not
I,
wouldn't
say
that
fetching.
The
data
is
part
of
what
I
would
call
data
analysis,
but
once
you
have
the
data
on
the
UI,
then
you
can
have
some
Implement
in
interpretation
of
it
for
the.
If
you
scroll
just
a
little
bit
Jake,
we
can
see
on
this
on
when
you
go
to
a
specific
plugin
and
else
of
that
specific
plugin.
B
A
C
B
D
B
F
F
Definitely
a
good
sign,
because
the
project
is
very
interesting
and
since
we
started
this
last
year,
the
idea
is
extremely.
You
know
creative
and
very
useful
as
well.
Since
we
got
to
know
now,
all
of
us
know
about
it
the
description
of
what
how
we
are
going
to
be
helping
who
we
are
going
to
be
helping.
F
Even
now,
and
after
the
project,
I
still
contributed
a
few
I
think
one
or
two
pull
requests
and
it's
because
I'm
also
doing
full-time
job
so
trying
to
balance
things
but
I'm
extremely
interested
to
be
part
of
this
project,
even
now
and
in
future
as
well,
because
the
reason
is
same
as
I
said
when
I
started
speaking
is
that
this
project
is
extremely
interesting
and
it
has
a
very
bright
future.
So
this
is
why
I
came
back
this
year
as
well,
just
to
help
Adrian
and
Jake.
F
Just
to
you
know,
help
with
any
questions
that
any
potential
contributors
might
be
having
or
anything
that
I
can
be
of
help.
So
that
is
what
my
aim
is
to
be
here.
So
if
you
have
any
questions
as
a
potential
Mentor,
sorry
potential
contributors
then
feel
free
to
reach
out
to
us
on
the
geta
channel.
We
would
be
very,
very
happy
to
help.
A
A
This
was
have
saved
quite
a
lot
of
energy,
just
to
have
a
simple
dashboard
to
know
when
you
have
to
do
as
a
system
administrator.
The
decision
can
I
use
this
plugin
plugins
is
the
power
of
Jenkins
it
it
brings.
It
really
creates.
Jenkins.
Jenkins
is
a
butler
that
serves
artifacts
serves
things
and
the
plugins
are
key
to
that.
It
serves
features
provided
by
plugins.
A
A
D
You
know
we
want
more
probes
right,
as
John
Mark
said,
to
to
Beef
It
Up,
because
the
last
thing
we
want
is
no
faith
or
a
loss
of
faith
in
these
numbers
right,
I
think
having
them
get
a
wide
array
of
data
points
only
feeds
to
its
power,
but
to
its
credibility
as
well
right.
We
want
people
to
trust
these
numbers
and
we
want
people
to
to
put
some
weight
behind
it
right
and
then
actually
have
some
value.
So
that's
important
part
of
this.
C
B
Promoted
published
by
the
community,
it
needs
to
be
inside
the
Jenkins
CI
organization
in
Gita.
That
is
not
true
for
all
plugins,
there's
old
plugins,
where,
when
that
rule,
wasn't
applied
or
wasn't
followed
very
carefully,
some
plugins
are
located
outside
of
the
Jenkins
CI
organization
in
GitHub,
but
overall
all
plugins
are
in
GitHub
and
and
normally
inside
the
organization.
B
Just
to
put
some
light
on
well
measurement
on
what
you
just
said.
We
are
not
only
looking
at
the
source
code.
So
not
all
the
probes
are
about
the
repository
some
which
are
not
implemented
and
are
in
the
idea
to
list
the
number
of
tickets
or
issues
for
plugin
that
are
open
and
that
is
potentially
in
GitHub,
but
also
potentially
in
in
the
jira
in
issues
the
Jenkins,
the
type.
B
D
Yeah
yeah
I,
like
to
think
of
it,
yeah
like
in
two
two
buckets
right
that
things
really
fall
into
the
ones
on
the
coat
side
right
in
the
repository
side
and
then
one's
more
on
the
maintainer
side
of
things
or
the
activity
side
of
things
related
to
the
people
involved.
Right.
There's
two:
two
kind
of
buckets
that
we're
looking
at
and
yeah
getting
data
from
more
places
will
will
only
be
helpful.
A
A
So
you
need
to
show
that
you
understood
the
problem.
You
come
with
experience
or
with
ideas
or
novel
ideas
that
you
have
a
good
grip.
What
we
will
be
looking
at
during
the
month
of
April
is
what
are
what
is
the
likelihood
that
contributors
have
to
complete
the
project
in
the
assigns
time
in
eventually
achieve
stretch
goals,
or
so
it's
not
limited
to
just
the
initial
scope.
A
A
Experience
has
shown
that
the
sooner
you
start
working
on
that
document
and
making
the
document
available
for
review
the
better,
because
once
you've
submitted
the
document,
if
the
mentors
the
mentors
are
going
to
review
all
the
documents,
so
all
everybody
I
will
read
all
the
documents
if
at
that
moment
that
I
don't
understand
what
this
contributor
wanted
to
share
he's
not
making
his
point
correctly
or
he
could
have
presented
it
another
way.
Then
it's
too
late
and
you
missed
the
the
opportunity
so
make
your
document
available.
A
A
Okay,
I
I
had
one
minute
so
I
need
to
check
my
my
clock
here
so
I'm
I'm,
sorry
I'm,
going
to
conclude
here
this
very,
very
interesting
and
fruitful
meeting.
Thank
you
very
much
everybody
to
have
attended
for
the
very
good
questions
and
I'd
like
to
thank
you
also,
Adrian
and
Jake
and
adiraj
for
their
explanations
and
being
there
to
to
support.
A
So,
let's
go
if
necessary,
on
Project
level,
you
can
organize
other
online
meetings.
So
I
will
not
organize
always
are
we
had
this
startup
meeting
here
so
request?
Organized,
don't
forget
everything
is
public,
no
one-to-one
communication.
We
want
to
be
fair
with
everybody.
It's
a
competition.
Okay,
we're
good
thank.