►
From YouTube: CDF SIG Events - Feb 13, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
A
B
Sure,
usually,
which
can
you
share,
which
people
which
are
in
these
meetings
like
on
our
recording
basis,
it's
like
people
from
CD
Foundation?
How
does
it
work.
A
We
usually
are
like
I,
don't
know
four
or
five
people,
maybe
in
these
meetings
and
there's
people
from
from
all
over
the
city
Foundation.
It's
it's.
People,
of
course,
are
interested
in
the
events.
Parts
of
the
interoperability
work
that
is
ongoing
in
the
foundation,
so
I
think
it
varies
quite
a
lot
who
is
here
I'm,
usually
here,
as
as
the
chair
of
the
group
together
with
Andrea
Victory,
is
also
one
of
the
chair
to
this
meeting.
A
B
I
submitted
last
week,
I
think
the
the
call
for
papers
ended
on
Friday
yeah.
A
B
A
Yeah,
okay
I
see
we
have
that
under
as
well
welcome,
let's,
let's
get
started
on
so
Bruno
or
I
can
just
first
mention
the
agenda.
I
hope
you
see
my
screen
sharing
here
now
we
do
yeah
perfect.
So
we
don't.
We
don't
have
any
action
items
from
previous
meetings
that
I
have
noted
at
least
this
time
today
we
will
have
a
presentation
from
Bruno
on
the
test,
Cube
tool
and
then
we'll
be
looking
into
some
updates
from
other
groups.
A
If
there
is
anything
valuable
to
share
here
in
this
group,
then
I
will
briefly
just
mention
about
the
CDF
awards
that
are
being
caught
up
right
now
and
announced
yeah.
So
they
actually
award
should
be
announced
later,
of
course,
with
silicon,
but
then
the
process
of
nominating
and
electing
the
people
to
get
these
Awards.
This
started
out.
I
will
mentioned
about
that
and
then
some
words
about
conferences
that
has
been
held
or
that
are
to
be
held
quite
soon.
A
Anything
in
particular,
you
would
like
to
add
to
the
agenda.
We
can,
of
course,
depending
on
time,
add
more
topics
in
the
end,
but
should
we
add
something
already
now
or
should
we
wait
till
we
get
there.
A
A
B
So
I'm,
just
I'm
gonna
talk
a
bit
about
test.
What
test
cube
is
and
the
reason
for
is
what
is
the
vision
for
it
and
also
do
a
demo
and
explain
what
problems
are
we
solving
and
also
talk
about,
ycd
event
like
what's
the
interest
here
and
what
was
the
potential
so
but
also
served
first,
we
just
test
Cube
as
soon
as
in
the
tool
and
what
it
does
so.
Testcube
is
a
tool
for
test
orchestration
and
execution
in
any
kubernetes
environment.
So
it's
12
teams
automate
and
run
tests
there.
B
The
the
reasoning
behind
this
tool
is
that
csab's
system
were
not
made
with
testing
in
mind.
They
were
made
to
continuous,
integrate
and
and
and
deploy
things
right
and
there's
this
aspect,
which
is
the
testing
aspect
of
it
when
it
comes
to
merging
code
or
deploying
to
certain
environments,
and
they
can
do
those
things,
but
it's
not
like
their
main
purpose
on
their
attic
like
they're,
not
very
adaptable,
at
least
into
the
new
times.
B
In
of
you
know,
githubs
and
different
environments,
and
all
of
that,
so
they
were
it's
it's
complex
to
do.
Distance
automation
and
another
aspect
of
this
is
that
the
testing
tools
that
are
built
are
not
built
with
running
kubernetes
or
running
indones,
particularly
environments
in
mind,
and
it's
not
like
a
bad
thing.
It's
like
normal
right
when
you
build
a
testing
tool,
you,
the
lesson
tool
is
made
to
test
whatever
use
case.
B
That
tool
is
built
to
test
for
right,
testing
and
running
those
stats
in
kubernetes
or
Automation,
and
all
that
is
like
an
afterthought.
It's
things
that
are
people
do
on
top
of
it
after
they
have
the
tool
ready
for
them.
So
what
what
we
do
here
with
test
cube
is
basically
we
come.
B
We
see
what
are
the
patterns
to
all
the
testing
tools
and
with
different
test
types
with
API
testing,
UI
testing,
load,
testing
and
type
of
tests
that
you
want
to
run
in
a
you
know
in
an
environment,
and
we
we
see
that
there
are
other
parts
which
is
you
have
a
pipeline.
We
have
some
things
that
you
want
to
run.
You
have
an
environment,
you
want
to
run
all
of
these
tests
and
then
you
we
want
to
see.
Okay,
did
my
test
pass
or
fail?
B
If
so,
I
want
to
promote
my
code
to
a
different
place
or
I
want
to
just
see
what's
happening?
What's
the
state
of
my
environment
is
everything
all
right,
so
one
one
part
is
the
automation
part
of
it
and
creating
an
integral
details
into
your
automation
systems,
and
then
the
other
part
is
seeing
those
things,
and
while
doing
this,
you
need
to
empower
and
simplify
this
process
to
all
of
your
team.
B
There
are
a
lot
of
stakeholders
when
it
comes
to
testing,
because
you
have
the
developers
that
you
know
do
the
code
and
see
the
test.
They
are
the
testers.
They
are
the
devops
team.
They
are
even
the
the
product
managers
and
product
owners
and
like
people
from
business,
they
want
to
say:
okay
is
like.
Is
these
things
running
well
or
not
like
What's
Happening
Here?
So
a
lot
of
people
have
some
stake
in
when
it
comes
to
testing
right,
even
though
like
from
different
ways
in
different
perspectives.
B
So
that's
why
we
build
Tesco
piece
is
to
be
a
kubernetes
native
testing
framework,
where
that
is,
anyone
can
use
just
to
run
tests
and
like
automate,
everything
there
and
see
what
are
the
results.
So
it's
not
an
alternative
to
a
cic
system.
It's
something
that
you
use
with
your
cic
system
to
make
the
testing
aspect
of
it
easier
when
it
comes
to.
You
know,
running
things
in
into
kubernetes.
So
this
is
the
the
UI
of
test
Cube.
There
are
teams
that
use
it
just
CLI
and
everything
is
CLI
based.
B
There
are
other
teams
that
want
to
use
the
UI
aspect
of
it
because
they
are
they
like
the
visual
side
and
they
like
to
see
things
now
running
and
doing
things
in
an
official
manner.
People
like
other
things
like
doing
both
so
just
because
it's
more
Visual
and
it's
easy
for
you
to
understand,
I'm,
just
doing
a
visual
demo,
so
I'm
just
going
to
use
the
UI
and
not
use
the
CLI,
because
the
client
does
the
same
thing.
B
No,
it's
just
on
the
terminal,
so
foreign
test
here
I'm
just
going
to
given
the
name,
let's
say:
CD
events
and
I'm
going
to
run
keysex,
which
is
load
test,
so
I'm
gonna,
maybe
say
load
test
and
cannot
label
so
so
test
Cube
tries
to
adopt
the
characteristics
of
kubernetes
like
the
the
patterns,
the
way
you
group
things
and
and
the
way
it
works,
and
so
anybody
that
is
kubernetes
and
is
already
familiar
with
the
mythologies
of
the
cloud
native
landscape
when
going
also
to
test
Cube,
DLC
tools,
patterns
and
in
a
easier
manner,
also
a
dotted.
B
For
example,
we
allow
people
to
add
labels
to
all
the
resources
and
group
them
so
if
they
want
to
add
a
level
to
certain
kinds
of
tests,
let's
say
text
tests
that
are
only
run
on
production.
You
can
label
all
the
tests,
let's
say
production
and
then
you
can
say
test
Cube
run
all
my
tests.
It
has
this
label.
B
So
there's
like
there's
like
a
way
we
do
to.
You
know
to
group
things
and
that
is
comes
inspired
by
kubernetes
and
the
way
they
handled
it.
So
everything
here
also
is
a
crd.
That's
the
the
way
we
also
Define
tests
in
the
kubernetes
cluster.
B
So
right
now,
I'm
just
gonna,
you
know
just
create
a
simple
test.
So
what
you
need
to
do
create
a
test
in
test
cube
is
just
give
it
a
name.
You
don't
need
to
execute
level.
You
just
need
to
test
the
other
type
type.
What
what
it
does
you
just?
You
just
tell
test
Cube,
which
Docker
image
to
take
to
run
the
test
that
you
need,
because
it
does
all
the
dependencies.
For
example,
if
you
have
to
run
a
postman
test,
you
just
need
to
tell
test
Cube.
B
Oh
I
want
to
postman
test
because
that
test,
you
will
fetch
a
Docker
image
like
which
you
call
executors
that
as
Postman
installed,
if
you
want
a
k6,
you
need
images
of
sk6
and
so
on
and
so
forth
if
I
press
the
same.
So
this
is
what
tells
test
Cube,
which
thing
is
going
to
fetch,
and
then
you
can
either
say
that
the
source
is
a
git
file.
For
example,
you
can
put
your
git
credentials
here.
B
You
can
upload
the
file
directly
if
you
want
to
do
something
like
quicker
manual
or
give
even
like
do
even
code
here
on
on
the
top
for
different
kinds
of
tests,
so
for
for
this
example,
I'm
just
gonna
upload
the
file
that
I
have
on
my
computer,
which
is
a
k6
test,
and
what
it
does
is
just,
does
load
testing
against
an
environment,
so
I'm
just
going
to
create
it.
So
this
is
a
is
a
Javascript
file,
and
it's
just
before
I
run
it.
This
is
what
was
done
behind
the
scenes
was
test.
B
Cube
put
this
yaml,
his
crd
defined
it
on
your
cluster.
So
if
you
didn't
do
this
manual
like
we
did
now-
and
let's
say
you-
you
are
running
this
in
a
cicd
system.
Your
cicv
system
would
deploy
like
if
you
want
to
Define
successful
deployed
this
definition
for
you.
So
you
can
either
do
this
on
the
CLI.
B
You
can
generate
the
same
thing
or
the
DUI,
then,
if
you
want
to
automate
things,
the
thing
you
have
to
we
just
you
know,
have
make
sure
that
these
yamas
are
deployed
on
a
kubernetes
environment
where
you
want
to
run
to
test-
and
this
is
all
you
need
test
cube-
is
going
to
fetch
the
dependencies.
It's
going
to
fetch
the
the
contents
of
the
test
and
and
then
takes
care
of
all
the
things
when
it
comes
orchestrations
right
now,
I'm
going
to
run
this
test,
so
what's
being
done
right
now
is
test.
B
Qb
is
scheduling
jobs
in
the
kubernetes
cluster
right
now
that
are
running
like
the
kubernetes
scheduler
is
just
scheduling
them
to
execute
these
tests
per
on
purpose
fails
after
the
time
it
was
programmed
to
do
that.
So
you
can
see
tests
failing
and
Test
passing
so
now
they
are
all
running
like
in
parallel
and
we
see
them
like.
So
it's
just
finishing,
and
so
we
gather
metrics
about
that
execution.
B
So
the
time
it
takes
the
logs,
for
example,
I'm
going
to
click
on
this
one,
for
example,
test
you
fetches
the
logs
from
that
job.
It's
run
on
your
cluster,
so
with
this
it's
very
easy
to
scale
to
do
a
lot
of
tests
right,
usually
pipelines
can
be
constrained
in
the
month
of
load.
They
can,
they
can
take
right
and
like
you,
can
configure
them
to
be
integrated
with
kubernetes
and
the
job.
B
So,
but
that's
like
a
complex
or
like
not
as
straightforward
case,
especially
when
it
comes
to
testing
and
test
query
is
made
for
that.
So
when
it
comes
to
scaling
you
just
if
you
want
to
run
more
tests,
you
just
need
to
add
more
resources
to
your
cluster
and
everything
here.
Like
just
runs,
you
know
normally,
so
you
can
you
can
you
can
can
cities
here?
B
You
can
see
the
the
logs
as
they
are
being
produced
by
by
your
machine,
and
you
know
just
see
things
happening
and
you
can
also
use
the
CLI,
and
so
this
is
like
a
dashboard
you
can
use
and
then
you
can
use
test
Suites.
So
you
can
group
tests.
If
you
want
to.
B
Let's
say
you
have
a
test
Suite
that
does
API
testing
using
any
tool,
for
example
Ginkgo,
which
is
a
golang
framework
for
testing
apis.
You
could
use
Cypress
and
testy.
B
Why,
and
let's
say
after
that,
you
do
some
more
testing
using
artillery,
which
is
a
two
lucky
six
for
load
testing,
so
you
can
create
a
test
Suite
with
all
those
things,
and
these
are
all
those
steps,
and
then
you
just
tell
this
Cube
run
my
test
Suite,
which
is
also
off
those
tests,
and
then
does
everything
if
you
want
to
change
testing
tools,
if
you
want
to
have
more
tests,
if
you
want
to
do
a
lot
of
things,
you
don't
need
to
change
your
cicd
pipeline.
B
You
just
need
to
do
the
changes
on
test
cubes,
because
this
is
the
only
thing
that's
casually
would
do
in
this
case
would
be
only
to
trigger
things
whatever
you
define,
if
you,
if
you
want
to
to
test
to
trigger
from
the
cicd
pipelines.
Another
feature
that
testcube
has
is
triggers,
so
we
we
plan
to
follow
a
model
which
is
more
asynchronous
so
in
a
way
that
this
don't
wait
for
scissors
system
or
a
person
clicking
on
a
button
to
run.
B
Tesco
would
know
when
to
run
tests
and
that's
when
we
start
with
the
events.
That's
why,
when
events
start
appearing
here
as
the
our
opportunity,
so
we
already
built
a
functionality
which,
where
a
user
can
tell
test
Cube
to
to
run
tests
based
on
if
on
cluster
events,
so
things
that
happen
in
a
kubernetes
cluster.
B
B
So
in
this
example,
when
a
deployment
deployment
is
a
kubernetes
resource,
a
kubernetes
deployment,
PT's
label
gets
modified
test,
Cube
will
run
a
test
and
the
name
of
the
test
will
be
sanity.
So
these
are
all
the
tests
that
no
are
were
defined
in
test
Cube.
It
is
the
list
of
them,
you
can
write
them
or
you
can
run
test
based
on
label
or
based
on
the
name
or
like.
However,
you
want
it
to
be,
so
you
can
so
then
what
happens
with
this
is
the
test.
B
Cube
will
basically
do
not
need
to
be
triggered.
You
just
need
you'll,
just
listen
for
things
that
happen
in
our
cluster
and
based
on
on.
No
whatever
you
want
it
to
be,
you
can
run
tests.
The
most
popular
use
case
is
when
a
new
image
gets
deployed,
a
new
version
of
your
app.
So
let's
say
you
have
an
integration
environment,
so
there's
an
Armstrong
deployer
with
your
application,
indeed
its
own
version,
let's
say
1.10.
So
now
we
release
1.11,
which.
F
B
A
new
deployment
with
a
new
image
there
right,
so
we
you
can
click
here
and
you
can
say
when
is
deployment
with
this
image,
the
image
change,
so
the
name
it
got
updated.
After
that
happens,
it
means,
like
somebody,
made
a
new
deployment
to
the
cluster,
so
I
want
you
to
run
this
set
of
tests
automatically.
B
So
just
you
know,
I
think
I
can
do
already
the
same
way
right
now.
I
investing
are
important
is
we
want
to?
We
want
test
Cube
to
listen
to
events,
and
we
want
us
to
to
produce
events.
The
reason
for
this
is
to
be
able
to
integrate
with
a
lot
of
tools
from
the
community
and
to
have
a
standards
for
it,
because
teskey
wants
to
be
the
the
tool
that
is
using
that
is
used
for
tests
in
a
kubernetes
environment.
B
We
want
to
be
like
create
patterns
and
definitions
of
structure
that
then
can
be
used
by
any
tool
that
can
integrate
or
as
like,
once
we
integrate
with
test
Cube
or
does
wants
to
do
testing
so
any
cic
system
that
wants
to
do
testing
any
testing
tool
that
wants
to
integrate
with
this.
They
will
follow
standard
and
the
standard
needs
to
be
like
a
very
you
know,
flexible
thing,
so
one
is
for
example,
events
related
with
deployment
and
testing
would
trigger
testing.
B
So
let's
say
we
can
configure
test
Cube
to
listen
for
CD
events,
so
things
that
happen
on
the
cicd
pipeline,
like,
for
example,
an
application
got
deployed
to
an
environment
or
like
something
needs
to
be
tested
that
you
could
listen
to
that
and
then
trigger
tests.
And
then
let's
say
you
have
Captain
so
I'm,
not
sure.
If
you
know
the
two
captain
we
are
thinking
about
integrating
with
Captain,
which
is
to
like.
F
B
Tickets
there
so,
let's
say
test
Cube
could
be
the
source
of
Truth
to
tell
the
tests
are
if
tests
are
passing
or
failing,
then,
for
example,
the
way
this
would
communicate
will
be
using
events
and
then
the
call
tickets
will
be
passed
based
on
the
events
that
are
generated
by
a
desk
when
it
comes
to
testing.
So
there
are
other
tools
like
after
before
the
test
get
executed
and
after
as
well,
that
would
listen
and
and
use
these
events
as
a
sort
of
communication
mechanism.
B
So
so
that's
like
the
vision
we
want
to
be
in
a
synchronous
environment,
which
is
events,
and
we
have
events
for
like
a
lot
of
things
that
people
might
find
it
useful
for
yeah
and
then
do
like
awesome.
Integrations.
A
Yeah,
that's
particularly
great
interesting
to
hear
so.
This
sounds
sounds
very
interesting
to
me
and
I'm,
looking
forward
to
to
our
continuing
cooperation,
of
course
in
the
standards
for
this.
These
test
events,
then
so
I
guess
I
have
a
couple
of
questions.
I
think
I
saw
on
your
website
that
the
code
is
most
written
in,
go
right,
so
you
would
use
the
go
SDK
for
City
events.
If
so,
yes,.
A
You
would
go
for
go
yeah,
that's
good,
perfect,
so
I
was
thinking.
Now
we
are,
as
you
know,
having
the
pull
request
there
from
mola
and
I
guess.
A
You
were
involved
in
this
as
well
to
get
in
these
test
events
in
City
events,
and
if
you
would
get
your
your
talk
accepted,
it
would
be
great
to
have
these
test
events
included
in
the
in
the
protocol
in
a
formal
release,
I
think
before
the
Silicon
so
yeah
just
to
to
inform
about
that
a
bit
we
we
are,
we
Our
intention
is
to
release
a
version
of
seed
events
in
time
for
silicon.
A
We
that
this,
the
content
of
that
is
not
set
yet
but
testing
events,
especially
one
one
candidate
there,
and
then
we
also
intend
to
have
another
release
before
that
which
actually
earlier
was
intended
to
be
already
this
week
now
the
middle
of
February.
But
that
won't
probably
happen
the
main
thing
to
get
in.
There
is
incident
events
and
we
can
come
back
to
that
later
on,
but
so
there
might
be
a
risk
quite
soon
and
then
another
one,
hopefully
before
silicon,
and
that
would
be
great
to
have
this.
A
As
a
showcase,
then
for
for
those
new
testing
events,
if
you
would
integrate
those
I
already,
I
also
hope
that
under
the
go,
SDK
would
be
implemented
in
the
same
time
frame
so
that
that
would
be
available.
So
you
could
directly
talk
about
that
being
being
out
there
and
released.
That
would
be
great,
so
I
mean
some
basic
questions.
I
guess:
where
did
you
first
hear
about
citizens
and
from
from
whom
or
how
do
you
get
to
hear
about
it?.
B
I
think
it
was
from
kubecon,
we
talked
with
Fati
yeah
before
so
this
could
be.
We
are
members
of
the
CD
Foundation,
like
silver
Partners
or
something,
and
so
we
go
to
a
lot
of
conferences
and
like
we
are
in
the
area,
and
so
we
I
think
we
just
because
CD
the
city
Foundation
is
like
a
brother
or
sister
to.
F
A
So
you
mentioned
Captain
before
which
is
such
a
new
AI.
This
is
also
an
event,
asynchronous
events
based
tool,
but
not
really
in
the
testing
area,
but
rather,
as
I
said
in
quality
Gates
earlier,
so
are
there
any
competitors
related
to
the
test?
Cube
I'm,
not
too
involved
in
kubets,
deploy
implementation
myself
really
for
and
exactly
I.
Don't
have
control
of
all
the
tools
that
exist
for
sure.
So.
B
Yeah,
this
will
be
impossible
to
have,
like
you
know,
to
know
about
RP
so
that
there
are
so
many
so
test
Cube
as
competitors,
but
nothing
in
a
very
direct
sense.
B
They
are
more
indirect
competitors,
meaning
like
when
it
comes
to
a
tool
that
is
made
to
run
tests
in
the
cloud
native
way
in
kubernetes,
there's
only
two
that
there
is,
but
there
are
other
tools
that
in
general,
allow
you
to
do
some
automation,
but
not
specifically
for
kubernetes,
or
there
are
tools
that
allow
to
run
those
tests
in
the
cloud
in
an
automated
fashion,
but
just
their
types
of
tests.
So
it's
like
testing
what
it
does
that
combines
a
lot
of
these
tools
that
they
do
it
just.
B
You
know
more
specifically
for
certain
use
cases,
and
this
could
be
like
more
General.
So,
instead
of
just
focusing
on
some
types
of
tests
or
some
types
of
automation,
we
allow
to
to
be
the
tool
that's
used
like
okay,
you
are,
you
are
running
tests
in
kubernetes
test
cube
is
like
your
your
go
to
Tool.
A
Right
right,
so,
if
we're
done
very
we're
in
a
bit
more
to
the
test
Cube,
but
what
does
the
I
mean
if
you
have
a
test
Suite
of
test
cases
to
execute?
What
does
the
the
workflows
that
say?
Look
in
there
can
you
define
in
what
order
to
execute
test
test
cases
and
so
on
on
the
execute
this?
If
that
succeeds
and
or
execute
all
these
in
parallel
or
is
it
like
a
flow
description
somewhere
here
as
well.
B
Exactly
it's
exactly
as
I
said
so
right
now
you
can
test
which
are
defined
as
a
list
of
test
cases,
and
you
can
either
say
when
one
of
them
fails.
You
stop
so.
B
Basically,
it's
rather
than
test
case
a
b
and
c
whatever
we
Define
one
fails
a
new
stop
and
the
test
it
fails,
or
you
can
also
program
it
to
run
all
of
them
regardless
if
one
of
them
fails
or
not,
because
you
might
want
to
also
see
the
executions
of
all
the
other
ones
and
then
at
the
end
we
have
the
report
like
we
have
the
list
of
tests,
and
then
you
see,
basically,
you
know
the
logs
and
what's
happened
there
when
it
comes
to
parallelization
inside
the
test
Suites.
B
You
cannot
do
that,
like
Define,
like
let's
say,
run
three
steps
in
parallel,
then
wait
for
them
and
then
run
these
two
and
then
run
more
like
the
those
more
complex
logic
is
not
possible
yet,
but
it's
being
implemented
right
now
as
well,
you
can
run
tests
in
parallel
using
labels,
so
you
can
say,
run
learn
all
my
best
to
test
these
labels,
but
there's
no
like
built-in
functionality
in
test
view
where
you
say,
run
t-set
of
tests
in
parallel
and
then
these
ones
and
then
these
ones
you
can.
B
A
Okay,
okay,
yeah,
of
course
yeah
great,
so
about
this
event
trigger
that
you
showed
there.
You
said,
for
example,
that
you
would
like
to
run
a
test
Suite
when
a
certain
artifact
has
been
deployed
or
something
is
it
also
possible
today,
or
do
you
have
plans
to
to
support
triggering
on
like
data
from
multiple
events
like
aggregate
the
data
for
multiple
events?
So
if
you
would
have,
for
example,
one
artifact
being
deployed
and
also
reached
a
certain
quality
gate
or
maturity
level,
or
something
like
that?
Like
a
combination
of
different
events?
B
So
today
it's
only
possible
to
listen
to
Cluster
events
from
your
cluster
and
not
conditions
for
it
and
that
those
conditions
is
like
I
want
my
deployment
and
my
config
map
open
later,
so
you
can
say
which
event
is
the
the
starter
and
then
conditions
there
are
things
that
test
you
can
write
to
be
ready.
For
example,
a
deployment
is
changed,
but
the
Pod
is
still
starting
right.
B
So
you
can
say
after
deployment
is,
is
done,
I
want
my
image
like
the
bot
to
be
ready
and
then
only
then
you
can
run
the
test
because
the
Pod
might
not
be
no
right.
It
takes
a
few
seconds
right
to
for
the
part
to
start
you
can
see
those
things
for
the
quality
Gates
and
things
you
mentioned.
That's
our
goal.
That's
that's
what
we
are
trying
to
work
on,
which
is
we
want
to
to
first
see
standards
or
ways.
B
We
can
tell
test
Cube
to
listen
for
things
from
places
and
then
run
tests
based
on
those
things,
but
right
now
we
didn't,
we
don't
know
yet
like
what
to
look
for
and
which
events
from
which
tools.
B
So
if
you
have,
if
you
have
suggestions
like
tools,
you
know
even
that
you
know,
please
send
it
my
way
or
or
relay
or
like
one
of
us
and
yeah
that's
what
we
are
looking
for.
We
want
to
integrate
with
tools
that
process
events
run
tests.
A
Right
there
I
think
it.
It
also
relates
a
bit
to
to
how
we
rate
these
events.
What
content
to
put
into
them,
because
there
are
discussions
on,
should
we
in,
should
we
add
all
data
that
we
know
into
modest
order
events,
or
should
we
expect
the
consumers
of
these
events
to
make
sense
of
a
serial
series
of
events
instead
to
get
all
the
data
that
they
need
to
to
do
their
jobs?
A
Let's
say
so,
for
example,
if
a
deployment,
an
artifact
is
deployed
that
such
an
event
could,
for
example,
contain
the
ID
of
the
artifacts
and
the
location
where
to
find
it,
and
maybe
even
the
source
change
that
was
the
trigger
for
creating
that
artifact
and
a
lot
of
different
content,
or
it
could
just
be
just
a
pointer
to
this
artifact
that
I,
already
described
sometime
before,
is
now
deployed
in
this
environment,
or
something
like
that
and
then
to
understand
more
about
what
does
this
object
contain
or
what
are
the
aspects
of
the
artifact?
A
So
that's
what
I
was
thinking
about
it
I
mean
we
are
discussing
in
different
areas:
how
to
make
sense
of
the
or
how
to
aggregate
events
that
comes
on
the
Stream
to
see
and
then
trigger
on
on
the
those
aggregated
data.
From
from
a
stream
of
events,
let's
say
not
just
one
single
event,
so
that
was
what
I
was
curious
to
see.
If
you.
A
Have
some
kind
of
language
to
describe
like
triggering
on
multiple
events
that
somehow
depend
on
each
other,
but
it
seems
you
don't
really
have
that
yet.
A
Yeah
yeah,
that's
it
yeah,
so
you
also
mentioned
Captain
there,
which
we're
very
much
aware
of
they
were
involved
very
early
in
this
11th
standard
as
well,
and
they
are
still
very
interested.
We
haven't
seen
them
recently
in
our
meetings,
unfortunately,
the
one
from
there
as
far
as
I
know,
but
as
far
as
I
know,
they
are
still
very
interested
in
integrating
City
events
in
Captain
as
well,
and
that
would
be
a
perfect
fit.
Then
for
you
to
to
integrate
with
Captain
and
showcase
that
as
well.
F
A
Okay,
okay,
I
see
all
right,
so
yeah
I
don't
have
too
many
more
questions.
Will
you
by
the
way
talk
about
coupon?
Will
you
be
in
Amsterdam
in
in
April
talking
about.
B
I'm
going
to
be
there
we're
going
to
have
a
boot,
so
please
laugh
by
there.
Unfortunately,
none
of
our
thoughts
got
accepted,
so
I
think
we
are
going
to
apply
to
the
rejects
conference.
I'm,
not
sure
if
you
know
about
that
one,
it's
like
a
it.
So
all
the
thoughts
get
rejected
at
kubecon.
There's,
like
another
conference
made
like
right
after
for
the
people
that
got
rejected
from
kubecon
I,
think
it's
online
I'm,
not
sure.
So
you
can
see
a
coupon.
F
B
17.
yeah,
it
is
on
the
is
it
still
in
Amsterdam
as
well.
So
it's
like
a
fun
thing.
Some
people
tell
that
these
Styles
aren't
even
better
than
the
the
cubeconomics.
A
E
A
Yeah
I
think
this
looks
very
promising
looking
forward
to
having
seed
events
integrated
into
testcube
pretty
much
yeah.
F
B
F
B
Do
you
want
to
I
think,
do
you
need
me
for
anything
else?
No,.
F
F
B
Yeah
yeah
and
let's
talk
about
the
pr
so
I'm
gonna
work
with
too
late
to
see.
If
we
can
finish
that
PR
and
we
have
it
merged.
A
Now
so
we
have
the
presentation
there
and
the
next
topic
for
the
agenda
is
I'll
play
some
other
groups,
so
I
guess
we
are
most
most
of
us
are
quite
involved
in
the
City
events
group
peer
work
group.
So
this
might
not
be
too
many
news
for
us,
then,
just
to
for
the
sake
of
the
recording
and
to
have
it
here.
I
would
like
to
mention,
then,
that
we
are
working
on
the
incident
events
and
the
connecting
events
and
the
testing
events.
A
Those
are
probably
the
three
main
categories
of
work
items
that
we
work
with
right
now
and
Our
intention
is
to
release,
as
I
touched
upon
before,
to
release
the
incident
events
quite
soon,
and
we
hope
that
there
will
be
a
formal
City
events
release,
including
the
incident
events
which
are
important
for
promoting
that
we
can
now
handle
all
over
core
Dora
metrics,
so
those
will
hopefully
be
released
quite
soon
in
a
City
events
release,
and
in
parallel
to
that,
we
also
work
on
the
connecting
events
which
is
about
how
to
relate
events
to
each
other
in
some
different
means.
A
So
we
are
discussing
links
Allah
Eiffel
there,
the
iPhone
1
protocol
or
we're
also
discussing
a
context
IDs
or
Trace
IDs
or
Global
IDs
different
names,
workloads,
different
kinds
of
global
or
global-ish
IDs,
so
you're
very
much
invited
to
work
with
us
there
and
the
testing
event
is
what
ola
mentioned
there
before
that
there
is
a
pull
request
there
for
improving
on
the
test
events
that
we
have
with
its
own
bucket.
Now
that's
about
the
Sullivan's
work
group
for
the
rest
of
the
groups
and
the
TLC
I
don't
have
anything
written.
A
C
From
the
TOC
point
of
view
next
meeting
is
tomorrow:
no
I
don't
think
there
was
any
three
events,
a
specific
well
I,
think,
probably
from
from
the
TSC.
He
brought
up
City
events.
C
You
can
try
to
yeah.
C
Mentioned
that
Mary's
point
of
view,
it's
yeah
it's
it's
very.
It
would
be
very
good
to
see
the
events
implemented
in
the
in
the
projects
or
at
least
in
some
of
the
projects
hosted
by
the
city,
Foundation
kind
of
like
eating
our
own
dog
food
as
a
CD
foundation.
So
integrating
City
events
into
the
into
the
different
CD
F
hosted
project,
and
you
know
demonstrate
internal
probability
there,
but
I
remember
so
yeah,
that's
something
that
also
Robert
is
interested
in
helping
with.
A
You
mentioned
that,
or
we
talked
about
it,
I,
don't
know
in
the
epoc
to
that
we
could
promote
to
have
it
in
Google
summer
code
projects
and
they're
already
such
defined
for
or
there
is
one
defined,
at
least
for
Jenkins
X,
for
integrating
with
steel
events,
at
least
the
proposal
for
it
for
Jenkins.
There
might
not
be
any
such
yet
and
I'm
not
sure
about
the
other
projects
if
they
have
have
some
keys
of
this
ongoing,
but.
C
Yeah
I
tried
reaching
out
to
Jer
and
waiting
for
his
reply,
which
are
from
Fidelity,
and
it's
also
the
governing
board.
The
the
the
first
use
use.
The
story
was
also
published
and
I.
Don't
know
if
fox
has
seen
it,
but
it's
it's
from
Fidelity
and
it
mentions
as
project.
It
mentions
Jenkins
and
City
events
and
his
stays
in
there.
That
Fidelity
is
interested
in
adopting
City
events
and
integrating
City
events
with
Jenkins
so
on.
C
We
need
to
start
the
conversation
again
on
how
to
make
make
that
pattern
in
in
practice
and
maybe
trying
to
put
some
dates
in
front
of
this,
because
I
think
we've
been
discussing
about
this
since
silicon
last
year,
but
we
were
not
able
to
get
some
progress
yet,
partly
because
yeah,
maybe
we
just
had
the
first
release
and.
C
F
A
A
So
then,
you
might
have
seen
this
as
well,
but
there
are,
there
is
the
CDF
awards
for
process
for
2023
has
been
kicked
off,
so
denominations
are
now
open
since
last
Wednesday
and
we
have
created
a
an
issue
on
our
own
guitar
project
for
nominating
people
for
the
City
events
project.
A
So
we
are
expected
to
to
contribute
one
one
person,
one
reward
winner
for
this
project,
so
each
project
in
this
area
will
will
provide
one
one
such
person
I,
think
expect
exactly
for
the
graduated
product,
which
would
actually
have
more
than
one
I'm
sure.
If
you
have
more
information
about
that
Andrea.
What
what
there's
some
more
categories,
I
think
for
this
example
Jenkins
and
techno
right.
It
will
be
more
than
one
category
I.
Think
Rewards
foreign.
A
Again,
yeah
yeah,
that's
right!
That's
us
here!
So
graduated
projects
will
have
these
three
different
categories
of
awards
and
each
other
project
will
have
the
most
valuable
contributor
award.
A
And
then
we
have
also
the
the
top
levels-
let's
say:
CDF
Awards
these
ones,
which
are
also
able,
of
course,
to
denominate
people
to
and
then
some
of
these
at
least
we
are
able
to
vote
on
us
as
well,
I'm,
not
sure
if
we
are
able
to
vote
on
all
of
them,
but
maybe
you
are
and
some
are
more
closed
votes
than
others,
somehow
yeah.
So
that's
about
the
awards,
so
you
can
think
about
that
and
the
nominations
close
on
March
3rd.
A
A
A
There
was
recently
a
conference
in
Brussels
I
believe
it
was
as
it
used
to
be
the
Boston
conference
and
there
was
a
CI
CD,
a
dead
room.
There
were
there
talking
about
City
events.
Sorry
CDF
and
I
expect
that
they
also
mentioned
City
events.
There
I,
don't
really
know,
but
I
think
they
did,
and
then
there
were
some
some
more
talks.
Obviously
around
CD
events,
sorry
about
cicd,
I,
haven't
looked
into
any
of
these
details.
A
Show
up
in
one
of
you
know
more
about
those.
If
there's
anything
valuable
that
you
would
recommend
us
to
to
look
at
afterwards.
Now
I
guess
there
are
recordings
of
many
of
these
available
yeah
there's
a
recording
on
that
one,
for
example.
So
well,
if
you're
interested,
you
can
go
in
here
and
look
at
these
these
talks
and
if
there's
anything
you
would
recommend,
you
can
also
do
that
to
us.
Of
course,
I
haven't
listened
to
any
of
those.
Yet
to
myself.
A
A
F
A
A
D
A
A
E
Yeah
one
thing
to
share
on
this
CD
con,
so
the
proposal
that
we
have
made
actually
to
have
a
talk
on
CD
events,
integration
with
different
cacd
tools,
I
mean
it's
a
general
talk
about
our
experience
and
how
we
use
the
Java
SDK
and
how
others
can
use
and
they
can
integrate
different
tools.
So
it's
it's
all
about
the
topic
of
how
they
can
integrate
different
tools
to
see
the
events.
It's
a
general
talk
about
that
and.
F
E
Know
like
we
are
also
started
working
on
the
CD
events
visualization,
so
that
is
not
like
very
much
Clear
right
now
so,
but
we
are
still
working
on
that
and
then
not
sure
like
if
we
come
to
any
a
good
shape
like
the
time
we
have
a
proposal
accepted,
and
things
like
that,
so
we
may
include
some
of
the
visualization
part
also
there
but
yeah.
So
not
really
now.
E
So
it's
it's
a
General
experience
that
we
wanted
to
share
like
how
we
can
integrate
the
CD
events
so
that
we
have
submitted
for
the
proposal.
A
E
We
yeah
so
we'll
talk
actually,
so
we
are
doing
some
groundwork
like
to
show
how
exactly
this
works
using
the
visualization
first,
if
that's
the
way
we
wanted
to
use
so
we'll
show
in
in
any
of
the
Sig
meetings
and
discuss
more
on
that
like
when,
when
we
have
a
at
least
a
dimensionable.
A
Okay,
yeah
that
could
be
interesting
to
see
if
we
have
any
yeah.
The
City
events
will
look
like
there.
That
would
be
great
I
think
that
that
might
also
somehow
relate
to
the
discussion
about
connected
events
connecting
events.
How
events
relate
to
each
other,
because
if
you
should
initialize
a
chain
of
events
or
a
graph
of
event
or
how
we
should
put
it,
there
needs
to
be
some
way
to
to
reference
them.
E
Once
we
have
a
good
exposure
on
like
what
we
are
doing
now.
F
E
A
Yeah
yeah,
that's
good,
because
I
guess
the
providing
visualizations
is
one
set
of
requirements
towards
such
an
initiative
to
connect
events
in
different
ways.
So
if
there
are
certain
requirements
from
that
work
it
it
might
be
good
inputs
to
to
the
discussion
that
we
have
there
on
how
to
connect
events
in
a
good
way.
C
A
No,
so
then
I
guess
we
came
close
for
today,
five
minutes
ahead
of
time.
That's
that's
just
good!
So
thanks
good
talking
to
you
today
and
see
you
next
time,
bye-bye.