►
From YouTube: SIG Interoperability Meeting - Feb 3, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
B
I
I
that's
good,
I
mean
what
what
company
are
you
with
right
now,
sap.
C
A
Not
very
specifically,
right
we're
we're
looking.
What
we're
looking
at
is
is
mainly
to
have
kind
of
an
orchestrator
independence
and
we
just
have
tons
of
teams.
B
I
think
at
the
next
meeting,
which
is
for
the
event
sake,
is
on
the
14th.
Fidelity
is
going
to
be
presenting
on
their
use
of
cloud
events,
sort
of
across
their
ci
cd.
B
B
Nice,
okay,
so
that
might
be
interesting
for
you
that
meeting
yeah.
B
Okay
and
those
would
be
policy
checks
or
which,
what
exactly.
A
Yeah,
there's
a
ton
of
things
where
which
our
teams
today
need
to
need
to
care
about
right.
It's
open
source
security,
static
code
checks
and
static
application;
security
testing,
for
example,
study
code
checks.
They
anyway
do
but
sas
tooling
ip
compliance
topics,
and
so
on
many
many
many
things
and
you
know
there's
at
least
one
tool
per
area.
B
Exactly
yeah,
it's
really,
I
think,
I'm
finding
a
really
strong
use
case
within
the
internal
platforms
and
things
like
that.
That's
great,
that's,
really
interesting!
It
would
be
great
to
have
your
involvement
in
those
meetings
as
well.
So
can
you
all
see
my
screen?
I'm
sharing
the
hack
image
document.
A
B
Okay,
great
so
welcome
everyone
to
the
interoperability
sake
great
to
have
you
here,
so
we
have
no
action
items
to
review
for
today.
So
that's
quite
nice,
but
what
I
would
like
to
remind
you
all
on
is
that
the
cdcon
cfp
is
still
open.
It's
open
until
close
of
day
18
february.
B
I
think
there's
a
little
bit
of
I
mean
you'll,
see
it
on
the
cfp
page,
it's
like
midnight,
I
think,
pacific
time,
but
basically
18th
february
end
of
day.
That's
your
that's
your
deadline,
so
it
would
be
great.
You
know
more
talks
than
mario.
We're
really
excited
to
read
your
talks
and
to
have
your
participation
in
citycon.
B
Please
submit
a
talk,
even
if
you're
unsure,
if
your
company
will
or
can
sponsor
your
travel
now
and
sort
of
permit
your
travel,
the
way
that
we're
seeing
a
different
regulation
and
rules
around,
certainly
the
western
world,
but
also
yeah,
actually
pretty
much
yeah
the
world
things
are
loosening
up.
So
hopefully,
uconn
will
be
accessible
for
more
and
more
people
around
the
world.
B
B
On
that
note,
we're
also
organizing
contributor
segments
for
cdcon,
but
at
the
moment
these
are
focused
on
cdf
projects.
So
within
the
interoperability
space
we
are
very
likely
to
run
a
contributor
summit
for
cd
events,
because
that's
now
a
cdcom
project
quite
exciting,
but
you
can
see
all
our
projects
on
the
projects
page.
B
Oh
see
the
events,
our
newest
project,
if
you
all
are
involved
with
any
of
these
project
communities
plea,
please
make
sure
that
you
know
if
you
would
like
to
see
a
contributor
summon
and
participate
in
one.
Please
encourage
your
community
to
sort
of
step
forward
to
ask
for
space
on
the
day.
There
is
a
form
below
some
of
the
communities.
B
I've
already
spoken
with,
such
as
jenkins
and
tecton,
but
you
know
we
we
have
room
and
we
have
at
least
two
days
and
there's
a
number
of
rooms,
so
we
should
be
able
to
provide
space
for
all
the
communities
that
want
to
come
together
and
we'll
ask
us
to
be
able
to
provide
you
know:
food
and
beverages
on
the
day,
though,
maybe
not
lunch,
but
certainly
breakfast
snacks
drinks.
So
that's
quite
nice
and
yeah.
B
We
just
want
to
make
sure
that
you
all
know
it's
happening
so
that
everyone
who's
interested
would
be
able
to
form
a
contributor
summit,
and
let
us
know
so
it
can
be
organized
and
on
the
note
of
conferences
fosdemos
this
weekend,
which
is
pretty
awesome,
the
cicd
devrum
looks
great.
There
are
people
from
within.
B
You
know
our
space
and
cdf
speaking,
but
even
just
generally
within
the
cicd
space,
there's
a
great
number
of
talks,
so
we
have
an
interoperability
with
cd
events
and
andrea
and
eric
are
speaking.
That's
nice
there's.
Also
a
number
of
talks
on
jenkins
oleg
is
giving
one
and
it
should
be
great,
so
obviously
fosdem
free,
it's
virtual
this
year.
B
Don't
you
don't
engage
if
you
can
don't
hesitate
to
engage
if
you
have
any
questions
about
cdcon.
This
is
a
good
moment
to
ask.
B
Okay,
super
and
then
we
are
fatty,
unfortunately,
is
going
to
be
stepping
down
as
co-chair-
and
I
say
unfortunately
because
he's
been
amazing
for
two
years,
but
he
has
been
co-chair
and
really
just
doing
a
fabulous
effort.
He's
been
amazing
for
two
years,
so
he
is
ready
to
step
down
and
so
now
we're
looking
for
another
co-chair.
If
you
are
at
all
interested
in
co-sharing
the
interoperability
sig,
then
please,
please.
Let
us
know
we
would
welcome
your
volunteering.
B
Okay,
not
going
to
worry
too
much
about
that,
then.
For
now
we're
also
anne-marie's
prs
are
still
up
on
stages
and
step
she's
working
at
more
new
detail
terminology.
We
discussed
this
a
little
bit
last
meeting,
but
you
take
a
look
at
them.
Unfortunately,
she's
not
on
the
call
today,
which
is
kind
of
too
bad.
She
could
provide
more
insight
on
what
she's
looking
for
or
if
she
feels
how
she's
feeling
about
them.
But
please
do
look
at
these
pr's.
Is
there
anything
that
you
all
want
to
discuss
on
them?.
B
Cool
good
well
provide
feedback,
reviews,
jump
in
and
let
emery
and
the
rest
of
us
know
what
you
think.
B
B
Yeah
actually,
on
this
note,
are
there
any
particular
presentations
either
of
tools
or
end
user
case
studies
that
you
all
would
like
to
hear
about
or
would
like
to
present
on
in
upcoming
meetings.
B
B
There
good.
B
This
area
software
supply
chain
fatty,
is
starting
a
new
software
supply
chain
security
sig,
so
I
would
imagine
we'll
be
losing
with
them,
but
they
will
be
sort
of
leading
that
conversation,
but
it
should
be
good.
It
should
be
really
good.
I
really
sign
that
to
be
part
of
it.
That
should
be
formalized
very
soon.
It's
already
in
process
to
do
so.
B
So
and
cd
events
going
extremely
well,
you
can
see
we
have
a
new
go
to
the
home
page.
We
have
a
new
website,
that's
under
development
for
cd
events,
pretty
exciting,
it's
still
very
much
in
beta
mode,
but
more
and
more
is
being
added
to
it
in
terms
of
the
documentation
and
the
cd
events,
repo.
B
Similarly,
getting
going
more
and
more
shall
be
added
to
it.
If
you
wanted
to
participate
in
contributing
to
any
of
the
work
there
or
the
sdks
are
under
development.
There's
one
most
active
development
is
on
the
go
on
there's
a
python
one.
That's
going
to
be
starting
soon,
based
on
the
go
one
there's
also
a
java
sdk
that
probably
will
be
kicking
off
soon,
because
there's
a
number
of
individuals
who
are
interested
in
having
it
so
by
all
means,
join
the
cd
events,
slack
channel
and
and
or
the
cd
events
same
meetings,
cool.
D
B
Nice,
so
that's
actually
really
all
my
notes
and
announcements
for
you
all
today,
but
if
you
have
any
questions
for
me,
let
me
know
or
anything
else
you
want
to
discuss
today
and
also
we
should
probably
think
about
the
general
schedule
for
for
this
egg
moving
forward.
B
B
So,
like
cd
events
was
an
awesome
thing
to
grow
out
of
this
egg
last
year
and
like
it
would
be
great
to
have
sort
of
another
really
tangible
area
to
lean
into.
B
B
C
Great,
I
think
one
thing
that
I'd
be
really
interested
in
is
to
have
some
like
a
like:
a
catalog
of
quality
events,
quality
gates.
C
B
Nice,
so
for
catalog
of
quality
gates,
you're,
not
talking
about
different
frameworks
or
tools
that
help
you
create
quality,
gates,
you're
saying
what
are
the
types
of
quality
gates
that
end
users
tend
to
create?
They
go
about
some.
C
C
B
So
these
would
almost
be
like
sort
of
a
listing
of
of
different
ways.
Quality
gates
are
being
used,
but
then
also
maybe
like
little
mini
case
studies
like,
for
example,
I
said
sap.
We
use
a
quality
gate
for
this,
and
this
is
how
we
use
it.
Is
that
sort
of
thing?
Okay,
yeah.
C
This
probably
falls
more
under
steak
best
practices,
but.
D
C
Curious
about
how
we
would
qualitatively
evaluate
a
pipeline.
B
B
B
C
Are
good
and
useful
for
this
this
context,
I
think
if
we
were
to
take
the
what
what
amounts
to
the
best
practices
grading
question
and
put
it
in
the
kind
of
work
I've
seen
this
sig
do
it
would
be?
What
signals
do
we
use
for
quality
like?
Can
we
quantify
the
signals
that
one
would
use
to
evaluate
quality.
D
C
If
you
have
zero
quality
gates,
that's
bad!
If
you
have
30,
that's
maybe
also
bad.
I
don't
know,
but
so
there's
there's
some
number.
That
would
be
better
than
other
numbers,
and
so
that
might
be
a
signal
to
ways
that
we
would
think
about
pipelines
and
the
health
of
pipelines
and
quantifying
the
metrics,
but
not
making
any
evaluations
on
whether
that
number
is
good
or
bad
seems
similar
in
kind
to
the
work
of
cd
events
and.
B
So
this
initial,
like
survey
or
asking
of
what
are
people
really
doing
in
practice,
is
really
more
just
information
gathering
and
then,
and
not
not
at
this
moment
in
time,
sort
of
making
any
judgment
call
but
really
seeing.
How
does
this
work
for
people
in
practice
and
then
using
that
information
to
kind
of
get
a
sense
of
best
practices?
I
would
imagine
it's
so
context
dependent
like
so
much
of
this
is
you
know,
but
it
would
be
interesting
to
see
like
from
industry
to
industry.
B
B
So
again,
really
practical
question:
what
do
you
think
is
the
best
way
to
start
gathering
this.
B
Do
you
want
to
start
either
an
issue
or
some
sort
of
page
on
the
interopsig
repo
or
the
best
practices
repo
or
both
and
link
them
and
and
kind
of
be
like
this?
Is
the
area
we're
going
to
gather
this
information
in.
B
B
C
B
And
so
is
it
at
all
normal
to
differentiate
between
the
quality
gates
that
you
would
run
and
use
before
I
mean
other
than
just
straight
up
testing,
but
before
doing
any
amount
of
roll
out
like
is
there
is
it?
Is
there
a
natural
split
between
before
rolling
out
anything
and
the
checks
that
are
done
when
you're
rolling
out
that
might
be
yeah.
C
It
is
the
I
think,
most
quality
gates
would
happen,
pre-roll
out
well,
at
least
before
they
hit
production
and
then
there's
like
a
monitoring,
slash,
ramping
process
that
would
do
some
amount
of
validation
once
it
hit
production.
B
B
C
B
How
do
you
differentiate
between
these
sort
of
quality
checks
are
happening
during
a
rollout
or
a
product,
progressive
delivery
versus
the
checks
that
you
run
all
the
time
when
it's
out,
like
anything,
that's
running
100
in
production,
or
is
it
just
a
continuation
of
the
same.
C
It's
a
little
different
for
us,
so
we
for
our
canary
rollouts.
We
have
a
few
metrics
that
we
kind
of
bake
in
like
error
rate
latency.
Things
like
that
and
teams
can
add
their
own
custom
metrics,
and
then
it
mostly
differentiates
based
on
what
the
result
is.
So
if
that
alarm
happens
to
trip,
then
it
will
roll
back
the
deploy
or
cancel
the
deploy
and
roll
back
as
opposed
to
just
paging
somebody,
and
so
it's
a
subset
of
our
metrics.
C
C
C
Of
the
one
of
the
dimensions
of
the
metrics
is
the
build
id
of
the
artifact
that's
being
deployed,
and
so
we
only
look
at
the
most
recent
one
when
evaluating
those
metrics
versus
our
actual
alarms.
That
page
us,
we
don't
care
about
what
the
build
id
is.
It's
a
larger
aggregate
set
of
data.
B
We're
thinking
too,
on
this
finding
what
quality
gates
that
people
are
using
within
teams
or
within,
like
a
company
thinking
about
which
quality
gates
are
absolutely
standardized
across
all
teams,
and
how
much
differential
like
how
much
additional
quality
gates
some
teams
have
versus
others
or
different
focus
areas.
B
C
Yeah
there's
a
standard
minimum
and
we're
trying
to
provide
pooling
to
increase
the
minimum.
So
like
everybody
like
basically
raised
the
bar
on
what
everyone
has
to
do,
but
that's
a
that's
a
work
in
progress
yeah
so
right
now
our
security
scans
are
asynchronous
and
non-blocking,
and
so
we're
working
to
make
that
synchronous
and
blocking
because
we
don't
want
security
issues
in
prague.
B
B
C
So
it's
a
little
slow
and
a
little
flaky
we're
in
the
process
of
moving
to
a
more
standard,
kubernetes
approach
like
this
kubernetes
deployment
model,
which
is
going
to
firm
up
our
software
bill
of
materials,
make
that
much
clearer
and
then
we
have
tooling,
which
will
operate
on
that
bill
of
materials
to
basically
do
a
better
security
scan
than
what
we're
doing
currently.
B
Nice,
okay,
good
all
right,
so
I
will
leave
you
to
set
up
this
page
from
the
cdf
point
of
view.
We
can
do
a
shout
out
on
channels
and
social
media
try
and
get
some
more
input
and
then
hopefully,
we'll
have
something
really
interesting
to
review
for
next
time,
which
I
think
would
be
pretty
cool
and
if
you
know
any
either
yourself
or
you
know
your
team
or
anyone
else
that
you
know
is
doing
interesting
work
in
their
quality
gates
and
would
like
to
speak
on
it.
C
B
Okay,
so
that's
the
half
hour,
I
don't
have
any
other
topics
on
my
agenda,
but
if
you
all
have
anything
else
you
would
like
to
discuss.
That
was
a
good
time.
B
Okay,
thank
you
all
for
being
here.
Remember
fosm
this
weekend
that
should
be
great
citycon
cfp
and,
if
you're
involved
in
any
of
our
projects,
please,
you
know
become
lead
organizer
to
host
a
contributor
summit.
It
should
be,
they
should
be
really
fun.
B
So,
okay,
good
and
please
do
get
involved
on
this
quality
gates
discussion.
It's
very
interesting
to
see
what
other
companies
and
teams
are
doing
and
how
much
variation
there
is.
I
like
this
a
lot.
Thank
you.
Thank
you.