►
From YouTube: CDEvents Working Group - Sept 28, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
A
B
A
B
B
A
A
B
B
B
B
A
Just
to
start
working
on
and
yeah
and
of
course,
you're
also
very
welcome
to
to
look
at
any
of
these.
If
you,
if
you
first
time
that
you
want
to
to
contribute,
I
mean
we
have
things
like
we,
we
have
schema
files
defined
now
and
for
for
the
protocol,
but
we
need
to
to
kind
of
host
them
under
the
domain
so
that
the
the
schema
ID,
the
type
IDs,
is
actually
resolvable
to
to
a
file.
A
All
right,
skinners,
and
if
you
look
at
any
other
schema,
then
the
ID
here
it's
generated
like
this,
but
this
does
not
resolve
today
to
to
a
valid
URL
and
we
own
the
CV.
We
own
the
CD
events
Dev
domain
and
we
have
our
website
there.
But
we
need
to
make
sure
that
this
schema
files
that
are
in
git
update
it
can
be
resolved
for
this
URL
so
that
you
actually
yeah
can
resolve
this
ID.
So
this
is
one
okay,
One
initial
other
things
that
we
have
more
like.
B
B
A
A
Yeah
like
this
is,
it's
probably
very
easy
contained
yeah,
but
things
like
for
Java.
We
have
like
align
the
SDK
to
the
latest
pack
because
the
esdk
was
created
based
on
the
old
spec,
so
it
needs
to
be
aligned,
but
yeah
I,
don't
know
the
Java
SDK
well
enough
to
say
how
to
break
this
down
into
pieces.
But
if
someone
wants
to
work
on
this,
we
can,
you
know,
start
the
discussion
and
see
how
we
can
break
this
down
in
smaller
PRS.
A
B
B
A
B
A
Yeah,
well,
it's
both
to
you
know,
get
our
name
out
there,
and
so
people
knows
that
there
is
this
project
they
can
can
contribute
to,
and
if
we
can
get
some
contribution,
that's
great
and
maybe
yeah
it's
interesting
enough
for
someone
then
to
stick
around
after
Oktoberfest.
You
know
so
I
think
that's
why
I
think
it
makes
sense
to
have
some,
maybe
bigger
items
that
maybe
some
can
work,
start
working
on
them
and
then
you
know
continue.
A
A
B
B
And
they
have
a
lot
of
gaming
is
written
in
C
sharp
for
like
when
they
use
Unity
for
to
run
in
games.
It's
quite
a
Common
Language.
Surprisingly,
okay
I,
don't
know
it's
just
an
idea
like
like
I
mean
at
the
end
of
the
day.
It
could
just
be
a
ticket
and
if
no
one
picks
it
up,
no
one
picks
it
up,
but
it
might
attract
someone
to
want
to
come
and
contribute.
Maybe
just
an
idea.
It
wouldn't
hurt
us
to
just
write
an
issue
for
it.
Maybe.
B
B
A
A
B
I
feel
like
maybe
another
good
issue
would
be
like
demos
or
samples
of
but
of
getting
like
like
because
see
the
events.
Might
the
whole
concept
might
be
hard
to
grasp,
so
if
hacktoberfest
was
getting,
you
know,
obviously
this
is
already
like
kept
an
impact
on
can
already
happen,
but
maybe
having
like
some
sort
of
you
know
like
hackathon
or
something
where
we
actually
get
Turtles
talking
to
each
other
could
be
cool
as
well.
A
B
A
B
B
Yeah
anyway,
if
there's
any
tools
that
really
want
to
see
the
events,
I
I
actually
talked
to
Jenkins
EX
maintainers
last
week
and
they're
quite
they're,
actually
really
interested
in
in
it.
So
we
could.
We
could
have
a
project
here
for
and
work
with
the
Jenkins
ex-maintainers
to
implement
it
into
Jinx,
which
is
as
far
as
I
I'm
aware
that
Jenkins
X
is
just
like
ticked
on
under
the
covers,
so
it
should
be
pretty
easy
to
implement
right
because
it's
probably
already
exists.
B
A
B
A
A
Bryson
CD
inventor,
which
is
something
that
allows
you
to
use
what
we
call
Custom
run
in
in
tecton,
and
basically
it's
it's
a
comparing
this
controller.
So
if
you
write
this
yamu
and
you
put
the
parameters
that
you
want
to
have
in
your
CD
event,
it
will
actually
go
off
and
use
the
go
SDK
to
send
a
CD
event.
B
A
Use
triggers
to
to
get
events
from
whatever
source.
Some
Source
was
a
container
registry
Web
book.
Another
was
a
gitty
Web
book.
Another
one
was
a
cloud
event
from
the
kubernetes
API
or
things
like
that,
and
then
I
use
detected
jiggers
to
extract
the
information
that
I
need
from
the
payload
and
then
three
years
we
create
a
run
and
put
the
information
in
the
right
places,
and
then
this
goes
off
and
send
the
CD
event.
A
B
B
B
Remember
there
yeah,
there's
another
one
called
trigger
mesh,
but
trigger
mesh
is
quite
yeah
heavy
there's
around
eight
pods
just
for
a
simple,
because
I'm
interested
in
the
getting
a
kubernetes
event
and
then
transforming
it
into
like
I,
see
the
event.
Or
you
know
this
does
sort
of
something
similar
directive
or
actually
coming
up
with
like
a
small
piece
of
code.
That
will
do
this
as
well.
So
I'm
gonna
catch
up
with
him
next
week
to
talk
about
the
progress
because
I'm
interested
in
seeing
what
they're
doing
as
well.
B
A
B
A
B
B
A
A
B
B
B
The
integration
with
directives,
because
they
would
be
quite
interested
directive,
is,
do
you
know
what
it
is:
yeah
yeah
yeah
yeah
yeah,
because
because
they're
really
smart
and
fast,
so
obviously
it
would
be
cool
yeah.
It
was
okay,
yeah
I
I
was
it
was
just
that's
it
yeah,
because
that
one
that
one's
been
just
like
brought
up
a
little
bit
at
the
tose
for.
A
B
A
B
B
B
A
B
A
B
B
It
makes
sense
to
me
because
a
lot
of
other
projects
wouldn't
have
to
reinvent
the
wheel,
which
is
it
feels
like
we're
going
back
to
integration,
sometimes
with
some
of
those
things,
because
they're
still
going
to
write
their
own
receiver.
So
it's
like
you're
still
running
integration,
really,
whereas
if
they
had
a
receiver,
they
could
plug
and
play.
And
then
you
know
it's
that
more
interoperability
over
integration.
B
B
A
Yeah
yeah
I
mean
I,
guess,
I.
Think
if
you
use
cases
would
be
like
I,
don't
know
if
you,
if
you
have
built
messages,
for
instance,
and
you
want
to
say
triggers
and
deployment,
and
you
can
have
some
policies
where
we
say:
okay
well,
this
builds
was
tested,
for
instance,
or
this
builds
assigned,
or
this
build
comes
from
this
repo
or
I
mean
you
could
have
you
know
any
number
of
rules
that
you
can
imagine
you
want
to
use
as
gates.
B
B
B
B
A
A
A
A
A
A
B
B
A
B
B
B
B
A
B
All
right,
cool,
I'll,
I'll,
look
through
the
tasks
as
well
and
I'll,
see
if
I
can
map
some
contributors
to
the
tasks
as
well.
I
know
I,
know
a
lot
of
people
looking
to
contribute,
but
they're
quite
entry
level
that
they
generally
are
the
new
contributors,
so
yeah
I'll,
try
and
think
of
a
way
of
maybe
I'll
look
at
if
we
can
break
these
tasks
down
a
little
bit
as
well.