►
Description
GSoC 2020 - REST API Specification Generator Project Discussion. https://jenkins.io/projects/gsoc/2020/project-ideas/automatic-spec-generator-for-jenkins-rest-api/
A
Okay,
I
started
recording
so
just
in
case
you're
watched
online.
We
are
recording
interest,
we
think
about
another
state,
PA
specification
generator
project,
it's
one
of
google
Summer
of
Code
2020
projects
and
right
now
we
have
a
number
of
potential
mentalists
and
potential
students
on
the
call.
Christine
will
be
driving
this
discussion
and
to
answer
any
questions
by
students.
B
B
B
A
A
A
The
library
swim,
but
we
should
have
couple
more
but
suppose
to
be
the
factor,
many
kisses
and,
for
example,
if
you
go
to
Jenkins
repository
or
too
many
plugin
repositories,
you
can
find
one
notations
like
exported
there,
and
here
you
can
see
that,
for
example,
that
is
take
something
easy.
So
there
is
a
whole,
my
page
where
you
can
go
and
just
see
details
about
your
user.
So
here
you
can
see
that
there
are
some
information
provided.
A
A
A
Yeah
it
so
it
was
just
keys.
So
here
you
can
see
that
I
get
some
details,
like
name
insulted
kid
authorities,
so
this
information
is
not
the
billikin
generated
projects
automatically.
That
is
page
rendering
for
that.
But
there
is
Trista
k,
and
this
is
good
REST
API,
where
you
can
receive
some
additional
permission:
I
click,
JSON
API,
and
here
you
can
see
some
information,
so
you
can
see
that
basically,
there
is
a
bunch
of
groups
being
pulled
from
my
github
account
I,
believe
that
is
nothing
secret
in
there.
A
So
there
is
a
bunch
of
authorities:
I
can
use
for
security,
the
result,
unification,
etc.
So
this
information
is
being
generated
by
step
there.
So
this
step
pleasure
it's
just
a
framework
for
data
binding
and
other
things,
and
really
it
uses
fermentation
processes
to
provide
you
this
information.
So
these
exports
and
allocations
didn't
get
processed
and
exported
to
rest
API.
So
as
a
developer,
for
example,
if
you
wanted
to
generate
specification
for
this
particular
dress
today,
you
could
have
gone
through
these
notations
using
says.
A
A
Here,
for
example,
do
description,
oh
yeah,
what's
in
the
description,
so
this
is
a
magic,
each
ourselves
ourselves
the
job
description
here.
You
can
see
that
basically,
it's
a
vegetable
in
point,
but
depending
on
what
you
sent
and
get
or
post
you
will
get
different
results.
So
forget
it
returns
your
information
for
post.
It
just
asserts
of
information,
so
we
could
go
to
a
page
in
vogue.
This
end
point
and
then
get
this
description
and
again
it
still
qualifies
as
a
part
of
rested
in
Jenkins
or
some
other
notations
are
the
use
kisses.
A
But
this
part
of
the
logic
is
quite
complex
and
it
may
require
a
lot
of
analysis
or
maybe
a
redesign
of
how
Jenkins
annotations
work,
because
it
might
be
acceptable
for
this
project
come
up
with
a
proposal
which
says:
okay,
let's
do
an
addition
for
this
rest.
Api
calls.
If
you
want
to
get
them
generated
automatically,
they
will
be
additional
requirements,
but
right
now
it's
quite
a
straightforward
things,
just
in
handle
by
step,
they're
independent
on
many
assumptions.
C
C
A
Just
short,
okay,
so
you
can
produce
rotations
using
access
pose
and
we,
if
you
explore
hijinx
rest
api
documentation.
That
is
a
bunch
of
them,
for
example,
for
other
things
like
one.
I
present
it
to.
Please
do
something
what
you
could
do.
You
could
just
process
how
stapler
code
otherwise
be
fixed,
because
you
can
find
a
lot
of
things
there.
A
We
can
always
see
some
additional
code,
for
example
dispatcher
code.
We
shall
basically
processes
at
request
and
mapping
them
to
objects,
so
you
can
see
how
it's
being
handled
there
and
try
to
reverse-engineer
that
and
probably
replace
and
bits
of
this
code
to
specification
generator,
but
it
might
be
just
a
second
part
of
the
project
because
just
reporting
get
EP
is
these.
Notations
would
be
good
first
step.
B
A
So
step
little
space
bridge
framework,
so
it
translates
say:
okay,
excellent
anyway,
yeah.
There
is
no
really
reading
in
this
repository,
but
the
eastern
engine,
which
receives
requests,
so
it's
HTTP
or
HTTPS,
and
it
can
map
them
to
Java
calls
or
vice
versa.
So
if
you
take
a
look,
for
example,
a
job
here,
you
can
see
that
say,
do
submit.
A
Okay,
delete
okay,
again
the
description,
so
here
you
can
see
that
the
stapler
requests
that
response
and
other
methods.
So
it
implies
that
this
methods
actually
handled
by
step
there
so
step
yet,
basically,
logic
which
receives
a
form,
submission
or
any
kind
of
other
HTTP
requests
processes
for
them
and
maps
it
to
Java
objects
and
to
endpoints
saying
in
the
Java
code,
so
which
does
all
the
mapping
Commission.
Could
you
expect,
for
example,
from
Spring
Framework
from
quark?
B
A
Okay,
so
you
can
review
some
information
about
requests,
hope
we
can
come
nothing
between
what
was
already
showing
at
the
previous
meeting.
There
is
a
bunch
of
jobs,
and
there
is
some
jobs
are
related
to
stapler,
especially
a
one
for,
for
example,
a
tablet,
requestdispatcher
filtering
and
fragmentation.
So
this
job
to
one
it
can
provide
you
some
insights
about
how
stuff
works
in
terms
of
new
common
are
requests
and
filters.
B
Freedom,
I
guess
opposed
projects,
maybe
100
or
something
like
that.
You
can.
If
you,
if
you're
doing
research
you
can
make
well,
you
know
ahead
of
time.
You
can
make
pull
requests
with
documentation,
examples
or
to
these
repositories,
and
that
can
help
with
understanding
and
then
people
to
help
other
people
figure
out.
What's
going
on
with
this
deeper
as
well,
okay,.
A
A
A
B
Think
the
community
I
was
kind
of
looking
for
something
that
would
be
able
to
easily
there's
just
a
little
bit
more
bottom
for
whenever
you
go
to
look
her
and
the
different
things
within
Jenkins.
It's
really
honestly
hoping
that
we
end
up
with
something
like
open,
API
document
that
would,
at
least
you
know,
be
a
little
bit
more
digestible
easier
to
read
through
people
who
are
kind
of
working
with
anything
with
Jenkins.
If
so,
because
there
are
a
lot
of
API,
so
there
are
is
coming.
B
There
are
powerful
things
you
can
do
with
them,
especially
if
we
start
seeing
in
some
of
the
plugins,
but
it's
very
difficult
to
figure
out
where
they
all
are.
So
if
there
was
just
kind
of
a
new
URL
based
off
of
Jenkins,
where
you
could
see
what
is
installed
and
like
what
api's
are
available
and
it's
in
an
open,
API,
well
Matt.
That
would
be
a
lot
easier
for
people
to
understand.
B
What's
going
on,
I
think
if
there
was
a
way
to
that,
we
could
keep
a
hand
it
Center,
it's
a
difficult
task,
but
being
able
to
also
polish
that
somewhere
on
the
website.
So
if
people
will
be
able
to
know
that
this
is
even
an
option
with
you
and
to
also
then
I
guess
included
in
continued
building
into
Jenkins
documentation.
B
That
would
be
useful
as
well,
so
I
think
it'll
start
with
something
that
is
that
lose
vocal,
and
we
could
update
our
documentation
to
point
to
hey
there's
this
there's
now
this
document
that
you
can
look
at
inside
it,
your
Jenkins,
to
see
what
they
eat.
The
HTTP
response
options
are
of
the
codes,
how
to
be
able
to
use
it
and
then
maybe
eventually,
maybe
you'd
like
later
on
a
face
for
your
I.
Don't
know
that
you
even
be
able
do.
B
A
I'm,
just
a
screen
sharing
one
of
the
jobs
of
2019
results,
basically
folded
authorization
project,
it's
a
project
created
by
all
student,
be
the
Sharma
and
as
a
part
of
this
project,
he
created
the
depositor
and
small
github
for
that
organization,
and
here
you
can
see
aristocrat
calls
supported
by
the
plugin.
Now
it
has
one
of
those
weakness
because
it's
generated
to
monitor.
So
there
is
no
automation
for
that,
but
if
there
was
automated,
we
should
at
least
create
skeletons.
It
would
be
a
good
step
and
again
it
can
be
done
incrementally.
A
B
Somewhere
exactly
but
documents
see
how
it
just
makes
it
so
much
easier
to
know
what's
going
on
with
the
plug
engine,
but
it
since
it's
done
manually,
it
requires
someone
to
continue
to
make
sure
the
document
is
up-to-date,
so
it
can
easily
fall
behind
so
being
able
to
auto
generate
something,
even
if
we
start
off
with
just
being
able
to
get
post
nothing
creaking
to
get.
That
would
be
useful
as
well
it
just.
This
is
a
great
example
of
something
that
makes
it
a
little
bit
easier
for
people
to
read
to
find
out.
B
A
Actually,
one
of
the
topics
you
can
consider
is
language
and
rate
to
the
specifications,
because
there
are
basically
two
ways.
One
way
is
that
you
generate
them
in
runtime,
so
one
Jenkins
runs.
Then
we
do
it
for
several
other
projects
where
you
can
go.
Example.
That's
more
instance,
that
is
the
agent
can
say
also
here,
for
example,
you
can
get
the
serve
documentation
for
pipeline
or
documentation
for
configurations
code
based
on
installed
plugins,
most
likely
it
will
fail
because
it
is
haven't
fixed
but
yeah.
A
This
reference
documentation
is
specification
which
be
which
is
being
generated
on
the
flight
dependent
conduct
audience
sets.
We
use
a
session,
it's
one
of
the
ways
to
do
that
and
same
is
basically
used,
for
example,
by
pipeline,
because
alright
and
again
you
can
get
the
communication
generated.
Another
way
which
might
be
paying
attention
just
is
generate
link.
Is
it
using
the
build
time?
A
So
basically
turns
up
is
what
you
prefer.
If
you
like,
front-end
development,
exactly
it's
mondo
jenkins
site,
you
could
do
if
you
like
back-end
development
yeah,
you
can
just
take
a
plugin
that
is
a
plugin
called
maven
is
a
plugin
which
basically
includes
so
the
most
of
Jenkins,
specifically
mailing
functionality.
For
example.
We
could
just
add
logic
there,
or
maybe,
as
a
library
and.
A
A
A
A
C
A
B
A
So
that's
right,
then
same
for
all
other
students
who
might
be
interesting
to
just
take
a
look
at
different
implementations.
Different
approaches
and
I
mean
we
try
to
keep
all
the
information
public,
so
we
will
be
shank
the
details
and,
for
example,
if
you
want
to
collaborate
between
each
other
to
somehow
make
projects
independent,
it's
possible.
So,
for
example,
if
you
want
to
collaborate
and
split
it
somehow
or
if
you
just
want
to
do
some
prototyping
kind
didn't
want
to
step
on
each
other's
toes.
A
It's
also
possible
so
again
use
public
channels,
so
that
would
be
exempt.
You
ended,
but
again
at
the
application
phase.
It's
not
a
bigger
concern.
So
even
if
you
propose
to
pull
requests
which
basically
do
the
same,
it
won't
impact
anyone,
because
you
will
just
take
a
look
at
this
tool
or
the
place
and
take
them
into
consideration.
A
Yes,
so
in
Jenkins,
especially
generous
cover
and
other
chaoticness,
a
pool
request
cycle
may
be
quite
long
because
we
need
to
verify
the
stability
etc,
and
for
you,
if
a
particular
pull
request
is
staged,
is
already
enough.
You
can
move
on
to
other
area
unless
you're
blocked.
You
can
keep
exploring
that
and
contributing
to
the
same
request.
A
A
You
can
just
keep
submitting
them
and
if
you
need
help
use
the
reviews,
so
just
think
some
dieter
channels,
because
here
sometimes
pool
requests
formula
through
the
cracks.
We
try
to
improve
the
situation
across
the
community,
but
yeah.
If
you
submit
a
request,
a
random
plugin,
you
may
need
to
raise
visibility.
B
A
And
yeah,
if
you
hope
to
pick
your
proposals,
which
you're
trying
to
do
something
rebuked
should
help
yeah,
because
yeah
we
will
do
our
best
to
ensure
that
that
is
communicable
around
this
project
and
for
this
particular
project,
I'm
not
concerned
at
all.
We
will
have
a
dozen
of
stakeholders
easily
across
the
community
interested
in
that,
maybe
more
but
again,
I'm
just
trying
to
do
something
is
the
best
way
to
explore
how
to.
B
Write
and
I
guess
also
you
like
a
litter,
you're
saying
all
the
stakeholders.
If
they
have
awareness
early,
they
can
also
help
they'll,
be
excited
that
someone's
interested
looking
this
and
be
able
to
you
know,
get
involved
a
little
bit
earlier
and
another
more
people
to
ask
questions
to
and
to
share
other
perspectives.
Now.
A
A
So
you
can
take
a
look
at
the
ji-sook
timeline,
so
there
is
a
visual
timeline
and
state
so
that
application
period
opens
on
March
16th,
so
just
in
one
week,
but
this
is
the
first
day
when
you
can
officially
submit
your
proposal
through
the
JSOC
website,
but
it
doesn't
mean
that
you
cannot
work
on
your
proposals
now,
because
what
we
usually
recommend
students
to
do
is
you
create
a
proposal
draft?
You
can
already
know
what
information
is
expected,
because
google
has
student
guide
and
we
also
have
the
student
guide
on
the
jenkees
website.
A
So
you
can
just
go
to
this
page
and
you
can
see
that
there
is
information
summarizing
what
we
expect
from
student
proposals.
Well,
it's
mostly
built
on
the
Google
student
guide,
but
we
have
some
additional
expectations,
so
you
can
start
drafting
your
proposal
and
you
can
just
immediate
jobs
through
the
main
entries.
So
you
didn't
hit.
Wait,
wait
until
much
16th.
If
you
already
have
something
to
propose
to
discuss
just
admit
a
document
and
people
start
reviewing
that,
though
yeah
right
now,
it
may
be.
A
A
E
A
If
you
are
not
familiar
to
a
scientist,
it
definitely
makes
sense
to
try
it
out.
So
what
we
usually
recommend
you
can
just
run
Jenkins
example
in
a
docker
container
locally,
and
you
can
just
try
out
to
making
some
of
your
projects
I.
Guess
you
have
something
in
your
universities,
for
example,
million
projects
with
Java
or
something
with
C++,
so
you
could
just
try
using
Jenkins
Toto
meet
the
bill,
for
your
project
is
a
first
step.
So
just
study
ETA
and
its
features.
B
Was
also
thinking
that
sometimes
with
if
you
start
to
run
Jenkins,
it
might
help
put
some
of
these.
You
know
projects
that
we've
talked
about
in
context
as
well,
so
you
might
be
able
to
see
well
stapler
talks
about
your
constructing
URLs
inside
of
Jenkins.
It's
like
alright.
So
now,
if
I
create
some
jobs,
I
can
click
and
see
you
know
the
URL
being
generated
like
and
you
can
kind
of
start
to
see
how
things
are
built,
so
that
might
help
as
well.
So
here
I
say
you
see
the
folder
infrastructure
here.
B
A
Things
like
yeah,
probably
this
is
not
the
best
instance,
so
we
have
staging
so
you
know
we
drive
at
some
guys
repairs,
but
yeah
heads
up
a
number
of
REST
API,
so
they
is
blocked.
So
it's
probably
not
the
best
project.
But
if
you
have
your
own
running
instance
or
if
you
find
there
another
public
instance,
because
many
are
projects
like
adopt,
open,
JDK,
Apache,
etc,
they
use
to
Jenkins.
So
you
can
find
a
lot
of
public
instances
and
explore
how
they're
organized
and
what
is
being
used
just
to
submit
for
the
link.