►
Description
CDEvents as Catalyst to Innovation in CI/CD Ecosystem - Maria Ashby, Armory; Fatih Degirmenci, Ericsson; Brad McCoy; Melissa McKay; + Erik Sternerson
The development of a CI/CD pipeline often involves cobbling together a number of different tools and technologies that enable organizations to release their products on time with quality. However, the technologies used to establish pipelines do not speak the same language similar to us humans due to lack of interoperability across them. CDEvents project works on establishing shared terminology and developing an event protocol to achieve interoperability within the CI/CD ecosystem. Join this discussion to learn more about the different use cases that could be addressed by events, hear what is currently being discussed within various groups and projects such as CDF SIG Interoperability, CDF SIG Software Supply Chain, Jenkins, and Spinnaker and how they envision what CDEvents project could do to enable the innovation within the CI/CD ecosystem.
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
So
while
we
are
waiting
for
everyone
to
get
geared
up,
I
have
the
same
question
as
I
had
before
lunch.
Have
you
heard
of
the
hungry
judge
effects,
because
now
I'm
back
again
with
the
last
session
of
the
day?
But
this
time
I
have
a
lovely
panel
with
me.
Actually
it's
more
their
event
than
my
event,
but
I
thought
once
everyone
is
or
we're
still
getting
rigged
up
you
and
me
fatih.
We
will
need
to
share
a
microphone
here.
I
think
there
are
microphones
for
the
rest
of
you.
A
They
will
be
installed
as
we
go
along,
but
in
the
interest
of
time
I
will
go
through
each
of
the
participants
one
by
one
and
ask
you
to
introduce
yourself.
You
all
have
like
responsibilities
and
position
inside
the
continuous
delivery
foundation,
and
you
have
other
things
going
on
in
your
day-to-day
as
well.
So,
starting
from
the
right
we
have
fatty
digesti.
Would
you
like
to
introduce
yourself.
A
C
D
B
C
To
that
I
was
a
developer
for
20
years
plus,
so
my
passion
is
for
the
developer
and
making
developers
lives
easier,
also
implementing
devops
practices.
That
kind
of
thing
for
now
I
am
a
part
of
the
technical
oversight
committee
for
the
cdf
foundation,
as
well
as
the
chair
for
the
interoperability
special
interest
group.
D
Hello,
everybody
nice
to
meet
you
all.
I
have
not
been
in
this
community
for
very
long,
but
hopefully
I'll
stay
for
a
long
time.
We'll
see
what
happens,
but
I'm
a
developer
advocate
at
armory
and
I
guess
my
goal
is
to
increase
accessibility
through
educational
content
and
really
lower
the
barrier
to
entry
to
continuous
delivery
and
really
welcome
more
people
into
the
community.
C
A
Thank
you.
So
the
main
topic
for
this
panel
is
going
to
be
how
cd
events
can
be
used
to
foster
innovation
in
the
cicd
ecosystem
and,
as
andrea
mentioned
this
morning,
the
cd
events
project
sprung
out
of
sig
events,
which
in
turn
sprung
out
of
sig,
interoperability
and
fatty.
You
were
there
in
the
beginning
right.
Can
you
give
us
some
background
on
the
interoperability,
sikh.
B
Yes,
thanks
eric,
so
I
think
cd
events,
its
roots,
goes
back
to
a
five
years
or
so
like
four
or
five
years,
and
it
was
actually
andre.
Andrea
was
part
of
the
very
first
conversations
we
have
been
having
about
the
challenges
we
all
have
been
facing
with
the
different
cic
tools
and
technologies
and
how
we
can
make
sure
we
get
those
different
technologies
working
with
each
other.
Well,
I
remember
a
conversation
me
and
andrea
had
around
2018
in
vancouver,
openstack
summit
and
andrea
was
actually
leading
openstack
qa
projector.
B
B
A
few
community
members
joined
special
interest
group
interoperability
formed
the
advanced
work
stream
that
turned
into
a
special
interest
group
events
which
andrea
summarized
as
well,
and
then.
Finally,
we
have
here,
like
the
conversation
me
and
andre,
had
like
four
or
five
years
ago,
result
in
formation
of
this
project
and
all
of
us
being
here
today.
So
it's
like
you
can
never
know
what
certain
conversation
could
lead
to
you,
and
that
is
why
it
is
so
exciting
to
see
all
of
us
here
and
looking
forward
to
what
else.
A
C
So,
first
of
all,
I
have
come
on
the
shoulders
of
some
very
amazing
folks
that
were
involved
in
this
project.
Long
before
myself,
and
the
enthusiasm
is,
is
just
it's
catching
and
I'm
really
really
impressed
with
how
the
cd
events
has
progressed
and
see
the
interoperability.
Sig
basically
has
the
feeling
of
a
proud
parent
the
child
was
is
doing
well.
C
It
just
makes
sense
to
have
this
other
abstraction
layer
where
all
of
these
tools
can
work
together
and
now
we're
all
speaking
the
same
language
and
the
capacity
that
a
group
like
cd
events
has
the
the
sig
that
this
came
from.
Is
you
have
representation
from
all
of
the
different
companies
from
all
of
the
different
use
cases,
so
that
you
get
a
lot
of
input
from
you
know
several
different
places
so
right
away,
you
get
credibility,
second,
for
the
hierarchy
of
your
company.
A
Thank
you
so
much
so,
and
now
I'm
going
to
to
let
the
the
panel
yeah
co-mingle
a
bit
so
to
say,
because
we
have
now
heard
about
the
the
foundation
of
from
sig
interoperability
through
sick
events
to
see
the
events,
and
we
heard
melissa
talk
a
bit
about
like
what
what
this
enables
us
to
do.
So
one
thing
I
really
like
to
do
when
I
have
access
to
such
fantastic
people
with
different
backgrounds
and
different
day-to-day
lives,
is
to
ask
simply
what's
the
future,
going
to
be
like.
Where
are
we
going?
E
Okay,
sure,
so
where
are
the
futures
going
with
cd
events
and
in
general
yeah
yeah?
I
see
it
being
abstracted
away
a
lot,
so
all
businesses
should
just
worry
about
that
little
piece
that
they
put
on
the
top.
So
instead
of
having
to
spend
you
know,
I
mean
a
devops
engineer
now
costs
a
lot
of
money.
If
you.
B
A
E
Of
four:
that's
a
million
dollars
a
year.
So
do
you,
do
you
want
to
rebuild
the
well
over
and
over
again
or
do
you
want
to
focus
on
innovation
and
what
your
company
to
you
know,
deliver
business
value
and
value
for
the
customer?
So
I
see
everything
like
melissa
said
talking
to
each
other
out
of
the
box,
and
we
should
be
worrying
about
our
business
value
instead
of
worrying
about
integrating
tools-
and
you
know-
writing
scripts.
E
A
D
But
if
your
community
speaks
a
bunch
of
different
languages,
it
makes
it
really
really
hard
for
you
guys
to
work
together,
and
I
think,
as
we
see
in
the
past
two
years
of
like
being
virtual,
you
can
have
community
members
from
anywhere
and
because
it's
so
spread
out
you're
going
to
have
people
coming
in
with
different
backgrounds,
different
ways
of
doing
things.
So
I
think,
as
the
community
grows,
we
need
to
all
be
speaking
the
same
language,
because
community
is
what
is
fueling
our
innovation.
D
B
Yeah,
I
think
both
brad
and
melissa
highlighted
the
fact
that,
if
our
developers
ourselves,
if
we
can
spend
our
time
on
more
value-adding
activities
rather
than
patching
here,
scripting
there,
that
would
be
a
big
win
for
us
as
well
per
person
developers.
Personally,
as
well
as
the
you
know,
organizations
we
are
part
of
because
then
we
will
be
spending
our
time
to
innovate.
B
New
things
rather
than
get
making
things
running
and
those
things
could,
you
know,
be
broken
on
a
daily
basis,
because
if
we
put
some
glucose
in
place
and
integrate
things
with
each
other,
no
one
can
guarantee
that
those
things
will
stay
working
for
more
than
a
day
or
a
few
hours,
because
communities
always
develop
new
things
and
they
may
be
breaking
the
things
you
have
been
using.
As
part
of
your.
B
You
know,
rapper
code
or
glue
code,
and
the
other
thing
I
want
to
highlight
about
especially
with
cd
ones,
is
like
the
current
use
cases,
mainly
like
the
discus
discussed
around
ci
cd
topics,
which
is
understandable,
but,
as
you
all
probably
are
aware
of
latest
conversations
around
software
supply
chain.
That
gives
us
a
lot
of
opportunities
to.
You
know,
contribute
to
improving
state
of
supply
chain
from
ci
cd
perspective
as
well,
because
cd
events
could
open
up
opportunities
for
us
to.
You
know,
modify
about
new
new.
B
By
new
event,
types
or
identify
some
vulnerable
compound
in
our
container,
which
running
on
production,
so
that
could
be,
you
know
not
by
cd
runs
and
something
else
could
be
monitoring
those
events
and
taking
action
to
you
know
accommodate
those
issues.
So
there
are
lots
of
different
things
we
can
do
within
the
community
and
like,
if
you
have
such
ideas,
I
think
seed
events
gives
that
opportunity
to
come
and
talk
about
those
ideas
and
help
enable
us
to
push
domain
forward.
Cic
domain
or
other
you
know,
domains.
We
are
working
with.
C
Okay,
I
just
want
to
start
with
a
question
hands
up
if
you've
learned
something
new
today
yeah.
This
is
what
these
groups
are
all
about
right.
This
is
where
we
come
together.
We
learn
about
these
things
and
they
don't
stay
in
this
room.
The
goal
is
that
you
return
to
your
teams.
You
spread
this
knowledge
and
we
get
more
visibility
of
things
like
cd
events
and
what
I
hope
for
in
the
future
is
that
as
open
source
projects,
take
this
on
and
take
the
lead,
we're
going
to
see.
C
For-Profit
organizations
follow,
there's
plenty
of
advantage
to
not
reinventing
the
wheel,
and
I
know
that
even
for-profit
companies
will
benefit
from
this.
It
is
so
much
more
fun
to
be
working
on
the
new
feature
rather
than
trying
to
just
get
the
pieces
working
together
and
spending
all
your
time
there.
So
that's
what
I
hope
for
the
future,
and
we
need
all
of
your
help
to
do
that.
A
Thank
you
so
much.
I
would
like
anyone
in
the
audience.
If
you
have
a
question,
raise
your
hand
and
I
would
try
to
bring
the
microphone
to
you
while
we
are
waiting
for
for
such
questions,
so
I
would
like
to
know
what
requests
do
you
have
for
the
seed
events
project?
What
should
we
focus
on?
What
should
we
in
what
order?
Should
we
do
things
because
there's
always
a
million
things
to
do?
We've
mentioned
pocs
sdks
we've
mentioned
community
outreach,
we've
mentioned
documentation
and
all
that
stuff.
A
B
The
other
thing
I
noticed
is
like
we
talk
about
technology
because
we
like
talking
about
technology,
we
like
playing
with
technology
and
may
so
you
highlight
that
point
as
I
think
we
need
to
find
ways
to
make
the
work
that
is
being
done
within
cdos
project,
to
be
understood
by
decision
makers.
Why
this
thing
is
important
like
what
are
the
business
aspects?
Why
are
we
talking
about
like
making
these
different
tools
talking
to
each
other,
using
same
language,
for
example?
B
If
I
want
to
contribute
this
project,
I
need
to
go
and
get
permission
from
my
manager
and
my
measure.
He
or
she
doesn't
isn't
necessarily
to
know
the
details
of
techton
jenkins
spinker.
But
if
I
can,
you
know
talk
about
what
kind
of
benefits
he
or
she
could
get
or
the
organization
could
get,
then
that
could
help
my
case
a
lot
better.
So
technical
documentation
is
great.
B
D
So,
okay,
let's
say
you
get
a
bunch
of
people
in
the
community,
but
if
you
don't
have
good
documentation,
you
just
have
a
bunch
of
lost
soldiers
just
wandering
around
being
confused,
so
I
think
they
go
hand
in
hand
together,
because
you
don't
want
to
spend
that
time
individually,
training
people
you
want
to
already
have
a
temple,
a
template
for
people
to
just
follow
easily,
because
when
you
begin,
I
think
people
stop
because
they
get
overwhelmed.
But
if
we
can
reduce
that
frustration
we
will
be
able
to.
A
So
mariah
you've
worked
as
a
computer
science.
Educator
previously-
and
I
mean
documentation,
is
an
enormously
fascinating
topic
to
me.
You
can
either
write
it
in
a
way
that
only
super
technically
detailed
people
understand
it
and
they
really
appreciate
it
or
you
can
write
it
too
far
in
the
other
direction,
so
it
gets
too
fluffy
for
anyone
to
really
appreciate
it.
What
would
you
do
you
have
any
like
tips
for
us
when
we
start
writing
this
documentation?
How
do
we
get
it
to
the
right
level.
D
D
If
a
seventh
grader
understands
it
pretty
much,
you
can
guarantee
that
everybody
who
should
be
hearing
about
it
can
get
it.
So
a
seventh
grader
has,
you
know,
reading
comprehension
and
they
know
how
to
ask
for
more.
So
when
you're
making
documentation,
you
want
to
give
people
enough
that
they're
hungry
for
a
more
complex
step.
So
if
you're,
you
know
doing
doing
something,
you
want
people
to
just
give
a
bite-sized
bite-size
amount
without
having
them
choke
on
everything.
So
I
think
seventh
grade
is
good.
A
Thank
you.
So
it's
always
tricky
when
you
try
to
teach
someone
something
different.
People
appreciate
different
types
of
of
or
different
avenues
for
learning
like
we
showed
a
super
technical
proof
of
concept
which
is
super
nice
for
or
many
people
find
that
really
really
inspiring.
Many
people
would
prefer
like
hearing
people
talk
or
seeing
stuff
written
down
and
stuff
like
that.
So
I
think
the
the
approach
that
we've
had
today
with
the
varied
types
of
talks
is,
is
going
to
be
really
really
helpful.
D
Oh,
that
sounds
like
a
question
for
an
engineer
on
my
team.
Honestly,
I
think
sooner
rather
than
later.
I
don't
want
to
give
you
an
exact
date,
because
once
again,
that
sounds
like
a
question
for
an
engineer
on
my
team,
but
I
think,
like
these
events
and
like,
if,
if
you
know
you
come
out
from
this
place
and
then
you
join
the
spinnaker
slack
and
then
you
say:
oh
I'm
really
interested
in
cd
events
having
community
outreach
and
it'll
push
it
towards
like
the
front
of
the
long
list
of
things
to
do
for
spinnaker.
C
Give
two
different
answers
so
as
far
as
community,
I
love
the
focus
on
documentation
and
I
think
we
can
actually
use
some
of
your
expertise
here.
Mara.
We
are
in
the
process
of
sharing
this
documentation
in
a
consumable
way
that
will
make
sense
for
different
audiences,
so
not
only
for
the
technical
audiences,
but
also
for
management.