►
From YouTube: CDF SIG Interoperability Meeting 2020-02-06
Description
CDF SIG Interoperability Meeting - 02062020
A
B
B
C
D
A
A
A
A
A
A
C
B
A
A
A
So
I
suppose
can
start
slowly,
because
the
first
few
points
are
basically
what
we
discussed
last
week
and
then
the
main
topic
I
want
to
bring
up
is
to
work.
We
started
doing
with
the
common
vocabulary
and
time
energy
followed
by
the
presentation
from
a
mill
because
to
Eiffel,
so
welcome
a
run
again
and
it's
great
to
see
all
of
you
here
as
usual.
You
know
when
you
have
meeting
someone
when
you
have
action
points
they
are
generally
left
to
the
later
parts
of
the
meeting,
but
this
time
I
won't
have
action
items
through
it.
A
First,
so
we
don't
forget
about
action
items
and
we
call
we
follow
those.
Let's
look
at
action
items
from
last
week.
So
the
first
action
item
is
basically
you
know
we.
We
are
using
mail
lists
and
slack
for
communication,
and
that
was
the
ask
from
everyone
to
join
the
mail
list
and
select
channel,
because
we
are
sending
all
the
updates
and
notifications
and
meeting
agenda
a
meeting
means
to
mail
lists
and
currently
I
think
there
are
20
people
signed
up
to
the
list.
A
Basically
just
sending
the
information
about
what's
happening
with
the
governor's
topic
and
starting
to
co-chair
nominations,
which
I
did
I,
think
it's
Monday,
which
I
will
touch
in
the
next
point
in
the
agenda
and
then
based
on
the
agreement
we
had
last
week.
All
the
current
members
listed
in
the
readme
file
are
added
to
seek
interval
with
the
github
repo
as
maintainer.
A
What
this
means
is
that
those
people
will
get
notifications
alternative,
ending
when
a
new
pull
request
is
open
for
develop
or
they
will
have
approval
permissions
and
so
on.
So
it's
basically
cutting
out
with
the
review
process
and
submitting
incoming
pull
requests
that
is
done
as
well
and
then
Tracy
helped
us
to
reach
out
to
eBay.
A
A
Basically,
last
week
what
we
discussed
was
the
question
was
like
CDF
contains
the
foundation
doesn't
have
a
clear
guidance
when
it
comes
to
have
special
interest
groups.
Our
government,
obviously
disk
use
us
out
of
freedom,
but
at
the
same
time
it
makes
it
difficult
for
anyone
who
is
joining
to
continue
the
foundation
are
working
in
groups
like
special
interest
groups
or
working
groups.
It
might
be
difficult
for
those
people
to
understand
how
these
groups
are
run
because
they
are
kind
of
different
from
projects
and
that's
the
point.
A
A
Three
co-chairs
and
one
of
the
reasons
of
having
multiple
cultures
is
to
enable
the
representation
of
different
views
and
bring
different
perspectives,
how
the
seed
is
run
and
what
the
cig
is
working
on
it
and
based
on
those
conversations
Monday
with
this
mail
I'm
showing
on
the
screen.
Right
now,
we
started
the
nominations
for
co-chair
and
the
idea
with
this
is
basically
finding
two
more
individuals
to
help
out
with
training
the
sick
and
one
of
the
people
could
be
representing
projects
and
other
people
could
be
representing
users.
A
So
when
and
if
other
people
step
up
and
nominate
themselves,
we
need
to
go
to
an
election,
but
if
there
is
no
other
person
nominating
for
the
co-chair
position,
I
think
we
will
have
ourselves
three
co-chairs
in
that
by
middle
of
next
week.
So
any
comments,
questions
about
the
government's
or
co-chair
topics,
yeah.
C
I,
just
posted
in
the
chat
that
the
intent
for
not
having
strict
strict
charter
manifest
to
start
its
instantiated
through
this
process.
So
if
you
look
at
the
example,
I
put
in
the
chat
from
C
NC
out,
that's
a
think.
I
put
the
one
for
security,
but
it's
very
similar
reads
very
similar
to
what
a
cig
is.
What
our
motivation
is
for,
making
one
What's
in
scope
what's
out
of
scope
and
the
Charter
and
the
Charter
cannot
violate
the
TOC
Charter.
C
Formations,
so
if
you
take
a
look,
we
yes
so
take
a
look
at
that
list
of
SIG's
that
we
have
a
similar
process,
almost
one
for
one
but
women,
you
form
a
say
you,
you
don't
necessarily
have
to
have
a
charter,
but
we've
already
defined
our
mission
and
in
gold.
The
only
thing
that's
missing
in
ours
is
a
direct
line
of
sight
of
forming
a
governance,
and
we
have
the
numbers
who
are
going
to
be
the
stewards
of
the
sig,
but
you
can
reference
hey.
This
is
defined
in
the
charter
of
the
TOC.
C
A
C
A
Actually,
thanks
for
passing
the
security
sector
from
CN
CF,
but
actually
I
referred
to
CN
CF
toxic
charter
because,
like
again
CN
CF,
six
save
their
own
charters,
but
the
top
level
talk
has
a
chart
of
where
all
the
six
can
refer
to
and
add
some
other
points.
That
is
not
in
conflict
with
the
top
charter.
That
was
the
missing
thing.
I
noticed
when
I
was
looking.
Cdf
doesn't
have
anything
like
this,
and
that
was
the
question.
Should
we
have
one?
If
not,
can
we
come
up
with
something
by
referring
to
something
else?
Yeah.
C
A
I
think
Tyra
Hernandez
two
connection
points
from
during
last
week's
talks,
talk
meet
again
just
to
clarify
like
you're,
not
after
something
very
heavy,
but
it's
just
important.
You
know
to
tell
the
people
who
are
not
you
know
into
how
the
six
are
run
and
they
know
how
these
things
are
run,
so
they
they
know
how
they
can
contribute
or
take
how
they
can
join
and
like
code
of
conduct,
that
type
of
like
very
basic
stuff.
It's
it's
not.
It
doesn't
have
to
behave
urination
behavior
either.
A
E
Sure
before
I
say
anything
about
that,
I
did
have
a
question
about
we're.
Just
talking
about
I
think
there
was
a
brief
mention
of
like
the
goals
and
the
mission
of
the
sig
and
I
was
wondering
if
we,
since
I
wasn't
at
the
last
meeting.
If
that
is
something
that
we
have
established
already
or
something
that
we
would
be
establishing.
My
guess
is
that
it's
something
that
we
would
be
establishing
going
forward
after
we
have
co-chairs
or
what
is
the
plan
for
that
I
think.
A
That
was
one
of
the
discussions.
Last
week
we
didn't
go
into
too
much
details.
Why
the
please
pick
up
odd
Iran
I,
don't
want
to
speak
on
here
and
one
of
the
first
questions
we
start
talking
about
was
like
I
think
it
would
be
good
to
describe
what
interval
with
the
means
in
CIC
the
context,
because
if
you
talk
different
people,
you
hear
different
ideas.
From
their
point
of
view,
some
people
say
pipeline
standardization,
the
other
people
say
like
this
event,
even
approach,
the
CI
CV
and
so
on.
A
F
Hi,
this
is
Tracy,
I
was
gonna,
add
like
I,
really
like
in
the
ML
Ops
working
group,
but
they've
got
kind
of
an
initial
roadmap,
and
then
the
plan
is
to
unity,
to
refine
that
maybe
even
take
the
first
full
year
to
sort
of
say
what
are
the
different
areas.
How
are
we
going
to
tackle
them
and
what?
What
are
the
kind
of
you
know
best
guesstimate
kind
of
timescales,
so
I'd
love
for
the
interoperability
when
to
just
if
I
decide,
so
it
divided
up
the
the
different
topics
and
kind
of
map
them
out.
F
E
E
But
yeah
I
guess
just
to
say
something
about
the
co-chair
nominations
and
elections.
Thank
You
Tracy
for
mentioning
me
last
time
in
the
meeting
that
I
wasn't
able
to
attend
I'm,
pretty
passionate
about
interoperability.
If
you
are
familiar
at
all
with
the
Tecton
project,
one
of
our
goals
is
to
try
to
help
with
reducing
fragmentation
in
the
CI
CD
space,
so
this
is
like
airy.
E
A
Christy
and
thanks
for
accepting
thanks,
trace
for
nominating
Christy,
because
it
is
very
important
area.
Obviously,
and
we
need
your
experiences
since
you
already
have
I
think
from
I
think
doing.
Last
week's
Faust
and
Tracy
you
mentioned
Tecton
is
working
on.
Tecton
already
is
some
kind
of
specification
for
pipeline
I.
Don't
remember
exactly
what
it
is,
so
it's
really
valuable
to
bring
those
things
here,
so
people
can
look
at
them
and
continue
working
on
those
things
collaboratively.
A
So
I
think
that's
enough
for
governance
and
we
will
continue
like
how
we
start
the
time
see
what
happens
on
top
level
and
then
we
will
adapt
going
forward
and
by
next
week
hopefully
we'll
have
the
co-chair
it's
filled.
So
the
next
topic
is
consciously
summit
Europe
and
that
is
happening
as
a
zero
event
to
coin
Europe
and
call
for
proposals
closes
tomorrow.
So
if
any
one
of
you
are
interested
to,
you
know
submit
a
talk
proposal,
you
have
one
day
left
and
then
I
think
Christi.
E
E
It
wasn't
available
through
Kuk
on
registration
for
a
while,
but
it
is
now
so
that's
another
thing
to
highlight:
I
guess,
even
if
you're
not
interested
in
proposing
a
talk,
if
you
just
want
to
attend
it,
please
register
and
yeah
about
it.
Well,
we
have
a
preference
for
lightning
talks
also.
So
if
you
feel
like
you'd,
be
interested
in
talking
about
something,
but
not
sure
if
you
want
to
do
an
entire
talk,
that's
actually
perfect,
because
we
really
like
lightning
talks
and
we're
going
to
try
to
have
lots
of
slots
available
for
those.
A
Yep,
please
submit
people,
and
then
we
get
your
ideas
present
there
and
you
can
meet
with
everyone
who
is
interesting.
This
area
there
on
site,
Monday,
March
30,
it's
Amsterdam,
so
hope
to
see
most
of
you
all
of
you
there,
hopefully
so
that's
C
D
summit
and
the
next
topic.
Perhaps
this
is
one
of
the
topics
brought
up
by
Jeremy
last
week
during
the
first
submitting
is
perhaps
even
before
we
start
talk
about
what
we
are
going
to
and
how
we
are
going
to
address
the
challenges
we
all
face.
A
It
might
make
sense
to
start
working
on
a
common
vocabulary,
time
energy,
because
what
some
say
when
it
comes
to
pipelining
might
not
mean
the
same
thing
for
the
others,
and
that
word
actually
started
last
week
and
there
is
a
pull
request
on
github
in
interpret
repository.
Basically,
what
is
there
right?
Now
is
the
term
terms
used
by
different
tools
and
listed
turf
and
basically
creating
them
simple
mapping
between
those
tools.
A
If
you
look
at,
if
I
can
show
the
file
yeah,
if
you
look
at
the
file,
you
will
see
some
of
the
CIC
tools
and
technologies
that
I
am
sure
we
meet.
We
miss
many
and
I
think
immediate
mentioned.
Our
goal
is
not
there.
So
please
review
the
pull,
request
comments
and
you
can
even
amend
the
pull
request
and
add
your
contribution
there
directly.
A
So
all
of
these
tools,
if
you
look
at
Tecton,
for
example,
under
Tecton
different
terms
used
by
Tecton,
is
listed
there
and
Simone,
which
is
all,
and
we
also
have
gave
it
github
and
it
lab
listed
there
and
at
the
end
it's
a
simple
mapping,
and
this
probably
is
not
entirely
correct
because
I
personally
am
not
very,
you
know
into
all
these
different
tools
and
technologies.
So
please
look
at
this
share
your
thoughts
and
then,
if
we
can
finish
the
work
with
this
vocabulary,
even
this
is
to
see
icd
ecosystem.
F
Yeah
I
think
this
is
great,
especially
this
mapping
I
haven't
had
a
chance
to
kind
of
dive
into
it
deeply,
but
I
certainly
plan
to
in
a
I'll,
be
happy
to
take
it
to
to
various
folks
and
just
get
their
perspective
and
I'm.
Sure
there'll
be
plenty
of
objections
to
putting
things
in
boxes
and
making
one-to-one
comparisons,
but
I
think
it's
really
good
to
have
these
conversations
and
just
build
some
awareness
that
you
know
a
job
in
one
thing
isn't
automatically
a
job
in
another
thing,
so
yeah
this
is
pretty
important.
So.
A
That
was
the
last
point
in
the
agenda
and
yeah
again.
Please
look
at
this
and
this
perhaps
the
very
first
thing
to
start
doing
and
if,
as
Christy
mentioned,
if
we
can
start
working
on
some
kind
of
cause
and
take
an
example
from
ml
ops
and
employ
a
similar
approach
for
interpreter
as
well,
that
would
be
great
and
if
you
are
up
to
it,
just
send
a
flu
quest
and
we
start
working
together.
It
doesn't
have
to
be
an
action
item.
C
A
Okay,
then
I
take
this
as
no
other
topic
for
the
moment
and
yeah.
This
is
not
the
only
way
to
bring
up
new
topics
obviously
have
made
lists
as
well.
Just
share
your
thoughts
on
mail
lists
and
perhaps
direct
go
to
the
agenda
and
add
new
topics
for
upcoming
meetings.
If
you
want
to
have
certain
topic
discussed
during
those
meetings,
just
feel
free
to
do
that.
Do
that
and
then
we
move
to
ml?
D
So
first
some
background
questions
that
I
would
like
to
look
into
in
this
presentation.
So
one
question
you
might
have
when
talking
about
zICA
pipelines
is
how
can
we
communicate
about
new
artifacts
becoming
available
within
a
pipeline
to
the
ones
who
are
interested
in
seeing
in
those
contracts?
And
how
can
we
reach
out
to
others
to
trigger
their
pipelines
or
at
least
inform
them
that
there
is
something
new
and
allows
that
others
that
might
have
different
platform
or
tools
to
render
sea
acidic.
D
And
also,
how
can
we
visualize
are
connected
pipelines,
then
pipelines
that
could
run
again
on
different
different
tools
or
different
technology
stacks
underneath
and
furthermore,
how
can
also
trace
our
delivered
products
all
the
way
back
to
the
source
code,
changes
that
were
made
in
the
beginning
to
before
they
were
built
and
also
across
different
pipeline
tools.
So
this
is
about
having
different
pipeline
tools
in
your
network
of
pipelines,
and
how
can
you
make
sure
that
they
can
communicate
and
that
the
information
sent
is
understood
by
an
external
Isner?
D
Also,
there
is
actually
a
book
on
this.
The
concept
of
the
ideas
behind
er-
if
it
has
been
discussed
a
lot-
or
at
least
it,
has
been
discussed
in
academia-
there
are
links
in
in
the
last
slide
of
this
presentation.
I
won't
read
them
out,
but
you
can
have
them.
You
need
the
presentation
deck
afterwards
and
there's
also
one
printed
book.
Actually
that
handles
these
matters.
Alright
I
would
invite
you
to
actually
look
into.
D
So
going
directly
to
I
feel
them
the
main
one
of
the
main
principles
are
actually
the
D
main
principle.
I
believe
that
I
Felice
is
concerned
about
is
that
you
need
to
it's
tough
to
you
what
you
want
to
communicate
from
your
pipeline,
but
when
you
do
communicate
something
you
need
to
follow
a
certain
pattern
or
protocol
so
that
the
listeners
can
understand
you.
D
Then
again,
it
could
be
very
well
to
have
dialects
of
your
language.
We
know
all
of
us
that
I
mean
in
this
call.
We
all
speak
English,
but
we
have
different
dialects.
Of
course
we
can
stay
down
the
standing
shot
and
that's
fine
as
long
as
you
speak,
the
same
language
as
long
as
they
don't
diverge
too
much.
D
So
what
you
communicate
is
up
to
you,
but
how
you
do
it
is
not
its
main
principle
of
Ifill
I
feel
is
the
protocol
with
events
and
the
events
are,
are
structured
in
S,
JSON
objects,
and
what
you
see
now
on
the
screen
is
the
main
format
of
this
dissidents.
So
there
are
three
sections:
the
Metro
section,
the
data
section
on
the
links
section,
I'll
come
back
to
the
data
and
links
section
later,
but
the
Metro
section
is
then
of
course
met
the
information
and
there
we
have
an
ID
of
each
event
sent.
D
D
There
are
also
different
event:
families
defined
in
eiffel
home
do
come
in
different
areas
of
your
pipeline,
so
there
one
is
one
family
handling,
the
artifacts
that
are
created
or
tested
or
created
or
composed,
and
then
there
are
test
related,
artifacts,
illustrative
events,
and
there
are
also
source
code
related
events,
and
we
also
have
activity
related
events
and
I
must
say
now
that
activity
is
may
be
a
new
term.
Here.
D
We've
talked
about
in
this
terminology
discussion
just
earlier
that
there
are
I
mean
well,
the
pipeline
is
one
thing,
and
then
we
have
the
stages
or
steps
or
jobs
or
whatever
we
call
them,
but
I
fell
all
those
different
things
are
actually
activities,
so
even
a
whole
pipe.
Don't
could
be
one
activity
or
a
stage
or
a
step
or
a
job
or
whatever
you
call
it
all.
Those
are
activities
to
trifle
and
they
can,
they
can
be.
D
There
is,
could
be
a
hierarchy
of
activities
so,
for
example,
within
one
pipeline
activity
you
can
add
a
lot
of
step
activities
or
stage
activities
or
whatever
you
call
them
so
pipeline
does
not
sorry.
I
fell
does
not
say
anything
about
the
concept
of
a
pipeline
or
stage
or
step
or
job
actually,
but
instead
all
those
things
are
called
activities
within
actual.
That
is
how
its
structured
right
now,
at
least
so.
If
we
look
into
this
event
stone,
we
dig
quite
deep
technically
directly.
D
This
is
the
first
event.
I'll
show
you
here,
it's
called
artifact
created
event.
I
will
refer
to
this
events
later
on
with
the
abbreviations
in
the
presentation,
so
I
will
spell
them
out,
probably,
but
you
I
will
not
show
the
interpretation
of
them
in
the
slides
everywhere,
because
that
wouldn't
fit.
So
this
is
no
trick
created
event
and
the
one
of
the
important
parts
of
this
event
is
done
within
the
data
section,
where
you
can
specify
an
identity
for
your
artifact
that
has
been
grated
or
built.
I
mean
the
Eifel
standard.
D
D
D
Yes,
then,
after
you,
a
bill
cannot
effect,
you
might
want
to
publish
it
somewhere.
You
see
this
artifacts
created
event,
at
least
in
the
picture
I
show.
Now
it
does
not
create
any
does
not
have
any
information
about
where
it
is
stored
or
anything.
So
sorry,
I'll
come
back
to
that.
First,
let
me
hate
to
talk
about
the
conference.
Leavitt
modified
event,
so
there
is
an
event
saying
that
a
artifact
has
reached
a
certain
confidence
level,
and
that
means
that
it
has
been
tested
in
some
sense.
D
You
can
now
tell
the
world
that
this
artifact
has
reached
some
certain
maturity,
level
or
confidence
level,
as
we
call
it
here
and
within
this
conference
level
modified
event.
There
is
a
data
body
again,
then
rate
an
object,
object
which
contains
a
name
free
text,
string
name
and
then
the
value
of
the
conference
level.
D
So
when
we
send
this
conference
and
modified
event,
we
don't
repeat
the
ID
of
the
artifact
that
we
have
created
or
tested.
Instead,
we
reference
the
event
that
contains
that
data,
and
we
also
have
link
types
on
each
of
these
links.
So
in
this
case
there
is
a
subject
link
saying
that
the
subject
for
this
conference
level
that
has
been
reached
is
then
the
artifact
pointed
out
by
this
first
author
I
created
event.
D
So
that's
how
events
are
linked
together
and
how
information
can
be
collected
by
listening
to
multiple
events
and
aggregating
information
from
them
and
then
to
the
published
event
that
I
was
about
to
talk
about
earlier.
So
now,
when
we
have
reaches
after
conference
level,
it
could
be
wise
to
also
publish
this
event
so
that
others
can
see
it,
and
then
we
create
a
artifact
published
event.
D
We
link
to
the
object,
create
event
again
with
now
with
an
artifact
link
in
this
case,
and
within
this
event,
you
can
see
that
there
is
a
data
object
containing
the
locations
sub
object,
and
here
you
can
specify
to
where
you
have
uploaded
this
specific
artifact,
so
that
listeners
can
download
it
and
test
it
or
include
it
in
their
bills.
Whatever.
D
D
Great,
so
let
me
go
on
down
to
the
next
family.
Let
me
look
into
some
of
the
test
related
events.
There
are
a
lot
more
events
than
I
will
show
here,
but
just
for
you
to
get
some
fun
feeling
of
what
it
is
so
where,
for
example,
something
that
we
call
a
test
suite
started
event
which
imports
the
listener
that
now
we
have
started
to
execute
a
certain
test.
Suite
this
event
doesn't
contain
very
much
it's
more
as
the
name
of
the
test
suite
that
has
been
started
and
later
on,
the
chemical
test.
D
Suite
finished
event
when
you
have
finished
testing
your
thing.
The
tests
we
finished
event
will
also
include
a
outcome
object
stating
if
it
was
successful
or
not
executing
this
test
suite
and
also
a
link
to
a
URL
link
to
the
persistent
logs
from
this
test
suite
execution.
So
you
can
look
into
more
details
of
the
outcome
if
you're
interested
and
again
they
are
linked
together.
So
the
test
suite
finished
around
links
to
the
first
restart
advanced
wireless
test,
suite
execution,
pipe
link.
D
B
D
D
So
for
the
source
code
related
events,
there
is
first,
a
source
change
created
event
which
states
that
now
you
I
have
created
a
new
source
change.
For
example,
you
have
pushed
something
to
Gary
it
or
you
are
created
a
pull
request
in
github
or
get
logged.
The
merge
request
and
this
event
then
contains
something
that
we
call
it
change.
That
is,
the
source
change
and
a
description
of
what
that
is
so
more
datas.
Of
course,
of
this
needs
to
be
read
in
the
protocol
spec.
D
This
is
an
example
where
we
have
a
gift
identifier.
It
could
be
some
other
source
control
system,
it
could
be
mercurial
or
clear
case
or
SVM.
Actually,
we
have
support
for
as
well
in
the
protocol.
So
here
you
state
a
commit
ID,
for
example,
of
your
source
change
and
also
reference
to
the
actual
change.
If
it
could
be
in
Garrett,
it
could
be
a
change
ID
reference
if
it
could
be
github,
which
would
be
a
pull
request.
D
Then
you
need
to
specify
a
new
gift
identifier,
because
that
that
merge
commit
ID
will
not
be
available
as
a
solar
and
create
the
event.
So
there
you
will
need
to
repeat
actually
delete,
identify
your
field,
but
with
a
new
commit
body
in
it,
but
again
linking
them
together
makes
it
possible
to
track
how,
for
example,
the
duration
between
those
these
two
actions
in
the
pipeline
and
follow.
D
D
If
you
wish,
and
a
baseline
emeral
composition
then
contains
one
or
multiple
links
to
different
source
changes,
so
if
you,
for
example,
have
commits
in
three
different
repositories-
and
you
want
to
state
that
now,
I
have
built
the
baseline
of
these
three
different
commits
from
different
repositories.
You
can
then
send
the
composition
to
find
I'm
saying
that
I
have
these
three
different
elements
in
my
composition
and
although
saw
them
notified
by
element,
type
links
from
this
composition
defined
event.
D
This
actually
has
a
name
on
it
as
well
name
property
in
the
data
field,
data
objects,
but
the
most
important
dimension
here
is
then
that
we
link
to
instead
of
again
stating
the
source
change
commit
ID
or
whatever.
We
instead
link
to
the
previously
sent
event
for
the
swirl
change,
submitted,
yeah
yeah,
and
it
could
be
multiple
yeah
in.
If
so,
there
can
be
multiple
elements
here
as
well,
pointing
to
other
search
engines
yeah,
and
then
they
about
this
activity
related
events
which
could
then
reference
pipelines
or
stages
or
steps
or
jobs
in
your
pipeline.
D
There
are
three
different
activity
related
events.
Mainly
first
is
the
activity
trigger
event
which
will
assess
that
now,
I've
put
this
activity
in
the
queue
to
be
executed.
If
you'll
be
related
to
normal
Jenkins
execution,
it
would
be
that
the
job
has
been
put
in
the
Jenkins
job
queue
or
the
build
queue,
and
then
this
artifact
triggered
event.
So
sorry
activity
trigger
event
it
could
be
sent.
It
will
just
contain
a
name
of
the
activity
and
not
much
more.
Of
course,
in
the
case
of
Jenkins,
it
could
be
a
job
name
as
well
within
it.
D
So
you
can
follow
the
progress
of
this
activity
execution
and
once
it's
done,
you
can
send
an
activity
finished
event
again
pointing
to
the
same
activity
through
activity
triggered
event.
And
here
you
can
state
the
outcome
of
the
activity
and
any
persistent
logs
that
you
want
to
to
notify
the
listener
about.
D
And
that's
the
about
activity
related
events
and
then,
if
we
now
try
to
combine
these
events
a
bit
in
this
picture
in
the
lower
section,
you
see
a
fictive
pipeline.
First,
you
merge
some
code
and
then
you
build
it
and
you
test
it
and
you
deliver
it.
Sorry,
we're
simple
and
straightforward
the
pipeline
time
flows
from
left
to
right,
as
in
the
other
pictures,
I
call
it
upstream
if
I
go
to
the
left
and
downstream.
D
That
could
then
trigger
an
activity
to
be
started.
This
build
activity
in
this
case,
so
if
you
in
your
pipeline
either,
if
you're
actively
hauling
your
source
control
system
or
if
you
are
being
called
by
a
web
book
regardless
how
you
have
started
your
pipeline,
you
could
send
this
activity
trigger
event
and
say
you
know
now:
I
have
got
this
activity
in
my
queue.
It
was
caused
by
this
Sora
change
submitted
event.
So
that's
why
we
have
a
course
link
in
this
case
and
then
suddenly
the
activity
actually
starts.
It's
a
built.
D
D
D
That
is
within
the
build
activity
in
this
case,
and
then
after
that,
I
probably
build
the
artifact
and
I
stand
anatra
created
event
pointing
out
the
composition,
with
the
composition,
element,
type,
sorry
link
type,
and
when
that
is
done,
I
can
send
activity
finished
event
again
pointed
entered
activity
triggered,
stating
that
now
I've
done
this
build
activity.
You
know,
then,
it's
up
to
the
next
step
in
the
pipeline
to
continue,
and
in
this
case
the
test
stage
was
triggered
by
the
finishing
of
the
build
activity.
So
therefore
the
course
link
goes
that
way.
D
I
send
in
a
confidence
level
modified
event
when
I
finished
all
my
tests
and
the
conference
level
more
relevant,
again
points
back
to
the
activity
or
fact
created
event
to
state
that
this
is
a
specific
artifact
that
I've
tested
and
it
has
now
reached
a
new
certain
conference
level
and
when
that
is
done,
I
can
finish
my
activities
under
the
activity
finished
event,
meaning
that
now
the
test
activity
is
done,
and
then
we
can
see
another
way
of
triggering
the
next
step.
In
this
case,
I
intentionally
did
not
trigger
the
delivery
step
from
the
activity.
D
To
finish
the
event
I've
studied
in
the
previous
step,
but
instead
of
triggering
it
from
the
conference
level
modified
event,
which
means
that
some
listener
to
this
test
or
to
the
conference
now
modified
event
could
trigger
some
other
activity.
That
is
not
really
connected
to
the
original
pipeline,
but
instead
just
triggered
because
some
has
some
artifacts
which
the
new
conference
level.
D
D
No
questions
so
another
example
done
or
combined.
Events
could
look
like
this
here.
I
don't
have
any
activity
events,
because
it
will
be
a
very
messy
picture,
but
in
the
middle
here
you
see
a
composition
to
find
event.
It
is
this
baseline
event,
saying
that
I
have
now
I
intend
to
include
a
lot
of
things
in
my
new
baseline
or
mean
value.
D
So
in
my
new
artifact
and
to
the
left
of
this
baseline,
you
see
three
different
chains
of
events
or
three
different
sub
pipelines
or,
if
you
wish,
so
this
states
actually
that
there
are
three
different
artifacts
coming
into
this
composition.
So
in
this
case
we
don't
build
from
source
code,
but
instead
we
create
the
baseline
out
of
binaries
of
artifacts
created
previously.
D
So
it's
more
like
an
integration.
If
you
wish
of
the
already
built
binaries
and
that
integration
could
then
result
in
a
new
binary
or
some
kind
of
artifact
doesn't
need
to
be
a
binary,
it
could
be
yesterd,
yeah
be
thoughtful
or
whatever
this
artifact
that
your
traits,
but
some
kind
of
integration
of
the
previously
built
wineries
I
mean
this
example.
Then
I
show
that
we
have
three
parallel
first
activities
running
actually
here:
I,
don't
have
just
sweet,
but
instead
test
case
triggered.
So
there
are
other
tests
related
events.
D
D
This
tests
on
my
artifact
and
then
I
publish
it,
and
it
could
also
don't
be
that
the
other
part
coming
into
this
composition
comes
from
K
beneath
this.
It's
good,
for
example,
I
guess
be
the
CRD
library,
from
goodness
it
is
that
I
believe
Tecton
is
dependent
on.
So
when
there
is
a
new
delivery
from
Cuban
artists,
the
kinetic
community
on
the
CID
library
or
whatever.
D
Then
I
have
no
idea
if
this
is
correct
property-
most-
probably
not
not
just
to
exemplify
that
these
could
then
run
on
different
technology,
stacks
different
tool
chains,
so
I
believe
that
Tecton
itself
uses
Tecton
city
to
deliver
itself
and
I.
Don't
know,
maybe
giving
a
person
uses
circa
CI
to
deliver
to
build
its
Travis
pipeline,
and
maybe
OpenSSL
use
this
travesty,
for
example
regardless.
D
If
all
of
these
would
have
support
for
the
same
event
protocol,
they
could
communicate
in
this
way
and
they
don't
need
to
stay
on
hold
on
the
same
tool
chain
to
be
able
to
communicate.
That's
the
message
and
this
graph
of
events
done
it's
it's.
The
director
exactly
grow,
so
it's
it's
not
circular
and
it's
it
termina.
Stick!
If
you,
for
example,
would
look
at
this
composition
to
find
event
you
could
perform
in
an
upstream
query
on
that
event,
and
then
you
could
get
all
the
artifacts
that
are
are
built
in
in
the
base
time.
D
So,
with
a
simple
upstream
query,
it
will
have
a
deterministic
result
stating
all
the
artifacts
in
your
composition
and
the
same
way
to
do
a
downstream
query
from
this
composition.
To
find
event,
we
were
going
to
define
all
test
results
for
this.
This
composition,
this
the
artifact
that
you
are
great
actually.
E
D
Question
so
yes,
we
use
it,
I
mean
if
your
protocol
itself
doesn't
state
any
directions
on
how
events
should
be
stored
or
even
if
they
should
be
stored.
But
obviously,
if
you
want
to
query
this
historically
afterwards,
you
need
to
store
them
somewhere
mm-hmm,
and
then
you
could
have
an
a
database
where
you
just
listen
to
this
message,
post
or
whatever,
where
you
send
the
events,
you
can
have
a
database
that
stores
them
and
of
course,
then
you
need
would
need
to
to
federate
the
messages
between
these
different
communities
pipelines.
D
You
need
to
set
up
a
federation,
of
course
between
those
message
classes
and
if
you
wish,
you
can
store
the
cubanÃa
dissidents
yourselves
in
your
own
database
or
maybe
keeping
it
assess
its
own
database
event
database,
where
you
can
query
from
so
that's
up
to
the
users
of
this
protocol
and
obviously,
as
we
use
this
quite
extensively
with
generics
and
so
far,
we
have
a
lot
of
ecosystem
tools
as
we
prefer
to
call
them
surrounding
a
shell.
So
we
have
we.
E
D
D
B
D
D
See
we
don't
have
too
many
minutes
left
so
I
might
rush
the
last
part.
This
I've
already
talked
about
the
use
cases
where
it
can
be
used.
Well,
I
will
go
into
this
actually
yeah.
So
if
you
would
mention
briefly
that
we
have
something
that
we
some
visualization
dissidents
internally
and
that's
something
that
we
we
can't
call
follow
my
commit
where
you
can
actually
have
your
pipeline.
D
As
you
see
it
in
the
top
here
and
with
the
event
sent
in
this
case,
I
send
us
for
change,
created
some
activity,
events
and
testsuite
events
and
other
activity
runs.
I
can
see
that
currently,
when
this
snapshot
is
taken,
there
has
been
an
activity
started
and
sent
for
my
build
activity,
which
means
that
I
can
visualize.
Now
that
the
build
activity
is
ongoing.
With
this
blue
color,
the
unit
tests
is
already
finished
and
it
was
successful.
D
D
Also
measurements
I
briefly
mentioned
before
you
can,
for
example,
these
are
just
examples
and
you
can
easily
calculate
the
duration
of
your
so-called
pre-emerge
pipeline
as
we
used
to
call
it
where
you
push
some
commits
to
to
get
a
burger
eat
or
whatever,
and
then,
until
you
have
reached
the
end
of
this
pipeline,
we
can
do
such
measurements
and
see
how
it
evolves
over
time
and
similar
time
for
the
post-merge
pipelines
that
you
create.
You
can,
for
example,
create
calculations
on
your
build
result,
frequency.
How
often
does
a
build
succeed?
D
B
I
ask
a
question
at
this
point.
Yes,
so
I
understand
this
is
you've
been
going
through
pure
protocol
here
there
is
no
talk
of
implementation,
which
is
fine.
This
there
is
a
definition.
That's
that's
very
important.
May
I
ask
what
exactly
what?
What
are
the
actual?
What
is
the
actual
implementation
that
you
folks
used
as
at
arrington
and
I'm?
Sorry
at
Ericsson,
for
this,
for
example,
what
message
was
was
at
Kafka?
What's
this,
what
is
the
event
store
that
you
used?
Is
it
elasticsearch?
What's
what
did
you?
What
did
you
actually
use?
Yeah.
D
So
for
message
propagation,
we
actually
use
rabbitmq
grab.
Thank
you,
okay.
Thank
you.
Mq
implementation.
There
that's
our
message:
bus
implementation
with
Federation
between
a
lot
of
different
gravity,
every
time
host,
I'm
done
for
storing
the
events.
We
currently
use
MongoDB,
but
you
also
have
an
elastic
search
interface
on
top
of
that
MongoDB.
So
we
can
query
the
database
where
there
are
search
queries
if
we
like
yeah,
actually.
E
D
Then
we
are
quite
extensive,
supporting
Jenkins
for
both
triggering
on
events
and
sending
events.
It
is
actually
so
actually
sent.
Implicitly,
you
don't
need
to
specify
them
yourself
when
you
define
your
flow,
but
instead
obvious
whenever
you
just
specify
a
create
a
job
with
a
specific
type,
and
you
will
get
those
events
for
free,
so
it
will
link
all
the
activity
vents
for
you.
In
the
background.
D
That's
quite
quite
a
reused
as
well
I'm
not
going
to
use
in
Yankees
pipeline
I'm,
very
interested
to
try
out,
take
it
on
as
well
and
really
use
or
go
to
some
extent
as
well.
So
we
have
some
different
type:
Kannan
Jets,
but
yeah.
As
you
know,
the
protocol
is
agnostic
to
underlying
architecture.
I,
don't
think
I
have
much
more
time
so
yeah
you.
D
B
Would
really
be
great
and
it's
something
that
I'm
sure
Kristy
can
can
sound
off
on
this
as
well.
There's
there's
a
couple
of
different
efforts
going
on
within
Tecton.
That
is
definitely
in
the
same
wheelhouse
as
what
you
just
defined.
In
fact,
Antonia
Fratelli
started
a
a
document
which
I
started
to
to
contribute
to.
B
A
D
D
B
E
D
A
@Ml,
so
we
are
already
over
time,
if
you,
if
anyone
has
any
question,
we
can
go
a
few
minutes
all
time
if
not
I
will
get
the
slides
from
email
and
I
asked
Denver
to
put
them.
You
put
the
slice
in
CDF
presentations
repository
and
then
the
link
to
slice
will
be
including
minute
of
meetings.
So,
if
you
are
subscribed
to
see
interoperability
mail
list,
you
will
get
the
minutes
and
you
will
get
the
link
to
slides,
which
you
can
look
at
them
offline
and,
as
I
noted
Christy
will
present
Tecton
on
February
22
meeting.