►
From YouTube: ☀️ GSoC CloudEvents plugin mentor meeting 2021.7.12
Description
The First Coding Phase has completed! This week will be an evaluation week. CDF GSoC participants are invited to present their work next week.
Shruti demos her latest work with discussion and feedback. ☀️
Shruti raised questions on ordering and/or locking of event order when have a larger system of events. One example would be if a build has started, but an event is received which means the build should stop, how is this handled?
Vibhav: these questions are great and part of a larger discussion on how to handle events in event based systems -- next week the Events SIG is meeting and it would be fantastic to raise these questions there and discuss further.
A
Last
week
there
were
a
few
things
that
oh
so
paul,
and
I
also
met
on
thursday
or
wednesday,
and
then
we
were
able
to
talk
that
we
are
going
to
be
like
putting
the
first
release
for
the
plugin.
So
getting
things
ready
for
that,
which
is
an
important
sort
of
goal
here
to
you,
know,
make
sure
that
everything
that's
being
emitted
from
the
cloud
events
jenkins
as
a
source
is
big
data
that
we
need.
A
So
one
of
the
first
thing
was
going
back
and
making
sure
that
all
of
the
the
data
and
the
fields
that
we
have
on
for
all
of
the
the
classroom's
data
field-
I
guess
it's
it's
updated
and
it's
also
being
like
it's
sort
of
changed
between
different
listeners.
So
I
can
show
you
an
example
of
I.
I
wasn't
really
sure
what
all
data
we
were
going
to
need.
A
A
So
I
didn't
want,
you
know,
create
a
date
or
updated
date
or
build
a
field,
so
build
field
is
containing
the
build
model,
which
is
information
about
the
the
build
of
a
run
itself.
So
things
like
the
the
time
stamp
when
something
started
or
when
something
ended.
The
the
display
name,
the
parameters
which
are
being
passed.
Another
thing
I
actually
just
give
sort
of
a
demo
about.
A
So
I
I
I
said
that
I
have
it
running
kubernetes.
So
what
I'm
going
to
do
is,
instead
of
have
it
displayed
from
my
local
jenkins
server,
I'm
going
to
display
the
plugin
from
kubernetes
itself
and
then
we
can
look
at
the
data
in
the
fields
which
are
being
emitted
for
different
events
which
are
emitted.
So
just
just
keep
keep
that
in
mind
that
this
is
not
my
local
system,
but
this
is
running
off.
B
A
I'm
just
going
to
make
sure
that
this
is
the
okay,
so
I
have
I.
I
did
an
earlier
version
where
I
had
two
replicas
running
on
three
different
nodes,
but
these
all
of
these
nodes
are
actually
sort
of
like
high
high
charging
machine,
so
they
do
charge
me
a
lot
for
the
vms
which
are
running
like
the
nodes
which
are
running
so
I
just
tuned
them
down
to
two,
and
I
have
a
single
replica
running
on
both
of
these.
Why
not
use
mini.
B
A
A
A
So
this
is
going
to,
since
you
know,
all
of
the
events
are
selected.
I
can
start
with
a
few
classes
that
I
was
talking
about
entered
waiting,
so
the
two
pauses
will
be
inside
of
the
event
data
only
when
it's
either
in
the
entered
waiting
stage
or
it
has
moved
from
one
stage
to
another,
and
this
is
the
entry
time
I
the
so.
A
A
So
the
source
is
this,
so
this
is
the
yeah.
So
this
is
like
the
the
resource.
This
is
going
to
be
the
job
and
then
the
job
name
itself.
Accu
left.
It
has
the
entry
time
and
the
exit
time
both,
but
it
does
not
have
like
q
positives.
It
does
not
have
any
sort
of
information
about
what
happened
to
that
particular
stage
that
the
queue
is
in.
A
So
it's
just
not
present,
so
it
did
not
have
the
need
to
put
it
here,
and
so
this
was
one
thing
in
in
the
in
the
build
or
like
the
job
started,
a
job
ended.
I
did
try
putting
in
scm
state,
for
example
like
from
github,
or
I
tried
it
from
github,
and
what
this
was
doing
is
every
time
a
job
had
started.
A
It
was
pulling
the
other
version
of
the
this.
The
comment
id
or
the
comment
shot,
the
older
version
and
it
like
job
started,
would
be
the
older
version.
For
example,
the
previous
shot
is
zero,
five
one.
So
whenever
a
job
is
started,
it
would
be
051
and
when
it
moves
from
one
stage
to
another,
completed
or
finalized,
it
would
pull
the
newer
version
and
then
when
I
can
also
also
show
that
I'm
going.
A
A
A
And
alongside
that,
we
have,
we
also
have
the
updated
date
and
whenever
a
job
is
created,
that
would
have
the
created
date
instead
of
the
updated
date.
So
so
I
just
thought
instead
of
having
like
started
data
as
no,
I
just
maybe
not
put
it
here
and
because
I
was
looking
through
events
from
different
other
systems
like
native
and
techton,
and
all
the
other
systems
that
you're
using
or
everything
without
events.
A
A
A
It
gets
a
new
commit
id,
and
so
this
is
the
updated
comment
id
so
whenever
a
job
would
start.
So
this
particular
event
right
here,
scn
state,
url
branch
commit
the
comment,
would
have
the
older
branch
for
jobs
started
and
then
moving
to
job.
completed
her
job
finalized.
It
would
have
that
updated
new
commit
id
and
then,
if
that
job
was
started
again,
maybe
by
maybe
I
triggered
it
from
the
ui
or
maybe
it
was
just
started.
A
By
pulling
the
scm,
it
would
have
again
the
older
version
of
the
the
comment
id
than
what
actually
is
the
new
updated
version.
Does
that
make
sense?
And
I'm
not
I'm
not
really
sure
why
that
is
happening.
I
tried
it
with
different
systems
and
that
still
was
given
the
same
sort
of
edit.
I
don't
know
if
that's
an
actual
letter
or
it's
it's.
It's
just
how
it
is,
but
will
you
guys
happen
to
have
an
idea
on.
A
A
Yes
so
so
I
had
sem
added
to
like
the
version
that
I
was
running
on
my
local
jenkins
server
and
I
have
you
know
like
whole
scm
and
whenever
like
something
is
pushed
to
the
master
branch
just
triggered
that
particular
job.
So
do
you?
Can
you
see
the
sem
state
like
field
on
the
unlikelias
code
to
the
right
of
the
screen.
A
Yes,
yes,
so
so
I
don't
have
it
added
to
this
particular
job,
but
let's
look
at
job
done,
so
this
is
the
job
dot
started.
So
whenever
I
push
up
whenever
I
push
to
the
main
branch-
and
this
is
the
like-
this
is
the
branch
that's
being
tracked
inside
of
jenkins
and
then
it's
pulling
this
particular
brand.
A
So
whenever
I
push
to
it,
it
would
have
a
new,
updated
comment,
shortcoming
id
and
so
whenever
you
know
it's
polling
and
then
a
job
would
start
the
scm
state
for
job
dot
started
event
commit
would
be
older
id.
The
older
comment
id
instead
of
the
newer
commit
id
and
then
it
would
move
to
job.completed
or
job.finalize,
and
here
inside
of
the
job.com
completed
or
jot
dot
finalize
scm
state,
it
would
have
the
new
the
recently
pushed
comments
id
but
it
but
for
the
job
dot
started.
A
It
was
still
giving
me
the
older
id
and
every
time
it
would.
It
would
refresh
every
time
like
a
newer
comment,
is
pushed
our
newer
job
is
just
started,
but
it
still
was
not
the
one
which
is
currently
the
most
latest
comment
which
which
pushed
to
which
like
started
this
job.
It
was
the
the
previous
version
so
like
like
comment
id
minus
one
of
whatever
stuff.
A
A
B
B
Yeah,
that's
all
that's
good,
I
think.
For
now,
what
we
should
do
is
what
you
have
here
is
like
pretty
good
stuff.
What
we
should
do
right
now
is.
We
should
focus
on
the
upcoming
demo
that
we
have
so
for
that.
So
on
on
friday,
we
had
a
meet
thing
right,
in
which
we
discussed
that,
I
think,
would
be
better
here.
B
It
is
a
new
version
of
the
cloud
events
plug-in
so
that,
along
with
your
demo,
we
have
a
new
version
as
which
people
can
use,
and
then
we
we
can
go
into
like
the
feedback
mode
for
the
second
half
of
the
project,
so
that
we
can
improve
along
those
lines
as
well.
As
you
know
what
we
think
we
should
probably
do,
and
that
would
help
us
give
a
better
idea
of
how
people
end
up
using
the
plugin
itself.
B
So
for
this
I
think
for
now
it's
let's!
Let's
not!
Let's
not
get
hung
up
on
this
one
small
thingy.
What
we'll
do
is
we'll
just
focus
on
the
release
and
then,
as
we
discussed-
and
I
would
love
to
have
your
opinion
on
this
so
guys,
so
I
was
thinking
initially.
We
should
just
relieve
this
for
the
sync
implementation
and
make
it
perfect.
I
think
it's
already
perfect.
B
Actually
we
just
maybe
need
a
little
more
documentation,
a
little
more
tests
and
after
we
release
that,
then
we
can
continue
working
on
the
moving
the
configuration
from
global
configuration
to
the
cloud
events
under
managed
jenkins
and
then,
after
that
we
could
probably
do
you
know
jenkins.
Sorry
jenkins,
as
a
source
I
mean
not
saying
jenkins
are
the
source,
then
we
work
on
moving
the
configuration
and
then,
after
that
we
can
work
on.
You
know
doing
sinks
in
jenkins.
C
C
B
Yeah,
I
agree
with
that
and
I
think
if,
in
the
second
phase
we
go
into
this
feedback
loop
with
the
users,
I
think
it
will
be
much
better
as
as
like
experience
and
g-shock
as
well
and
like
because
the
first
phase,
you
know
you
kind
of
like
build
it
up
in
the
second
phase,
you
can
get
in
more
touch
with
the
community.
Maybe
do
like
some
focus
more
on
kind
of
like
evangelizing,
a
little
bit
of
the
plugin.
C
A
And
yes,
that's
a
really
good
idea
and
I
have
added
more
tasks.
I
like,
I
think
that,
yes,
the
documentation
is
really
important
for
it
and
I
am
creating.
I
have
it's
just
a
text
document
where
I
have
hold
all
of
this
event
data
and
you
know
how
maybe
techdon
has
or
even
how
other
cloud
event
systems
even
k
native,
has
good
documentation
on
this
and
what
type
of
event
gets
submitted
and
here's
what
it
looks
like
alongside
headers,
and
we
can.
A
B
I've
noticed
one
thing
with
jenkins,
so
plugins
is
that
the
readme
that
we
have
for
it
is
directly
shown
on
the
plugins
page.
So
if
you
go
go
to
plugins.jenkins.io,
I
think
that's
what
it's
called
the
readme
that
we
have
for
readme.,
that
we
have
is
the
same
thing
that
is
shown
there.
So
we
can
stuff
as
much
information
as
we
want
on
the
readme
and
keep
that
as
like
a
single
source
of
truth
for
the
entire
plugin,
and
that
would
that
be
completely
fine.
B
If
anything
would
be
much
better
because
the
users
don't
have
to
go
to,
like
you
know,
different
dogs.
If
so,
if
we
want
to
kind
of
differentiate
between
user
docs
and
developer
docs,
we
could
do
we
could
do
that,
but
like
user
docs
would
be
the
readme
and
the
developer
docs
could
be
something
else,
but
I
think
to
start
off,
we
can
stuff
everything
on
this
readme
I
think
that'll
be.
That
would
be.
A
B
A
I
did
just
mention
about
jenkins
instinct
and
what
we
are
thinking
of
doing
you
know
just
to
sort
of
give
an
idea
of
here's
what
people
can
expect,
and
it
is
a
bit
aligned,
above
with
the
the
sockeye
that
you
showed
earlier
and
figured
that,
and
I
did
also
create
a
slightly
gamma
file
of
what
it
can
be
or
what
it
can
like.
What
jenkins
is
the
same
configuration
can
look
like,
so
if
maybe
we
can
talk
a
bit
about
that
too
right
now,.
A
Okay,
so
what
I
was
thinking
is
inside
of
you
know
having
filters
so
a
person.
Is
configuring
jenkins
as
a
sync,
so
there
would
be
sort
of
this
field
of
filters
where
it
could
be
cloud
events,
metadata
cloud
events,
event,
body
or
event
data,
so
those
those
can
be
like
the
two
broad
fields
where
someone
might
want
to
filter
it
by
the
cloudvents
metadata
or
by
the
cloud
events
data
itself.
A
So
configuring
that
might
help
us
figure
out
what
information
can
we
extract
from
either
the
the
headers
or
the
body
as
in
like
the
metadata
or
the
event
data,
and
I
also
thought
that
inside
of
you
know
the
actions
that
a
certain
user
might
want
to
trigger.
What
we
can
do
is
have
an
option
of
okay.
Is
this
action
parameterized
or
not?
Just
how
you
know
jenkins
does.
A
Is
this
build
parameterized
and
if
it
is,
you
might
want
to
add
parameters
so
actions
a
person
chooses
yes
to
start
build
of
a
job
and
a
person
then
selects
yes,
this
particular
action
is
parameterized
and
this
will
be
receiving
parameters
from
the
event
which
is
coming
in
right.
So
this
is
just
happening,
a
configuration
is
happening
and
jenkins
is
a
sink.
So,
yes,
this
particular
action
is
parameterized
and
inside
of
that
particular
you
know
if
it's
parameterized
or
not,
it
can
be
okay.
B
B
A
B
A
So
the
what
I
had
I
was
like
sort
of
thinking
is,
I
did
not
have
like
regular
expression
fields
inside
of
the
like
the
metadata
or
the
data
itself,
but
more
inside
of
the
actions
where
a
person
is
selecting
parameters,
but
we
can.
You
know
we
can
like
put
that
both
in
both
of
those
places
when
a
person
is
selecting
filters
and
when
a
person
is
entering
parameters
for
the
particular
action.
A
I
was
just
like
looking
at
different
events,
and
you
know
look
looking
at
them.
I
just
I
thought
that
if,
if
a
certain
sort
of
a
field
is
present
inside
of
the
cloudvan's
metadata,
then
it
will
be
present,
like
whatever
a
person
might
be
looking
for,
for
example,
if
it's
a
it's,
it's
a
tactile
event.
A
If
someone
is
looking
for
a
task
or
on
a
particular
idea
of
potassium,
it
is
going
to
be
present
inside
of
a
body
so
just
giving
users
the
ability
to
also
filter
by
the
body
and
also
enter
parameters
from
the
body
as
well.
It
plus
the
headers
of
course,
and
yeah
I
think
filtering
inside
of
the
headers.
A
B
Maybe
maybe
we
can
come
up
with
examples
for
that,
because
just
like
match
won't
work
in
this
case.
At
those
points
we
we
might
have
to
do
stuff,
like
you
know,
pick
up
pick
up
certain
information
from
the
body
itself,
so
I
think,
in
those
cases
we'll
have
to
work
with,
like
those
cases
will
arise
when
we
are
doing
more
sync
stuff,
and
we
are,
you
know,
doing
real-world
applications
such
as
you
know,
working
with
tecton
or
something,
but
I
think
that
is
still
ahead
in
the
game
right
now.
B
B
B
A
The
parameter
includes
or
like
the
parameter
contains
and
like
includes,
obviously
makes
more
sense
here.
It
includes
this
particular
object
or
if
it's
like
an
object
itself,
it
can
be
like
it
like
contains
this
particular
field,
and
if
it's
like
steadfield,
it
can
obviously
sort
of
go
in
like
a
nested
direction.
A
Of
this
insists
and
like
the
condition,
includes
a
message
we
like
this
particular
message
again
because
each
event,
if
you
like,
go
in
and
look
at
a
canadian
event,
they
have
a
different
way
how
they
are
defining
their
events,
and
you
know
not
everything
here
is
an
array
or
not.
Everything
could
be
an
object,
so
maybe
just
just
thinking
of
how
the
matching
might
not
only
be
matching
of
strings
but
objects
or
or
arrays
or
even
I
don't
know
like
something
is
complex
like
an
entire
field
or
an.
C
B
Look
at
the
existing
or
like
the
user
will
have
to
look
at
the
existing
payloads
and
then
figure
out
the
rejects,
based
on
that.
What
is
better,
if
that
the
user
doesn't
have
to
go
through,
go
through
that
path.
So
I
was
thinking
if
we
could
do
something
like
dollar
or
dollar
period,
and
then
you
know
whatever
task
run
dot
creation,
timestamp
and
you
know
taskrun.metadata.creations
timestamp,
so
that
dollar
that
the
user
gives
it
will
replace.
So
it
doesn't
have
to
be
dollar.
A
So
can
we
think
of
any
events
which
might
not
be
like
parameterized,
but
just
like
the
last
time
that
we
were
talking
and
the
idea
of
stopping
the
build
of
the
job
came
up
right
and
mauricio
suggested
something
really
good
which
was
like,
which
was
if
a
certain
parameter
is
present
inside
of
it,
then
stop
that
particular
build
else.
Just
stop
the
last
build
that's
running,
so
I
I
was
just
thinking
that
it
can
be
complex
to
understand
where
to
get
that.
A
A
A
A
B
They
usually
work
with
generate
names
right
so
like
it
could
be.
Something
like
like
this
could
be
something
we
discuss
with
the
cd
foundation,
guys
in
which
we
figure
out
like
a
way
in
which
there's
like
a
sin,
act
happening.
So
like
imagine,
the
cloud
event
that
is
being
sent
by
techron
to
jenkins
is
a
sin.
It's
like
a
synchronization
phase
and
then
an
event
is
triggered.
B
B
Which
build
has
been
triggered,
so
there
will
be
a
build
number
there
so
and
after
that
like
and
that's
how
that's
how
technolon
will
know
that
this
build
has
been
created
by
jenkins.
So
that's
like
a
syn
ack.
So
that's
like
the
second
phase
of
tcp
right.
So
this
we
might
have
to
send
out
a
new
event
back
to
tech,
town
and
then,
based
on
that
you
know,
techno
would
do
something
be
like
okay.
B
This
is
completed,
but
you
know
actually
you're
discussing
something
that
has
I
I
don't
know
if
it
has
been
discussed
before
so
this,
and
I
think
there
are
like
talks
going
on.
I
think
there
is
already
like
work
being
done
to
kind
of
store
the
state
of
events,
and
you
know,
link
them
together,
and
this
is
this
is
the
problem
that
we
are
discussing
right
now
so
like
linking
events
together
is.
B
B
This
basically,
this
basically
tells
us
that
we
need
to
like,
even
in
the
tecton
payload,
we
probably
need
to
have
like
a
synchronization
block.
I
don't
know
how
that
works,
but
we
probably
need
to
have
that
and
probably
need
to
go.
Look
back
at
you
know
the
like
some
like
protocol,
such
as
tcp,
and
see
how
they
store
this
information,
and
you
know
how
this
could
be
interpreted
in
something
like
if
events
which
is
not
a
which
is
not
a
lower
level
protocol.
B
A
Yeah,
that's
that's
right.
I
I
hope
that
so
the
next
cloud
event
safe
meeting
is
on
the
19th
and
I
have
like
I'm
obviously
really
wanting
to
join
and
I
hope
that
I'll
be
able
to
join
and
maybe
take
some
of
our
questions
there
and
also
just
hear
about
what
or
how
they
have
built.
The
current
adapters
and
system
for
techton,
jenkins
and
canada.
B
A
B
C
C
Okay,
thank
you.
Hopefully,
hopefully
I'll
be
able
to
announce
that
soon
and
also,
if
you
can
think
of
a
better
time,
I
try
to
make
the
times
I
mean,
I
guess
it's
because
I'm
in
europe,
so
I
wanted
to
make
it
european
friendly
and
then
it
would
be.
I
really
wanted
to
make
it
apac
friendly,
because
that
is
really
important
for
all
our
students
this
year,
as
well
as
most
of
the
mentors
or
a
lot
of
the
mentors.
C
C
C
A
Yes,
I
I'll
go
through
it
again,
and
so
I
I
still
think
that
on
the
19th,
we'll
be
able
to
do
this
meeting
and
then
the
meeting
right
after
which
is
for
cloud
events
and
moves
the
the
demonstration
to
20
and
the
23rd,
if
you
guys
are
okay
with
it,
of
course,
but
if
not,
I
I
claudius
said
they
they're
recording
the
meeting,
so
we
can
just
maybe
post
our
questions
on
the
the
slack
channel,
for
I
think
it's
clock.
It's
called
cloud
events,
I'm
not
really
sure.
C
A
I
don't
have
anything
to
add
right
now
and
I
will
send
the
as
soon
as
I'm
able
to
configure
the
the
get
scm
thing
that
I
was
talking
about.
I
will
send
it
to
you
guys,
maybe
a
video
or
maybe
just
screenshots,
and
also
working
on
like
right
now,
I'm
basically
working
on
adding
more
tests
and
also
just
making
sure
that
the
data
that's
being
emitted
and
it
kind
of
makes
sense
for
the
events.
B
A
B
But
there
might
be,
there
might
be
cases
where
we
would
like
to
keep
the
field
and
the
key
at
least
key
and
whatever
value
is
null.
But
at
that
point,
when
the
user
is
passing
the
data,
we
shouldn't
have
a
null
pointer
exception
on
our
side.
You
know
they
could.
When
the
user
is
passing
the
parameters,
they
could
probably
have
null
as
a
string,
but
I
don't
know
how
I
feel
about
that
really
so.
A
You
know
actually
neither
but
yeah
so
the
fields
which
are
absolutely
sort
of
essential.
I
have
kept
them
even
if
those
are
null,
for
example,
I
don't
know-
maybe
just
even
or
maybe
just
like
job
name,
maybe
that's
just
null
for
some
reason
I
don't
know
but
feels
like
those,
but
where
I
thought.
Okay,
I'm
not
really
sure.
If
this
might
be
helpful,
I
have
I
just
chose
without
really.
A
B
But
I
think
it
should
be
pretty
straightforward,
because,
when
it
comes
to
giving
a
presentation,
I
think
showing
the
cloud.
Events
and
soccer
would
be
actually
very
nice
and
anyways
when
you're
able
to
run
these
run
run
this
on
mini
cube.
So
well
like
we
can.
You
know,
give
users
like
a
end-to-end
kind
of
like
not
at
least
solution
of
anything,
but
like
end-to-end
solution
of
you,
know
your
jenkins
and
then
you've
got
soccer
and
to
like
see
how
this
works.