►
From YouTube: CDEvents Working Group (EMEA/AMERICAS) - May 16, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
No,
unfortunately,
we
have
a
travel
restriction,
so
I
was
unable
to
go,
unfortunately,
but
for
my
manager
went
so
that
that
was
at
least
one
of
us
went.
That
was
not
too
shabby,
but
yeah
yeah
I've
been
actually
sick,
like
oh
yeah.
These
last,
like
few
weeks
well
I've
been
trying
to
like
get
it
under
control
like
sick,
as
in
like
just
like
more
paranoia
like
I,
had
like
really
high
blood
pressure,
so
I've
been
like
trying.
B
B
C
B
C
B
C
A
A
B
C
B
A
A
C
B
It's
actually
basically
done
so.
The
reason
why
the
hold
up
is
I
need
to
go
through
internal
teams,
which
I
have
a
scheduled
meeting
for
Thursday
with
two
big
teams
here
at
Apple,
and
the
reason
for
these
meetings
is
basically
to
make
sure
that
our
goals
and
proposals
align
with
their
use
cases,
because
you
know
the
whole
goal
is
to
make
this
work
for
everyone
right
yeah.
So
what
I
was
thinking
is,
since
this
is
a
little.
B
This
is
taking
a
little
bit
longer
to
get
these
meetings
and
you
know
kind
of
get
more
of
the
internal
Apple.
You
know
people
all
on
board
on
the
same
page,
because
you
know
it's
a
fairly
big
company
and
you
know
I
I
want
to
what
I
was
thinking
is
I
want
to
create
a
draft
PR
and
then
maybe
we
can
iterate
their,
maybe
well,
there's
only
a
few
action
items
that
I
have
so
I'll
start
from
from
the
top.
B
B
To
oh
yeah
yeah,
just
a
different,
commit
yeah,
yeah,
okay,
cool
cool,
so
what
I
will
do
then
is
I
will
create
a
draft
PR
after
this
meeting,
so
you
guys
can
at
least
get
an
idea
of
like
what
I'm
you
know
what
we're
thinking
about
and
then
on
Thursday.
If
that
meeting
goes
well,
I
can
then
move
it
out
of
draft,
and
we
can
put
it
in.
You
know
ready
to
be
reviewed
if
that
works.
For
you
perfect
sure,.
D
C
D
D
D
C
C
A
D
D
B
Yeah
yeah
I
didn't
want
to
interrupt
their
but
yeah
yeah.
So
this
is
the
lynx
proposal,
so
it
has
quite
a
few
things
in
here
kind
of
some
outlines,
so
the
basic
gist
of
The
Proposal.
It's
basically
what
we
talked
about
kind
of
the
hybrid
approach.
I
do
have
a
comment
in
here
that
is
hard
to
see,
but
but
it
goes
over,
like
semantics
is
the
first
section
which
is
which
is
nice.
You
know
just
having
you
know
something
that
we
all
agree
upon.
B
You
know
like
what
it
is.
You
know
people
that,
like
especially
here
at
Apple,
we
don't.
We
don't
have
too
many
familiarity
with
links
in
general.
Nor
do
we
have
any
like
even
with
tracing
people,
don't
really
know
tracing,
so
they
don't
really
have
this
concept
of
like
connecting
events
or
anything
like
that
to
go
over
some
descriptions
of
of
iPhone
links,
kind
of
the
semantics
there
and
the
biggest
thing
here
is
an
Eiffel.
B
It
would
be
a
an
array
of
links
like
you
know,
everything
that
had
happened,
but
in
this
proposal
we
actually
state
that
links
will
always
be
the
direct
parent
of
of
whatever
thing.
So,
if
you
need
to
get
like
a
grandparent,
you
actually
need
to
call
an
API
which
I
talked
about
this
link
service,
which
can
be
a
service,
a
part
of
the
whole
city,
events,
event,
bus
lifecycle
or
or
service,
or
what?
What
not.
B
Exactly
exactly
so
so
it
always
so
when
you
get
in
a
vet,
you're
always
going
to
get
the
immediate
parent
and
the
reason
for
that
is
nine
times
out
of
ten.
That's
what
you
care
about,
because
that's
usually
the
thing.
That's
calling
you
right
or
expecting
you
to
do
something,
but
you
know
we
don't.
We
didn't
want
to
limit
the
the
potential
use
cases.
So
if
you
wanted
to
go
out,
you
know
grandparent,
grandparent
or
you
know,
whatever
ancestor,
you
can
go
ahead
and
retrieve
and
whatnot.
C
Have
some
some
questions?
I,
don't
really
recognize
the
the
links,
the
object
from
iPhone
if
I
go
up
to
the
the
previous,
oh
right
right
there,
which
one
so
it
looks
yeah
this
one.
So
it
looks
there
that
you
have
a
link,
so
if
it's
contain
an
object
of
meta
and
data,
so
what
it
actually
looks
like
in
iPhone
is
that
you
have
metadata
and
links
on
the
same
level
and
there's
no
links.
No
external
links.
Objects
like
this,
so
so
links
is
something
on
the
same
level
as
data
and
and
meta.
B
C
C
B
C
C
B
C
B
B
B
Exactly
exactly
so,
I'm
thinking
is
potentially
because
the
Eiffel
link
could
still
be
the
same
like
at
the
DB
level
right
and
when
you
request
the
service,
when
you
you
know
it
could
just
adapt
this
and
change
this.
To
look
like
this.
Essentially,
you
know
with
whatever
metadata
and
and
what
have
you
so,
maybe
that's
a
potential
option.
B
I'll
have
to
think
about
that
some,
but
that's
definitely
an
interesting,
an
interesting
problem
here.
Yeah.
Let
me
let
me
think
about
that,
but
yeah,
because
that
kind
of
changes
things,
because
we
we
definitely
need
at
least
the
type
it
would
be
good
to
have
the
version
as
well,
just
to
know
actually,
maybe
not
the
version,
maybe
that
we
could
just
have
the
the
type
and
then
also
the
metadata
or
the
custom
data
is
also
really
important.
C
B
Yeah,
but
that's
what
I'm
saying
like
you
only
ever
have
the
immediate
parent
that
that's
making
it
so
like
the
so
you
wouldn't
have
any
number
of
ancestors.
It
would
only
be
the
immediate
pairing,
so
you'd
only
ever
see
see
this
so
so
that
that
might
be
fine,
but
yeah
because,
like
we,
we
definitely
don't
want
to
spend
all
ancestors
like
that
would
just
be
way
too
large.
But,
having
like
the
immediate
impairing
I
think
makes
the
most
sense.
C
C
B
C
C
B
Yeah
definitely
like
I
want
to
get
so
so
the
idea
is
to
kind
of
lay
the
foundation
and
then,
if
we
need
or
we'll
we'll
need
that
at
some
point,
we'll
need
some
way
of
ensuring
the
the
like,
knowing
where
something
came
from
right,
which
it
would
be
a
signature
but
I
feel
like
yeah.
That
would
be
like
the
next
step
was
like
kind
of
like
security
related,
so
but
yeah.
That
would
be
not
part
of
the
aspect,
but
definitely
a
future
spec.
C
D
D
C
D
The
CD
side,
we
never
talk
about
security,
so
the
more
that
we
can
make
that
a
priority
and
pull
that
information
in
the
better
off
will
be
to
get
the
eyes
of
the
open,
SS
app
and
the
CDF
needs
the
open
ssf
and
the
open
ssf
really
needs
the
expertise
coming
from
the
CDF.
So
that's
why
I
bring
this
kind
of
stuff
up?
D
B
B
C
We
have
had
people
from
from
who
who
wants
to
Wilson.
That
was
the
most
see
me
thing
that
copier
ago
I
don't
remember
his
name
now,
someone
who's,
also
opener
stuff,
I'm,
pretty
sure
yeah
anyway,
so
yeah,
we
have
had
some
discussions,
but
it
was
some
time
ago
now.
So
we
should
really
revive
those
suggestions
for
sure,
yeah,
I
think
so
too,
and.
C
C
It's
very
similar
to
City
events.
I
would
say
it's
a
predecessor
to
citizens
in
some
sense.
It's
it's
what
we
use
today
in
Ericsson,
which
is
solid.
It's
we
use
it
while
waiting
proceed.
Events
models
we
recycled
because
it
serves
our
needs
quite
well
cool,
but
there
are
benefits
perceived
events
that
we
want
to
leverage
on,
of
course.
So,
therefore,
we
are
highly
involved
to
make
sure
this.
C
D
C
C
Just
how
it
has
been
I
mean
it
just
has
happened
to
not
stand
up
anywhere
so
I
guess,
but
when
the
community
was
created
a
long
time
ago,
it
was
it's
really
considered.
If
we
should
be
part
of
some
higher
Foundation
and
since
then
we
haven't
really
made
the
effort
either
to
to
try
to
join,
but
yeah
well,
I
have
thought
of
it,
but
I'm
not
sure
if
it's
worth
it
now,
when
we
are
looking
for
Citizens
but
I.
D
C
A
C
B
If
it
makes
sense-
but
you
know
like
like
you
know
like
what
mute
was
just
saying-
you
know
like
you
know,
this
should
be
like
an
inspiration
and
actually,
after
checking
out
the
example
like
we
need
the
format
to
be
more
like
this,
as
opposed
to
just
a
link
of
ID.
So
we're
gonna
have
to
make
some
changes
to
get
what
we
need.
You
know
for
us
to
be
able
to
use
it
internally
at
Apple
to
look
something
more
similar
to
this.
B
So
if
there
is
overlap,
then
I
I
would
think
you
know
that.
That's
that's
a
good
idea,
but
yeah
like
like
Emil,
was
saying
like
I
I,
think
you
know,
if
they're
trying
to
solve
the
same
problem,
you
know
having
two
competing
unless
one
can
leverage
the
other
which
which
isn't
being
done
today,
I
don't
know
if
it
makes
too
much
sense,
but
but
yeah,
but
yeah
going
back
to
what
you
were
saying
a
meal.
B
C
C
B
D
B
D
D
C
B
Yeah
so,
and
and
like
I
said
Emil,
that's
why,
like
I,
wanted
to
have
these
internal
meetings
with
apple
just
to
make
sure
what
did
because
the
less
data,
the
better
right
yeah
for
good
reason?
But
but
you
know,
like
I,
said
I
can
I
can
pass
along.
Is
there
any
caveat
or
is
there
any
field
that
you
see
right
now
that
you
might
not
think
is
useful,
like
I'm,
like
maybe
Target,
isn't
really
useful.
D
B
C
B
B
Yeah
yeah,
so
my
thinking
was
most.
You
would
have
always
like
one
parent,
but
my
thinking
was.
You
could
potentially
have
a
service
that
groups
a
bunch
of
requests
together
to
send
it
down
like
as
a
single
event.
But
like
has
you
know
like
like,
for
instance,
let's
say
you
have
something
that
publishes
artifact
a
b
and
c,
and
that
a
b
and
c
gets
triggered
for
a
single
event
to
like
deploy
something
right.
C
So
that's
one
thing
and
I
mean
you
know
if
we
quite
often
have
multiple
links
in
our
events
as
well
to
different
types
of
targets,
so
one
could
be
the
parents
another
one
could
be
the
the
context
of
some
other
kind
it
could
be,
and
if
you
send
a
test
event,
you
can
have
the
target
pointing
at
a
artifact.
You
have
to
test
it.
Then
it's
not
the
parents
probably,
but
it's
it's
a
relation
to
another
event
that
was
sent
earlier,
an
artifact
event.
A
D
A
D
C
D
I
have
the
list
of
everybody
that
I
believe
should
be
in
that
in
that
voter.md
file,
which
gives
us
a
election
Authority
or
a
registered
voter.
What
I'm
thinking
of
doing,
though,
is
sending
out
an
email
to
everybody
and
telling
them
to
check
that
their
name's
on
the
list.
Let
them
know
that
the
election's
coming
up
and
if
they're
not
send
them
the
Forum
to
register.
C
C
C
C
D
C
B
C
B
C
B
C
C
The
next
thing
that
happens
is
that
the
pipeline
is
triggered
so
an
activity
trigger
event
deny
for
distance,
which
signals
that
now
a
new
pipeline
has
been
started
caused
by
this
Source
change
event.
So
there's
a
course
link.
So
this
is
the
link.
The
Targets
in
this
event
is
then
the
event
ID
of
this
one.
So
that's
the
Target
Field
in
the
link
right.
B
C
C
Which
then
links
to
the
triggered
events
saying
that
now
I
started
something
and
the
thing
I
started
was
this
activity
triggered
thing
that
was
secured
before
and
then
here's
another
event,
another
link
type
called
activity
execution.
So
this
is
not
really
caused
by
that
event
being
sent
it's
rather
caused
by
a
timer
or
a
queue,
or
something
like
that,
and
it's
just
a
reference
that
what
we
have
started
is
what
is
referenced
by
this
activity
execution
and
then
the
next
thing
that
happens
is
that
we
create
a
baseline.
C
So
this
is
a
composition
defined
event,
as
they
call
it
an
apple
which
signals
that
we
have
now
a
new
Baseline
created
based
on
this
new
source
change.
That
came
up
here
so
here
we
see
that
one
of
the
elements
in
this
baseline
or
the
element,
probably
in
this
based
on
the
I,
mean
the
one
of
the
parts
of
the
Baseline
itself-
is
actually
this
Source
change
this
new
source
change.
So
we
have
a
reference
to
the
Distortion
that
was
created
a
while
ago,
and
it
was
created.
I
mean
this.
C
This
composition
was
then
created
under
the
context
of
this
pipeline.
So
there
are
two
different
events:
it's
a
sorry,
two
different
links
there
with
different
types
because
they
mean
different
things.
One
of
the
links
mean
that
this
is
the
source
change
the
element
that
is
part
of
the
Baseline.
They
are
the
link
points
to
the
context
in
which
this
was
was
secreted,
so
those
are
two
different
links
in
the
same
event
and
then
we
create
an
artifact.
That
means
we
built
something
here.
C
We
create
the
artifact
and
we
reference
then
to
the
baseline
or
the
composition
that
was
used
when
building
this
artifact.
So
that's
one
event
link
there
and
then
we
have
the
finished
event
saying
that
now
this
activity
was
finished,
the
first
the
build
step
was
finished,
so
this
is
actually
not
the
full
pipeline.
It's
just
one
of
the
steps
in
the
pipeline
and
again
we
link
to
the
activity
trigger
event
to
say
what
what
was
finished.
C
So
we
don't
include
all
information
about
the
activity
itself
in
this
event,
but
we'd
rather
link
it
to
this
other
event.
So
here
we
are
heavily
dependent
on
on
a
database
collecting
all
these
events,
of
course,
so
we
can
afterwards
see
what
happened
in
what
order,
and
then
we
were
calling
water
as
well
yeah,
yeah
and
and.
C
This
case
test
with
finished
events,
and
then
we
have
something
called
confidence
level
event
which
is
more
or
less
a
maturity
level
saying
that
after
we
have
tested
this
now,
we
have
gained
a
new
confidence
of
this
artifacts.
So
the
subject
of
this
confidence
level
for
this
maturity,
the
subject
of
it
was
this
artifact
that
we
tested,
and
it
was
done
under
the
context
of
this
step
in
the
pipeline
and
going
on
similarly
yeah
whatever.
So
you
get
the
point
yeah
a
clear
example
of
multiple
links.
B
Give
me
all
the
links
for
test
events,
and
it
would
go
ahead
and
return
those
if
they
cared
about
them.
If
they
need
that
context,
but
nine
times
out
of
ten
a
CD
event
or
CD
service
is
only
going
to
care
about
the
delivery
of
an
artifact
and
then
do
something
off
that
artifact
from
a
CI
system.
So
that's
kind
of
like
what
I'm
thinking.
B
B
The
CI
system
would
necessarily
care
about
all
the
links
between
these
things,
mostly
because
was
when,
when
it's
ingesting
the
like
the
artifact,
for
example
the
artifact
or,
let's
say
the
test-
let's
say
it
finishes
a
test.
That's
still
within
the
system,
and
you
know
it
submits
that
submits
a
test.
Successful
the
parent
ID
is
still
going
to
be
itself
right,
so
I
don't
think
it
needs
much
more
information.
Like
it's
just
saying,
hey
this
came
from
us.
We
know
you
know
where
all
that
information
is
already
right.
B
C
B
C
I
mean-
and
we
have
multiple
purposes
for
it,
I
mean
one
is
for
driving
the
flow
itself.
So
as
you
call
it
a
cioc
lead
system
that
would
know
that
now
this
is
an
artifact
and
we
should
test
it
and
then
we
test
it
and
then
we
should
publish
it
and
set
some
confidence
on
it
or
whatever,
but
that's
just
the
CI
system
itself,
the
the
engine,
the
CI
engine
or
the
pipeline
engine,
but
we
have
a
lot
of
other
consumers
in
this
area
as
well.
C
B
B
Each
other-
yes,
yes,
okay,
I,
think
that's
where
the
disconnect
is
okay,
so
I
understand
now,
okay,
so
the
the
reason
so
we
didn't
get
into
the
link
service
because
it's
low,
it's,
we
didn't
get
that
to
the
section
of
that
of
that
proposal,
but
everything
you're
asking
for
is
part
of
the
link
service.
So
basically,
this
link
service
has
all
this
information.
It's
basically
the
Eiffel
links
in
the
database.
That's
basically
what
it
is
I
mean
we'll
probably
need
to
do
a
little
bit
of
changing,
but
so
yeah
I
think
I.
B
C
But
in
order
to
populate
the
link
service,
then
you
wouldn't
need
all
the
or
to
duplicate
all
this
data,
because
the
link
service
would
would
listen
to
all
events
right.
Yes,
so
you
wouldn't
need
to
duplicate
all
data
from
the
parent,
because
the
link
service
has
already
here
heard
about
the
parent
event
when
it
came
on
the
bus,
yeah.
B
B
The
the
only
reason
why
the
parent
is
there
is
because
a
lot
of
the
times
Services
that's
what
they
care
about.
That's
why
the
parent
is
in
in
the
actual
in
the
payload.
In
this
case,
and
rather
than
going
and
calling
because,
like
you
know,
when
you
get
an
event,
you're
gonna
be
like
hey
I
need
this
parent,
like
all
almost
all
the
time
right,
so
we're
just
gonna.
C
But
if
we,
for
example,
it
would
be
a
a
consumer,
then
that
listens
to
this
artifact
published
event.
In
the
end,
they're
saying
that
this
thought
that
was
published,
then
it
will
I
mean
the
parents.
To
this
I
mean
the
artifact
created
event
is
far
away
from
this.
It
was
a
long
time
ago.
It
was
created,
then
a
little
activities
that
happened
in
between
a
lot
of
things.
C
So
the
parents
to
this
artifact
published
event
is
probably
not
the
artifact
created
event,
but
rather
a
another
activity
or
a
test
case
or
something
a
test
case
execution
or
some
confidence
level
or
whatever.
Or
would
you
consider
that
when
sending
this
artifact
published
event,
then
you
would
always
set
the
parent
to
a
certain
type
of
event?
That
is
the
the
artifact
event
in
this.
B
Case
yeah,
my
thinking
is
like
you
would
group,
so
that's
that's.
How
I
was
thinking
about
I
didn't
outline
that
and
the
proposal,
but
I
probably
I,
definitely
should
it
would
always
brute
by
the
type
that
you're
a
part
of
like,
for
instance,
a
test
execution.
You
know
its
parent
would
always
be
a
source
code
change
or
or
a
build,
for
example,.
C
B
Yeah
build
exactly
so
yeah,
so
that
was
my
thinking,
because
I
I
think
it
it's
hard
to
make
sense
of.
You
know
like
like
what
you
were
saying,
like
an
artifact
published
being
a
test
event
like
what
can
you
do
with
that
right?
So
my
thinking
was
like
it
would
always
be
a
part
of
the
artifact
creation
or
build,
or
whatever.
B
B
C
Yeah,
so
the
consumer
of
like
published,
doesn't
need
to
to
to
find
out
the
ultra
creative
event
in
a
database,
but
it
could
just
get
it
by
default.
I
was
just
thinking
one
more
thing
that
about
the
the
context
here,
but
we
often
use
this
context
links
you
know
to
some
activity
related
events
which
says
you've
watched
pipeline
step.
It
was
done,
but
in
your
proposal
that
maybe
it
shouldn't
really
be
a
in
that
case.
It's
not
really
a
context
or
sorry,
a
parent
link.
C
B
So
I
I
just
want
to
make
sure
I'm
understanding
what
you
mean
by
a
local
ID
just
to
make
sure
like
because
I
heard,
like
everything
you
said,
but
I
I
I
just
want
to
make
sure
I'm
I'm
assuming
the
same
thing
so
you're
saying
like
let's
say
we
have
stage
a
Stage
B
stage,
C
right
stage,
a
would
be
the
local
ID.
Or
is
this
like
a
unique
ID
or.
C
Like
what
it's
sort
of
stage,
so
so,
when
okay,
okay,
when
a
bill
happens
in
stage
eight
for
example,
then
the
all
of
all
events
related
to
that
build.
Of
course,
it's
an
ultra
created
event,
but
there
could
be
other
events,
maybe
as
well.
They
should
all
include
that
that
ID
of
the
stage
itself
stage
eight
okay
and
then
maybe
some
tests
are
happening
in
Stage
B
on
that
artifact,
but
they
would
then
be
referencing
some
other
context.
C
I
mean
another
stage,
yeah
yeah
and
then
maybe
the
publishing
or
the
deployment
or
the
delivery
or
whatever
it
could
be.
A
third
in
stage
see
them
and
that's
yeah,
so
so
that
we
can
see
what
what
activities
or
what?
What
yeah,
what
artifacts
events
more
or
less?
What
we're
happening
in
different
steps
of
the
pipeline.
B
Yeah
yeah,
that
that
makes
sense,
okay,
cool
I
can
definitely
update
that
I
think
that's
definitely
a
good
call
out,
because
that
at
least
we'll
give
you
some
context
of
the
structure
of
the
pipeline
as
well.
So
that's
definitely
really
helpful.
Okay,
cool!
That's
a
really
good
call
out
so
I'll
definitely
update
that.
B
B
Okay,
cool
cool
so
go
ahead
and
do
that
and
then
I'll
also
add
some
other
like
images
just
so
you
know
people
that
are
not
familiar
or
you
know
you
know
to
get
a
better
understanding
of
like
the
flow
of
things
you
know
like.
Like
you
said
you
know,
once
I
saw
this
picture
I
think
we
immediately
both
understood
like
what
we
were
talking
about
so
yeah
picture.
B
C
A
C
So
we
didn't
talk
about
the
roadmap,
but
I
mean
that's
also
just
links
anyway.
So
okay,
Google
for
the
agenda,
if
we
started
I,
didn't
know
55
minutes
into
the
meeting,
so
the
action
items
were
empty.
There
were
no
action
items
and
trace
the
order
to
mentioned
this
about
the
COC
project,
representation
Representatives,
so
just
keep
it
in
in
the
minutes.
Even
though
Tracy
talked
about
it
there
not
too
much
to
mention
that,
and
then
we
have
the
zero
series
which
was
released.
A
C
B
Support
yeah,
yeah
and,
like
I,
said
I
think
once
the
draft
is
out
and
like
I
said
once
I
have
this
last
internal
meeting
with
with
the
two
major
teams
here
at
Apple
that
are
interested
in
this
and
they're
quite
large
teams.
If
we
can
get
them
on
board,
it's
it'll
be
a
huge
win
for
CD
events
in
in
general,
so
that's
kind
of
the
plan
and
yeah
so
I
think
I.
Think
this
I
think
we're
moving
along
great.
B
C
Then
we
just
have
the
link
straight
for
the
Java
SDK
in
golang
and
Python
and
Jenkins
plugin
I.
Don't
think
you
have
any
information
on
those.
No
I,
don't
probably
probably
skip
all
that
I.
Don't
have
any
other
replacement,
what
else
either
so?
Okay,
you
can
skip
that
from
the
agenda.
So
that's
what
was
in
the
agenda
really
so
I
wanted
to
discuss
this
as
a
main
focus,
and
now
we
did
so
that's
perfect.
All.