►
From YouTube: 2021 01 27 GSoC 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).
B
Great
welcome
to
today's
gsoc
meeting.
We
have
a
number
of
pr's
to
discuss
and
questions
to
answer,
including
by
sagar.
Thank
you
all
for
being
here.
Should
we
should
we
address
that
glass
question?
First,
actually,
that's
maybe
the
best
way
to
go
about
it,
and
I
will
should
I
screen
I'll
screen
share
and
we
can
look.
Is
that
all
right?
If
I
screen
share
your
questions,
I
got
it's
in
the
gift
card.
That's.
B
B
Good,
and
can
you
all
see
the
jisok
great
excellent,
so
cigar
has
a
question
on
exp
understand.
Well
I'll,
let
you
phrase
it
actually.
Could
you
like
two
years
ago.
C
So
I
mean
I
was
that
meeting
again
to
understand
what
oleg
said
to
me
on
13th
gen,
where
I
asked
the
questions
about
rest,
api
specification
generator
and
the
conclusion
we
had
in
that
he
said
to
me:
you
have
to
try
to
extract
the
end
points
for
the
just
start,
with
some
small
plugin
plugin,
which
is
he
said,
code
coverage,
plugin
and
and
when
I
tried
on
how
can
I
extract
that
end
point
on?
Even
I
don't
know
how
to
use
that
plugin.
C
First
of
all,
so
I
I
just
first
I
mean
to
just
hand
my
get
dirty.
I
just
I
came
to
know
that
this
was
a
project
from
2018
g-shock
again
made
by
one
student.
I
mean
and
shin
yang
something
like
that,
and
so
I
just
posted
my
questions
in
that
gator
channel
and
I
just
I'm
concurrently
still
trying
to
figure
out
how
it
is
working,
and
I
mean
that
I
mean
there.
C
One
person
said
to
me:
I'm
just
use
this
my
github
link
and
try
to
run
jenkins
using
docker
and
so
that
so
first
I
just
learned
docker,
which
is
actually
quite
amazing,
and
now
I'm
running
docker
using
jenkins.
I
mean
yeah
running
jenkins,
yeah
containerized
by
docker
yeah.
C
So,
but
still
when
I
looked
into
the
source
code
of
that
plugin,
it's
I
mean
I
mean
I
don't
have
any
idea
still
what
to
do
further
on,
even
though
I
just
even
though
it's
like
just
said
to
me:
okay
sagar,
you
have
to
extract
the
endpoint,
but
I
don't
know.
Actually
I
mean
where
to
research.
Actually
I
mean
it's,
maybe
quite
unclear
to
me,
it
seems
lit,
seems
again
confusing.
I
mean.
A
Yeah
so
so
I
think
it
seems
like
there
would,
at
least
for
me
if
I
were
approaching
there'd,
be
a
challenge.
First,
how
do
I
identify
a
rest
api
endpoint
inside
the
java
source
code
of
a
particular
plugin
or
of
jenkins
right?
So
that's
that's
one
because
I
think
the
if
it's
going
to
be
an
automatic
generator,
it's
got
to
walk
through
all
of
the
1700
plug-ins
that
are
in
jenkins
and
read
their
source
code
and
identify.
Oh,
this
is
a
rest.
A
Api
endpoint
and
this
is
a
rest,
api,
endpoint
and
then
it's
got
to
identify,
and
these
are
the
arguments
that
I
endpoint
and
in
a
in
a
perfect
world,
here's
the
javadoc
for
that
rest,
api,
endpoint,
implementation.
Now
now
I
said
perfect
world
because
many
of
them
no
javadoc,
you
know
varied
levels
of
quality
of
javadoc,
and
so
so
that
was
that
was
what
I
was
assuming
is
that
likewise
what
you
were
assuming
cigar.
C
Yeah
in
the
in
the
last
meeting
on
trading,
you
also
said
I
mean
we
find
out,
I
mean
some
plugins,
even
don't
have
exported
bean,
and
currently
we
are
relying
on
exported
bin
to
get
the
rest.
Endpoints,
and
even
you
said,
even
my
friend
has
a
one
plugin
I
mean
mark
and
even
that
plugin
don't
even
have
exported
bean
right.
A
Right
so
so
so
the
the
challenge
and-
and
it's
I
think
it's
a
an
interesting
challenge
that
challenges:
how
do
we
identify
a
rest,
api,
endpoint
and-
and
I
think
that
so
so,
there's
certainly
one
level
of
rest-
api
endpoint
that
that
we
can
identify
from
the
jenkins
user
interface.
So
would
it
be
okay
if
I
shared
my
screen
and
illustrate
that
one
that
you
might
use
as
a
first
exploration?
Okay,
this
is
not
even
using
a
plug-in.
This
is
just
the
jenkins,
the
jenkins
jenkins
user
interface.
But
for
me
that
helps
me
already
see.
A
Oh,
I
might
look
here
and
here
to
see
how
is
that
api
expressed
in
the
java
source
code
that
I
can
see
from
the
jenkins
ui?
So
so
I'm
going
to
share
my
screen
and
let's,
let's
take
a
look
at
that.
Oleg
oleg
would
certainly
do
a
better
job
of
this,
but
we're
going
to
use
my
inadequate
techniques
here.
A
So
I'm
going
to
go
to
my
jenkins
server
and-
and
this
is
just
a
jenkins
installation
that
I
use,
and
so
if
I
look
at,
if
I
remember
right,
if
I
just
put
slash
api
on
the
end
of
any
url,
I
get
this
rest
api,
endpoint
and
so
already
I've
got.
And
if
I
want
to
see
the
json
data
there,
it
is
so
so
already
at
the
root
level,
there
is
an
api
endpoint
that
returns
in
this
case.
A
A
So
now
the
challenge
is:
how
are
they
being
discovered
and
once
we
know
how
they're
being
discovered
that
discovery
process
is
the
hint?
Oh,
those
that
same
technique
is
probably
being
used
to
discover
things
from
plug-ins
like
so.
Let's
see
that
was.
That
was
one
example.
Let's
try
did
you
have
a
question
before
I
continue
talking.
C
Yeah,
so
you
said
in
order
to
just
know,
I
mean
how
actually
this
thing
is
working
from
the
jenkins.
I
have
to
put
a
debugger,
but
how
can
how
can
I
know
like
where
to
put
a
debugger?
There
are
thousands
of
lines
of
code,
so.
A
Good
good
question,
and,
and
in
in
my
case
I
would
go
looking
for
so
so
again.
This
is
oleg,
I'm
sure
would
have
better
better
guidance,
but
we're
going
to
use
my
my
feeble
and
inadequate
skills.
So
I
would
look
at
this
string
assigned
labels
and
look
for
that
string
in
the
jenkins
source
code.
Thinking
that
okay,
it's
probably
something
related
to
that
and
set
three
or
four
set
break
points
at
various
places
around
that
label
trying
to
find
it.
A
C
A
Well,
and
that
that
I
think,
is
the
next
question
right
so
so
for
me,
the
first
question
was
okay,
which
what
what
does
an
api
endpoint
look
like
inside
the
jenkins
code,
yeah
right,
and
so
that
was.
That
was
the
first
question
and
that's,
but
that's
certainly
not
not
a
conclusion
of
the
questions,
because,
once
what
does
the
api
endpoint
look
like?
The
next
question
is:
how
does
jenkins
determine
that?
That
thing
is
an
api,
endpoint
and,
and,
and
it
may
be,
it
may
be
that
we've
already
got
the
hint
right
here.
A
B
A
C
Yeah
yeah,
that
makes
sense.
I
mean
the
first
question
that
we
currently
looked
into,
and
just
I
mean
a
possible
answer,
may
be
that
we
looked
into
just
look
into
the
files
that
when
we
are
hitting
that
input
and
just
put
a
debugger
and
explore
those
files,
maybe
I
mean
I
get
some
hints
and
another
possible
way
is
to
explore
further.
A
Right
yeah,
so
so
I
think
I
think
we're
also
open
to
it.
I
can
ask
to
see
if
we
can
find
some
of
olek's
time
specifically
for
this
topic,
just
because
it
would
be
a
good
conversation
to
have.
He
might
be
able
to
give
us
in
15
minutes.
A
quick
tutorial
we
could
record
of
oh.
This
is
how
okay
we
we
saw.
We
saw
here
are
some
examples
of
the
endpoints
and
we
found
that
in
the
source
code.
But
then
how
does
jenkins
decide?
Something
should
be
a
rest.
C
A
A
A
Search
apparently,
I
don't
know
how
to
use
get
grip
and
that's
embarrassing,
because
that
should
have
found
what
I
was
looking
for.
So
this
thing
is
the:
who
am
I
implementation
right
so
and-
and
here
we
see
yeah
so
now,.
A
However,
and
maybe
that's
I
guess
it
depends
on
what's
best
for
you
in
terms
of
exploration,
you
could
conceivably
say:
hey,
I'm
going
to
do
it
just
for
exported
beans
initially
and
then
try
to
extract
extract
a
sample
for
an
exported
bean
for
exported
beans
and
see
if
I
can
generate
the
swagger
definition
of
that
and
look
at
that
to
see.
How
does
it
look
that
might
be.
A
C
Yeah,
I
mean
yeah
that
maybe
oleg
is
going
to
tell
us
in
maybe
a
short
tutorial.
What
are
the
possible
ways
to
how
jenkins
understanding
is
it
recipe
right.
C
A
That's
that's
what
I
was
assuming
my
assumption
was
that
that
the
the
source
code
has
some
way
of
documenting
itself,
so,
for
instance,
here
this
is
this-
is
the
javadoc
for
the
this.
This
comment
right
here
is
the
javadoc,
for
who
am
I
and
then
I
don't
see
any
other
javadoc
so
that
yeah,
so
that's
the
total
javadoc
and
then
the
other
things
that
are
here
are
the
at
exported
annotation.
A
That
tells
us
this
is
probably
giving
us
a
an
api
endpoint.
That
is
for
the
name,
and
this
is
anonymous
and
is
authenticated
here.
Let's
are
you
okay?
If
I
check
that,
I
think
I
think
this
would
be.
This
might
be
helpful
to
check.
Let's
see
if
I
do
slash
api
on
the
end
of
that
and
then
look
at
the
json
api.
A
It
says
yes,
so
here's
an
anonymous,
authenticated
and
name
so,
there's
there's
the
there's,
the
representation
name
for
for
the
get
name
at
exported,
annotation
and
there's
the
one
for
authenticated
yeah,
so
so
that
I
think
what
we
saw
see
there
is,
who
am
I
slash
api
in
the
ui
maps
to
the
the
name
field?
Is
this
the
authenticated?
Is
this
the
anonymous
is
this
now
I
don't
know:
oh,
oh
interesting,
okay,
so
and
here's
here's
an
example
of
one
little
league
of
sessions
with
same
security.
C
Though
I
don't
know
what
is
such
an
id,
but
it
seems
little
bit
yeah
rejected
security.
So
that's
why
maybe
they
remove.
A
Yeah
yeah,
certainly
we
if
we
wanted
to
know
why
this
was
removed
there.
There
are
marvelous
tools
like
this
one
that
blame
this.
That
will
tell
us
why
it
was
when
it
was
removed
and
we
could
read
the
list
so
but
but
for
the
rest,
api,
you
don't
need.
You
don't
need
to
know
why
it
was
removed.
You're,
just
that
if
you
were
feeling
curiosity
or
thought
you
should
become
an
archaeologist
instead
of
a
programmer,
then.
C
Okay,
yeah
makes
sense,
and
I
was
thinking
okay,
I
believe
I'm
this,
where
my
class
is
being
maybe
processed
by
stapler
and
then
he's
doing
some
magic
behind
the
scene
and
just
showing
the
output
on
the
screen.
C
I
mean
glue
my
code
somewhere
where
the
stapler
code
is
doing
the
processing
and
try
to.
I
mean
from
that
and
process
that
same
class
to
extract
the
endpoints.
Maybe
I
need
I
just
need
to
check
where
this,
who
am,
I
call,
is
calling
I
in
the
and
jenkins
source
code,
and
maybe
then
I
have
to
maybe
just
console
log,
some,
maybe
log
some
end
points.
C
I
mean
control,
clicking
on
control
and
just
clicking
on
this
class
name,
and
it
will
show
me
all
the
places
where
it
is
using
and
just
seeing
where
how
it
that
that.
A
That
that
you
certainly
could
that
seems,
like
I
mean
for
the
rest,
api
specification
generator.
I
would
think
you,
you,
probably
don't
even
care
who
this
thing
calls
right.
You
don't
care
because,
because,
for
the
rest,
api
specification
in
terms
of
the
specification
there
is
a
there
is
a
rest
api
endpoint.
A
Let's
go
back
here,
so
there's
a
rest,
api
endpoint
that
looks
like
this
or
something
like
that
right.
It
looks
like
jenkins
url,
who
am
I
slash
api
and,
and
then
there
are
arguments
that
that
thing
takes
like
like
this
well
here
we
can
see
the
examples
that
this
talks
about
are
things
where
we
can
say:
should
it
take
a
certain
names
of
jobs,
or
should
it
do
a
certain
depth?
A
A
So
so,
back
to
I
I
don't.
I
don't
know
that
you
need
to
look
at
who's
who
this
is
calling
it's
calling
somebody,
but
the
fact
that
this
is
exported
and
that
there's
a
get
name
means
that
the
rest
api
specification
should
say.
Yes,
this
thing
returns
a
a
a
name,
a
field
with
name
in
it
and
the
value
of
name
and
a
field
authenticated
and
the
value
of
authenticated
in
it.
A
D
C
So
so
eventually
I
mean
you
know,
so
I
we
so
in
order
to
extract
endpoints,
where
I
can
put
my
source
code,
I
mean
to
just
I
mean
for
the
exploration
to
where
I
I
just.
I
can
actually
log
some
of
the
end
points
in
that
yeah.
I
was
just
thinking
about
that.
Yeah
yeah.
C
Okay,
so
I
know
I
mean
I
in
this
file
that
contains
exported
bean
and
some
exported
annotations.
That
is
that
data
is
going
to
be
output
on
the
screen,
but
so
our
main
goal
is
to
make
to
show
a
documentation
to
a
user,
a
beautiful
documentation
which
is
being
generated
by
again
swagger,
and
for
that
we
need
open
api
specification
before
that.
Even
we
have
to
extract
rest,
api
endpoint.
C
So
in
order
to
extend
extract
that
end
point
where
I
have
to
I
mean,
should
I
have
to
I
mean:
can
you
give
me
any
helpful
any
tutorial
or
an
just
like
previously,
like
I
made
a
plugin?
That
was
a
great
tutorial.
I
just
made
a
scratch
plugin.
So
if
I
put
this
code,
that
menu
is
being
created,
so
I
mean
where
I
can
so
so
in
order
to
make
this
thing
happen.
So
where
I
can,
I
mean,
put
create
files
and,
put
I
mean.
A
So
so
maybe
what
you're
asking
is?
How
will
the
rest
api
specification
generator
be
invoked
by
someone
who
wants
to
generate
the
specification?
Yeah
yeah?
Is
that
yeah
okay,
so
so,
and
that
I
think
that
I
think,
is,
I
think,
the
rest
api
specification.
Generator
should
be
an
external
program
that
that
is
separate
from
jenkins,
but
reads
the
jenkins
source
code.
So
we've
got,
we've
got
something
similar
that
we
do
with
a
thing
called
the
pipeline
steps,
documentation
generator
where
the
pipeline
steps
documentation
generator
does
what
it
does
is
it
asks
for
the?
A
I
think
it
asks
for
the
list
of
all
plugins
and
then
reads
those
plugins
looking
for
any
of
them
that
implement
a
pipeline
step
and
when
it
finds
a
pipeline
step
implementation
inside
one
of
those
plugins
it
goes.
It
reads
inside
that
plug-in
source
code
to
find
the
documentation
that
is
related
to
that
pipeline
step.
A
So
it's
a
separate
program
that
we
run
independent
of
jenkins
so
and
it
it's
separate
so
that
we
can
run
it
and
and
show
and
extract
the
data
and
then
use
that
on
a
website,
and
I
think
this
open
this
rest
api
specification
generated
be
the
same
thing
that
we
would.
Ultimately,
you
would
create
a
program
that
is
a
separate
program
and
that
separate
program
would
read
the
jenkins
source
code,
read
the
plugin
source
code
and
decide.
C
Yeah,
that
makes
sense,
I
believe
so
I
mean
from
now.
I
guess
it
seems
I
have
to
maybe
explore
maybe
about
pipeline
step
like
documentation,
I
mean
how
maybe
it
is
working.
A
Right
that
that
might
be
a
good,
that's
probably
a
good.
That's
a
good
place
to
see.
How
does
how
did
someone
else
do
the
discovery
of
of
of
information
from
inside
jenkins
plug-in
source
code
yeah,
because
pipelines,
pipelines,
pipelines,
steps
yeah,
I'm
sorry,
I'm
not
remembering
the
exact
name,
but
let
me
find
it
because
I
was
just
working
with
it
with
the
doc
stock
sig
because
it
was
it
okay.
Here
we
go
there,
it
is
and.
C
Is
that
generator
is
also
is,
is
I
mean
made
by
made
by
christine?
I
mean
I
mean?
Is
it
yes,
that's
the
one
that
kristen
redstone
made.
A
A
C
A
Yeah
so
so
jenkins,
jenkins
infra,
is
the
github
organization
where
the
jenkins
project
keeps
its
public
infrastructure,
and
so
so
that's
where
cara
and
I
and
others
do
maintenance
work
to
to
improve
the
jenkins.io
website
or
to
fix
the
update
center
or
to
capture
ratings
of
new
releases
or
to
publish
publish
change
logs.
All
sorts
of
things
like
that,
okay.
D
So
it's
completely
external
program.
A
Right,
it
is
yes,
it
is
an
entirely
external
program.
It's
you
know.
Now
it's
it's
written
in
java
and
I
suspect
that
it
would
be
good
to
write
it
in
java,
because
that
way
you
get
the
benefit
of
using
java
to
do
the
the
looking
inside
of
class
files,
if
you
need
to,
if
you
need
to
do
java,
byte
code
manipulation
for
whatever
reason
having
it
written
in
java,
is
a
lot
better
than
choosing
to
write
it
in
go
or
python
or
something
else.
So
so
I.
A
C
Yeah
so,
and
when
the
christian
made
this
plugin
I
mean,
is
there
is
anything
that
she
read
it
before
I
mean
which
I
can
like.
There
is
a
I'm
documentation
on
how
to
create
plugin.
A
So
the
readme
in
this
plug-in
this
pipeline
plug-in
doc
generator
is
a
is,
is
has
some
good
outline
of
hey?
This
is
how
you
use
this
thing
and
when
you
use
it,
this
is
what
happens.
The
other
is
that
there
are.
There
are
at
the
moment
in
the
doc
sig
people
who
are
actually
working
on
pipeline
step
generator
to
be
sure
they
understand
it.
So
if
you
have
a
question
about
that,
one
specifically
go
to
the
getter
channel
for
the
pipe
for
the
doc
sig,
and
I
will
paste
that
into
the
chat
here
as
well.
A
A
Oh
here,
actually
let
me
show
you
what
it's
generating,
if
that's,
okay,
that
that
makes
it
makes
it
sort
of
real
for
us
right.
So
I'm
gonna.
A
A
A
A
You
discovered
that
there
is
a
plug-in,
that's
the
get
plug-in
discovered
the
source
code
for
the
git,
plug-in
search
the
source
code
for
the
get
plugin
and
found
this
page
that
it
could
then
embed
in
its
output,
and
that's
that's
so
that
that
gives
a
hint
of
what
the
pipeline
docs
step
generator.
The
pipeline
steps.
Dock
generator
is
doing.
A
C
Okay,
so
this
is
that
it
is
generated
by
pipelines.
A
That
generates.
Where
is
there.
It
is
here,
is
the
job
that
runs
periodically,
that
gen
that
actually
publishes
the
its
results
and
jenkins
thought
I
o
uses
it.
So,
ultimately,
your
rest
ap,
the
rest
api
specification
generator
would
someday
be
run
in
a
ci.jenkins.io
job.
To
do
exactly
this,
it
would
do
the
the
reading
of
source
code
writing
of
documentation
files.
A
It's
so
it's
it's
doing.
If
I
remember
correctly,
it's
generating
its
ultimate
output
is
static
pages
that
are
then
used
in
the
jenkins.io
site.
We
don't
want,
we
don't
want
the
site,
this
thing
to
be
anything
but
static
pages,
and
so
it
I
believe
it.
Those
steps,
generator,
creates
static
pages
or
ultimately
creates
static.
Pages
that
are
displayed
here
as
static
web
pages
did
was.
Was
that
your
question,
or
did
I
misunderstand
your
question?.
C
Currently,
even
I
don't
know
much
about
that,
I
mean
I
get
a
little
glimpse
about
pipeline
step,
documentation
generator.
Maybe
I
have.
I
will
look
into
it
for
this
week
and
then
maybe
maybe
if
I
have
questions
I
will
further
on
for
next
week,
I
mean
it's
it's
better
to
explore
it
I
mean
we
are
just
yeah.
I
mean.
A
The
the
for
me,
the
the
concept
that
pipeline
steps,
doc
generator
is
providing
is
an
external
program
that
we
that
somebody
calls
you
from
a
development,
environment
or
jenkins
from
a
ci
environment
that
reads
the
jenkins
core
source
code
and
the
list
of
jenkins
plug-ins
and
then
uses
that
information
to
extract
use.
Some
useful
content,
pipeline,
documentation
or
rest
api
documentation.
D
A
A
A
A
C
Going
now,
oh,
oh,
I
see
I
mean
for
writing
this
language.
What
are
the
things
that
we
need
to
know
before?
Writing
this?
That's
all
been
I
mean
for
a
bunch
of
I
mean
heap
just
the
accurate
information
is
being
generated
by
pipeline
step.
A
You
understood
perfectly,
that
was
exactly
right.
It's
it's
okay!
This
is
what
which,
which
things
can
be
called
in
this
context,
and
so
now,
if
I,
if
I
click,
if
I
remember
right,
if
I
go
back
here
there
is
this
handy
little
tool,
this
thing
called
pipeline,
syntax
that
actually
helps
me
generate
valid
syntax,
and
so,
for
example,
you
remember
we
we
looked
at
that,
get
step,
here's
the
get
step
and
it
says.
A
A
Oh,
no,
no!
No!
No!
No!
Because
cara's
here
and
she
lives
in
in
the
uk.
We
use
mi6,
of
course,
right.
Okay,
so
that
just
generated
the
the
the
pipeline
syntax.
If
I
wanted
to
use
this
now,
you
don't
care
about
this
for
for
the
rest,
api
generation,
but
being
aware
that
this
exists
won't.
Do
you
any
harm
it's!
This
is
a
kind,
a
tool
that
is
very
helpful
for
people
who
are
writing
pipelines.
C
I
see
I
mean
this
whole
configuration
has
been
written
in
this
one
line.
Is
it.
D
A
C
Okay,
so
I
will
look
into
the
pipeline
stock
documentation
so
how
it
is
working
so
that
maybe
that
would
be
now.
I
have
idea
because
last
time,
when
oleg
said
to
me
discover
what
is
code
coverage
plug-in,
even
I
don't
know
first
of
what
is
code
coverage,
then,
one
day
later,
I
came
to
know
it
is
just
a
testing
practice
which
is
just
showing
a
measure
yeah
yeah.
A
Okay
right
well
well,
and
so
exploring
the
code
coverage
plug-in
is
interesting,
but
but
we
we
failed.
We
had
failed
to
give
you
the
the
the
general
framework
for
hey.
This
is
an
external
program
and
it
needs
to
read
from
jenkins
core
and
read
from
jenkins
plugins,
and
you
may
find
the
pipeline
steps
doc
generator
closer
to
the
final
structure
of
the
program
you
you
would
need
to
create
than
than
just
exploring
code
coverage
plug-in
yeah.
A
C
Yeah
my
pleasure
yeah,
that's
for
today
I
mean
for
from
my
surgeon.
Oh
yeah,.
A
B
C
D
A
Those
are
brilliant
questions
and
thank
you
very
much
for
asking
them.
We
are
delighted
that
you're
asking
questions,
and
it's
and
and
thank
you
for
your
patience
with
my
giving
inadequate
explanations
or
imperfect
and
flawed
explanations.
That's
wonderful,
we'll
we'll
talk
to
you
in
a
week
sagar
and
I
look
forward
to
more
questions.
C
Yeah,
just
just
please
just
post
this
on
youtube,
I
will
I
will
eager
to
watch
it
again.