►
From YouTube: ☀️ GSoC CloudEvents plugin mentor meeting 2021.5.31
Description
This is the second community bonding meeting for GSoC CloudEvents plugin and already Shruti is doing impressive exploratory work!
Note: the decision to record the meeting was taken about 10 minutes in. Thus, the recording starts just as Shruti shows her week's exploratory work and we map out next steps.
GSoC CloudEvents plugin meeting notes: https://docs.google.com/document/d/11uMgE29StGLZEeOTteRXWIOpohBFk9ztwj1JeiUv9-U/edit#
A
A
A
A
A
A
What
build
is
building
if
it's
completed,
if
it's
in
queue
or
the
description
of
the
job
and
stuff
like
that
and
finally,
there's
also
the
other
particular
like
that
is
not
one
of
these
right
now,
but
I'm
really
thinking
about
using
it
to
get
information
about
the
build
itself,
which
would
be
the
api
for
the
world.
I
do
not
have
I
I
was
looking
into
techtons,
even
that
techcon
is
emitting
or
it's
like
similar
events,
and
it
has
events
for
if
I'm
talking
about
a
task
or
a
job
itself.
A
A
A
And
then
this
is
the
data
itself.
You
know
the
law
can
go
into
the
data
that
we
want,
but
since
this
is
a
simple
job,
I'm
not
really
sure
what
what
all
can
I
put
in
you
know
we
have
the
url,
we
have
the
I
can
put
in
actions,
I'm
not
entirely
sure
to
actually
this
guys
was
what
actions
usually
by
telling
about
a
job.
C
I'm
not
sure
if
build
actions
are
important.
At
this
point,
I
think
when
it
comes
to
build
actions,
we
might
have
to
ask
someone
who
is
so
a
little
more
experienced
in
that,
so
we
should
probably
approach
someone
in
jenkins
who's,
who
knows
more
about
build
actions,
but
what
we
can
do
at
this
point
is
this
is
like
a
very
good
start.
We
can
figure
out.
B
A
So
right
now
there
is
the
job
name.
There
is
the
the
number
like
the
build
number
itself
and
then
obviously
you
have
the
url
that's
going
to
the
source
of
wherever
it
is
generating
from,
and
I
I
am
trying
to
build
the
the
event
for
whenever
a
job
has
ended,
which
is
a
bit
tricky,
but
over
there
it
would
be
sort
of.
If
the
result
is
success
or
this
result
is
failure.
A
I
I've
been
working
on
that
a
bit
not
a
lot,
but
I'm
researching
on
how
we
can
start
with
the
event
of
what
happens
when
a
job
builds.
You
know
this
like
this
is
a
bit
of
pulling
the
api
issue,
because
I
thought
it
would
be
easy
if
you're
using
jenkins
rest
api
client
for
java.
But
I
don't
know
it's
it's
natively
inside
of
jenkins
plugin,
that's
giving
media.
If
I
run
the
code
outside
of
it,
it
works
fine.
A
A
Yeah,
I
I
looked
at
it
a
little
bit,
but
not
not
a
lot
like
not
entirely.
I
was
not
able
to
you
know.
There
were
a
lot
of
things.
He
was
not
able
to
really
get
my
head
around
it,
because
what
I
had
like,
starting
with
things
and
there's
a
lot
of
things,
but
it's
something
that
I'm
like
looking
in
as
a
part
of
the
research
for
just.
C
So,
as
far
as
I
know,
I
think
yeah
the
web
trigger
plugin
gives
an
end
point
to
receive
an
http
request
on.
So,
if,
if
you
want,
we
could
sit
down
and
kind
of,
you
know
just
go
through
the
code
and
figure
out
how
it's
doing
it.
Just
like
leave
the
code,
wherever
you
might
have
problems
while
you're
reading
the
code,
you
can
just
ping
any
one
of
us
and
ask
like
what
is
this
part
of
the
code?
What
what.
A
A
This
has
started
now,
and
this
is
running
now,
so
just
the
differentiating
between
spill
and
then
building
a
build
or
like
running
of
a
build
and
then
finally,
when
a
build
has
ended
like
that
exact,
and
that
exact
point
like
that
exact
amp,
100
billion,
I
know
that
we
can
go
into
on
one
another
of
api.
That's
going
to
be
information
about
the
building
that
says:
okay,
the
bill
has
finished
but
just
understand.
C
I
understand
what
you're
saying
so
I
got
so
I
was
completely
yeah
off
point
then.
So
in
this
case
you
want
to
understand
from
jenkins
itself
like
when
our
build
starts
and
ends
like
those
exact
moments
like
those
events
in
jenkins
inside
which
you
can
read
properly.
So
that's
what
you
want
to
know.
Okay,.
A
That
means
it's
not
building
yet,
but
it's
a
job
that's
present,
but
if
it's
like
blue
underscore
anime,
it's
it's
like
something
that's
building
and
then
going
inside
of
it
just
understanding
the
cloud
event
that
we
have
to
trigger
the
job
that
hasn't
started,
then
another
cloud
event
to
trigger
just
to
say:
okay,
the
job
is
running
right
now
and
and
then
from
there
going
into
the
buildings.
I
have
the
code.
I
I
I
think
it
I
I'm
thinking
that
it
should
work,
but
it
doesn't.
A
C
This
was
something
I
had
added
to
the
design
document.
I
think
at
some
point
I
think,
but
yeah.
This
is
something
that
could
help,
probably
because
they've
they've
already
implemented
this
so
kind
of
you
know
listening
mechanism
where
you
know
on
finished
or
like
started,
they
do
certain
things.
So
could
probably
get
some
inspiration
from
here
and
just
extended
to
kind
of
support
cloud.
A
A
Do
you
think
that,
like
would
you
happen
to
know
why
even
the
jenkins
rushed
api
java
client
working
like
I'm,
pretty
sure
there
might
be
an
issue
with
my
system
itself,
because
it
might
be
trying
to
find
different
dependencies?
I
did
look
into
the
tree
and
I
did
not
find
any
complete
independencies
from
like
you
know.
If
we
were
using
it,
it
would
have
been
so
much
easy
to
just
pull
and
get
whatever
we
need,
but
it
helped.
C
C
C
Sorry,
my
bad
okay,
so
yeah
I
was
saying
to
start.
I
think
it's
like
a
pretty
easy
thing,
like
kind
of
just
you
know,
pull
the
rest
api
endpoint
and
see
what
is
the
state
of
the
job
at
a
certain
point,
but
ideally
it
should
like
hook
into
the
eventing
within
jenkins
itself,
and
then
you
know
send
out
events
that
way.
Otherwise,
if
you
think
about
it,
then
we
are
doing
like
a
two-way
thing.
We
are
first
going
to
pull
and
like
upon
some
change.
C
If
we
see
a
change
we
are
going
to
keep,
we
are
going
to
keep
doing
that.
If
there
is
a
change,
then
we
will
send
something
else
out.
So
there's
like
a
two-way
thing
happening
on
two
different
directions.
So
instead
you
wanted
to
go
in
like
a
smooth
single,
like
flowing
fashion
so
like.
If
something
happens,
then
the
plugin
gets
to
know
and
then
like
internally
and
the
plugin
will
send
out
the
cloud
event.
C
You'll
always
have
the
thread
be
running
in
the
background,
otherwise
for
polling
and
it
could
you
can
you
can
see
that
as
a
overhead
in
one
way
and
easy
way
to
kind
of
get
rid
of,
that
would
be
to
kind
of
just
hook
into
this
internal
jenkins
event
thing,
which
the
statistics
gather.
Our
plugin
has
figured
out.
C
A
A
I'm
just
because
what
I
have
right
now
is
that,
like
the
user
is
going
to
enter
the
url
for
this
thing,
I'm
sorry.
I
wasn't
able
to
show
that
part,
but
it's
like
already
configured
on
my
system.
It's
just
like
the
user
enters
a
url
for
this
thing
and
as
soon
as
like
you
know,
as
job
is
started,
the
polling
starts
as
well
and
then
similar
to
that
as
soon
as
like
the
polling
starts,
wherever
the
url
is
and
stuff.
So
I'm
just
thinking
of
how
could
it
look
like.
A
A
C
A
Yeah
yeah,
I
mean
yeah,
that's
what
like
I
had
in
the
http
server
that
I'm
running
right
now.
It's
just
receiving
post
requests
from
jenkins,
like
the
jenkins
plug-in
but
like
what
I'm
trying
to
understand
is
if
we
move
the
system
out
like
the
cooling
system
itself
outside
of
the
plug-in,
I
think
that's
I
think
I
might
have
to
read
on
that
to
understand
the
architecture
better.
C
A
Plugin
yeah,
it's
like
it's
being
done
inside
of
the
plugin,
so
it's
so
as
soon
as
I'm
like
running
the
plug-in.
You
know
as
soon
as
that
that,
as
soon
as
a
person
adds
a
plugin
into
theirs,
like
a
user
enters
a
plugin
into
their
system,
it's
going
to
like.
Obviously,
then
it
becomes
a
part
of
their
infrastructure
and
and
and
like
pulling
starts
right
at
that
moment.
So
as
soon
as
a
person
like
clicks
on
build
now
it
it
continues
to
be
pulling
the
apis,
which.
C
C
A
So
basically,
it's
as
like,
as
I
said
earlier,
to
starting
from
the
api
like
the
first
account,
which
is
just
like
apigee
song,
which
just
gives
information
about
the
jenkins
system,
like
the
number
of
force,
the
number
of
jaws
which
are
in
the
system
at
that
moment
and
then,
if
it
figures
out
that
if
a
certain
job
is
building
based
on
the
color
of
the
job,
then
it's
going
to
go
further
and
then
it
starts
the
other
one
which
is
like
looking
in
the
job
itself.
So
the
test
jobs.
A
A
A
And
I
will
still
have
like
a
bit
of
code
for
when
it
ends.
I
mean
it's
not
different.
It's
just
like
going
a
step
further
into
the
field
itself
and
seeing
if
it's
still
building
or
like
the
build
itself,
is
still
building
or
if
it
has
stopped
building
and
then
generate
another
event
which
would
be
okay.
The
bill
was
failing.
A
A
C
So
I
think
this
this
this
mini
demo,
was
like
a
good
place
to
start,
but
imagine
now
at
scale
like
if
you
have
a
lot
of
jobs
that
you're
pulling
for
using
the
plugin,
the
plugin
will
have
so
many
threads
running
in
the
background
for
each
different
job.
That
is
there
like.
It
will
at
some
point,
be
like
a
large
overhead
created
by
the
plugin
for
all
of
these,
so
just
it
like
in,
like
in
my
head,
when
I
think
about
it.
C
B
C
Have
to
that's
why
you
have
to
understand
like
how
these
smaller
things
in
jenkins
work
somehow,
like
the
build
staff
listener,
like
I'm
looking
at
the
build
step
listener
over
here,
the
build
step
is
research
extend
so
in
the
start,
plugin
the
build
step
starts
listener,
which
extends
the
build
step.
Listener
is
a
jenkins
class
itself,
so
it's
so.
It's
comes
under
hudson
model
build
step
listener
similar.
We
could
use
that
and
similarly,
there
is
a
run
stats
listener
and
there
is
a
there
is.
C
There
is
a
class
called
run
listener
which
is
being
used
for
this
one,
and
this
one-
and
I
think,
run
over
here
means
a
build
run
itself.
So
in
this
case
they
are
getting
the
run
which
is
happening
at
that
time,
and
it
says
okay,
if
the
run
is
started.
If
it's
in
progress,
if
some,
if
environment
variables
are
there,
so
a
lot
of
information
is
being
picked
up
from
these
listeners
themselves.
B
C
C
A
A
A
Yeah,
I
think
like
this
is
like
a
really
good
place,
and
definitely
can
you
know
like
start
implementing
this
and
then
testing
out
with
the
the
evidence
part
of
the
cloud
events,
and
if
we
have
that
down,
you
know
it
basically
have
an
idea
of
how
just
working
with
cloud
events
and
gentlemen's
can
look
like.
So
I
think
the
other
step
would
be
easy.
The
easier.
C
That's
great,
very
frankly,
I'm
very
impressed
that
we've
already
reached,
like
sync
state,
to
like
testing
this
out,
because
this
was
supposed
to
be
only
like
community
bonding
chatting
and
like
how
many
party
time
that
we
have
you
know
figuring
out
who
what
this
is
about
and
getting
to
know
each
other
and
stuff
but
yeah.
This
is
great.
You've
already
recessed
it
and
awesome.
C
A
D
A
A
C
C
Yeah,
but
this
is
great,
let
me
know
how
that
goes,
then,
for
you
with
the
buildlessness
stuff
and
yes,
kara
like
I
found
this
project.
While
I
was
writing
the
design
doc
and
it
just
seemed
like
the
perfect
thing
like
this
is
exactly
what
we
are
trying
to
do.
All
we
need
to
do
is
send
cloud
events,
so
yeah
yeah,
it's
just
it's
just
pretty
straightforward.
When
you
look
at
statistics.
D
Yeah,
it's
a
great
it's
a
great
starting
point
and
you're
you're
doing
awesome
strategy,
I'm
so
impressed
as
well.
The
only
this
is
not.
This
is
not
your
work.
This
is
vis-a-vis
jenkins
and
some
of
the
code.
You
will
see
internally
from
the
from
the
user's
perspective
at
this
point.
There
are
certain
words
that
shouldn't
be
showing
anymore
certain
older
terminology
which
we're
removing
from
the
project
like
master
slave,
so
in
your
own
work
that
you're
writing
instead
of
using
a
word
like
slave.
D
A
I'll,
just
maybe
ask
you
guys
once
again
about
the
events
itself.
I
know,
let
me
talk,
let's
look
into
how
or
like
what
events
is
tactile
emitting
and,
as
I
said,
about
jobs
itself,
there
can
be
when
a
job
has
started
when
a
job
is
building.
When
a
job
succeeded
like
the
job
is
ended,
it
succeeded
and
the
job
failed
starting
part.
C
Well,
it's
good
that
you're
thinking
in
this
way
at
this
point,
but
to
start
it
would
be
a
good
place
to
completely
map
out
all
the
events
sent
out
by
jenkins
first
and
then
map
them
out
to
like
a
larger
context.
So
in
tecton,
what
they've
done
they've
done
something
similar
they've
they've.
They
have
this
event,
type
called
unknown,
which,
which
is
kind
of
like
condition,
passing
kind
of
like
an
event
type.
Let
me
send
you
the.
C
Okay,
so
electron
cloud
events.
They
they've
got
this
cloud
event
type,
especially
for
unknown,
where,
if
a
condition
is
changing,
they
really
don't
know
what's
happening
there,
so
they
called
it
unknown,
not
condition
changing.
So
in
such
times
where
there
is
not,
there
is
a
certain
event
which
is
not
explicitly
being
given
out
by
jenkins.
C
It
will
be
good
to
like
just
map
all
these
events
that
are
being
created
by
jenkins
directly
onto
cloud
events
and
then
later
on
figure
out
with
them.
Okay,
what
is
missing
over
here
and
then
we
can
like
add
certain
things.
You
know
unknown
events
that
are
in
there,
which
probably
are
there
but
are
happening
in
the
background,
and
we
just
don't
know
so,
and
those
also
might
need
you
know
a
different
mechanism
of
sending.
C
A
C
So
you
at
that
point
you
know
like
okay,
these
are
all
the
mappings
that
I
need
to
do,
and
this
is
the
first
like
the
life
cycle
of
these
resources,
because
there
are
not
resources
just
for
like
jobs
and
bills
and
stuff
the
resources
for
projects,
and
I
think
for
views
and
these
very
shanky
things
that
are
there.
So
actually,
let
me
see
if
I
can
pull
that.
A
C
I
don't
know
to
what
extent
but,
like
I
don't
know,
if
any
like
some
of
these,
like
cloud
executor,
workspace
even
have
listeners
of
their
own,
but
it
will
be
a
good
place
to.
I
think
I
really
feel
like
the
hudson
model
listeners
package,
which
is
there
or
you
could
just
like
check
what
all
this
now,
whatever
listener
classes
are
there
under
there
and
that's.
C
The
best
place
you
could
figure
out,
you
know
how
to
from
where
you
can
like
map
these
cloud
events-
that's
probably
the
best
place,
because
this
is
just
documentation
and
documentation,
sometimes
isn't
like
the
source
of
truth.
That's
the
code
itself,
so
you
can
just
probably
look
at
those
listening
classes.
A
C
C
Okay,
so
I
found
I
think
there
are
like
six
listeners
over
here
which
you
could
use
and
no
yeah.
There
are
five
listeners,
so
there's
item
listener,
run
listener,
saveable
listener
cm
listener,
but,
based
on
what
we
saw,
there
are
some
other
listeners
as
well,
which
we,
I
don't
think
we
are
seeing
them
over
here.
Right
now,.