►
From YouTube: SIG Interoperability Meeting - Aug 18, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
B
A
Well,
I
suppose
we
can
go
ahead
and
get
started
more
might
trickle
in
as
we
go
on.
I
anticipated
this
to
be
kind
of
low
attendance,
just
because
I
don't
know
about
you,
but
I
feel,
like
the
last
two
weeks
were
just
a
blip,
but
we
do
have
a
few
items
to
discuss
on
our
agenda
this
time
around.
A
A
Got
posted,
I
don't
know
if
any
of
you
got
a
chance
to
look
at
it
or
if
it's
been
discussed
since
it's
been
posted,
I
don't
know
justin
have
you
had
anyone
reach
out
to
you
about
it
or
make
any
comments.
A
A
I
don't
know
if
there's
more,
we
want
to
do
here
more.
We
want
to
follow
up
with.
A
A
A
C
A
D
A
Right
well,
as
we
move
forward
here,
I'd
like
to
look
at
this
a
little
bit
more.
It
just
seems
like
there
should
be
something
out
there
or
an
attempt,
and
I
didn't
we
discussed
like
jenkins
or
something
had
tried
something
along
this
line
and
abandoned
it
for
what
one
reason
or
another.
I
think
we
still
have.
Maybe
an
action
item
there
to
get
in
touch
with
someone
that
has
the
inside
scoop
on
that.
B
A
D
B
Yeah
a
link
to
chat
melissa.
It
was
actually
ramen
who
highlighted
jenkins
sex.
Sorry
to
interrupt
you,
rajat
ramen
akbari.
He
said
jengas
had
x
had
this.
A
C
C
B
Well,
I
think
I
I
like
this
idea
about
this
internet-based
pipeline,
so
like
whatever
way,
we
can
continue
bugging
people
about
this
idea.
Just
you
know
I
can
be
you
know
reaching
out
to
people
if
you
have
people
who
know,
but
they
are
not
part
of
the
comic
just
you
know
I
can
help
you
reach
out
as
well.
A
All
right,
I
would
like
to
fill
it
out
a
little
bit
more
too,
but
I
tend
to
go
directly
to
like
the
to
do
side,
the
engineering
side
of
it
so
which
might
be
a
little
cart
before
the
horse,
but
I
would
like
I
know
we
discussed
in
the
past
of
coming
up
with
you
know,
maybe
more
examples
of
different
kinds
of
pipelines
that
could
be
written
in
this
format.
A
You
included
one
in
the
in
the
blog
posting
that
you
put
out
there
justin
and
you
know.
Maybe
we
can
fill
that
out
a
little
bit
more
with
some
of
the
other
ideas
that
have
come
up.
C
Yeah
happy
to
do
that.
The
I
think
my
bandwidth
to.
C
A
Well,
let's
keep
keep
looking
I'll
keep
you
know
bringing
this
up
from
time
to
time
and
see
if
we
can
get
some
more
attention
and
some
more
interest
and
any
of
you
on
the
call
right
now
or
listening
to
this
recording
later,
maybe
you
can.
You
know,
reach
out
to
friends
and
colleagues
see
if
there's
anyone
interested
in
taking
something
like
this
on,
because
I
really
do
think
it's
interesting
and
we're
you
know
the
very
beginning.
So
who
knows
how
it
could
turn
out,
but
I
like
the
idea.
D
One
question
from
for
me:
sorry:
maybe
I've
not
looked
into
this
enough
details.
I
was
trying
to
understand
what
the
the
user
would
be
of
the
intent
based
pipeline.
So
do
you
imagine
like
a
platform
team
that
defines
the
pipeline
in
this
format
and
then
different
teams
compiling
into
the
format
of
their
preference,
whether
if
they
use
tactile,
they
would
and
get
a
techno
pipeline?
If
you
use
jenkins
junkies
pipeline
or
everything.
C
Is
yeah?
I
was
thinking
about
it
from
the
perspective
of
like
when
I
start
a
new
project
and
I
want
to
draw
a
pipeline,
I
go
to
the
whiteboard,
just
draw
it
and
it
takes
like
10
minutes
and
then,
when
I
want
to
go
implement
it.
It
takes
two
weeks
and
it
would
be
really
nice
if
it
was
as
simple
as
drawing
on
the
whiteboard
and
I
think
that's
possible,
but
it's
maybe
not.
C
C
D
A
The
more
along
the
lines
of
a
spec
like
describing
how
something
like
this
could
be
consumable
by
multiple
tools,
I'm
imagining
just
even
the
hardship
it
is
to
move
from
one
tool
to
another
and
re
redo,
all
of
your
pipelines
and
re-implement
them
in
a
different
way
that
can
be
pretty
irritating
at
times.
Yeah.
C
D
So
that's
my
my
concern,
but
maybe
there
is
some
some
something
in
the
middle
or
I
was
wondering
whether,
like
you
said,
I
draw
the
pipeline,
I
put
certain
constraints
or
rules
there
I
mean
the
drawing
could
compile
into
some
kind
of
structured
language
like
the
one
in
the
example,
and
maybe
there
could
be
a
mechanism
by
which
a
specific
pipeline
could
be
matched
to
this
at
least
say.
Okay,
this
pipeline,
actually,
com
complies
with
this
format.
D
E
And
something
that
reminds
me
of
that,
although
is
different
and
is
less
interoperable
per
se,
is
the
get
ops
tool
kit
by
weave
works.
E
So
they've
broken
it
down
into
you,
know
your
flux
and
flagger,
but
they
have
other
components
and
then
you
can
pick
and
choose
from
that
and
there's
a
narrow
set
of
possibilities,
but
you
can
pick
and
choose
from
that
what
else
you
would
want.
So
that
seems
like
it's
heading
more
in
this
direction.
A
A
It
does
feel
like
every
time
I've
been
involved
in
implementing
a
pipeline
in
different
tools.
It
just
just
feels
like
we're,
starting
to
get
to
a
point
where
everyone
is
you
know
using
yaml.
A
Maybe
we're
so
close
to
that
that
that's
why
no
tool
exists
or
no
spec
exists.
I
don't
know,
but
I
think
it'd
be
cool
to
define
one
and
future
tools
doing
this
can
consume
that.
A
Yeah,
okay,
well
anything
else
to
say
about
that
or
comment
about
that,
any
more
action
items
we
need
to
take
on
this.
C
A
A
All
right
next
one
we
have
on
our
list-
oh
yes,
determining
where,
in
the
best
practices
site
to
add
vocabulary
documentation,
so
we
might
want
to
switch
these
items
right
fatigue.
Is
there
still
some
outstanding
stuff
that
needs
to
happen
with
the
vocabulary
documents
as
it
is
or
are
we?
I
know
there
was
a
split
that
was
done
correct.
B
Yeah,
it
was
done,
but
the
supply
chain
stages
that
pr
hasn't
been
merged
yet
and
dave
panduri
actually
commented
it
during
this
week.
I
think
so
that
needs
some
work,
but
we
don't
have
to
wait
for
supply
chain
stages.
We
can
start
working
to
the
exiting
stages
and
marry
documented
error.
A
Okay,
just
for.
A
A
Yeah
it
looks
like,
were
there
any
outstanding,
I'm
sorry,
I'm
scrolling
so
fast
any
outstanding
items
there
to
address.
B
Yeah
the
harness
was
like
the
triggers
was
added
with
the
last
latest
pull
request.
Yeah.
Oh
awesome,.
B
C
Yeah
his
he
wants
to
add
a
stage
which
basically
amounts
to
the
deploy
is
done
and
we're
just
monitoring.
Slash
waiting
for
the
next
deploy
to
happen.
Like
the
steady
state.
A
Okay,
that
wasn't
exactly
the
topic
I
was
trying
to
talk
about,
but
it's.
B
Just
to
give
you
a
historical
context
about
these
tools
terminology
or
to
why
we
collected
because
like
when
we
first
formed
the
interability
you're
like
okay.
What
is
the
purpose
of
this
sig
and
so
on?
And
we
kind
of
said,
let's
start
documenting
some,
no
popular
tools,
terminology
to
highlight
the
problem.
We
can't
even
use
the
same.
A
This
is
too
specific
for
the
best
practices
site.
Okay,
let's
just
pull
that
up,
take
a
look
at
it,
real
quick.
This
is
what
it
looks
like
right
now,
there's
various
places
we
could
put
something
like
you
know,
terminology
information.
E
Yeah
it
would,
I
mean
it
would
either
go
under
learn
or
resources
for
sure
and
learn
is
maybe
under
active
development
and
stuff
yeah.
C
E
C
C
A
B
B
You
know,
like
let's
say
just
making
things
up
like
we
start
adding
the
stages
and
steps
to
energy
into
best
practice
site
and
if,
like
people,
see
okay,
this
stage
or
step,
I
don't
know
what
this
corresponds
to
in
jenkins
or
argo
cd,
and
that
could
be
a
section
there.
All
the
tools
call
these
things
differently,
and
here
is
the
current
mapping
of
these
different
terms
redirecting
to
our
repo,
because,
as
justin
says,
like
putting
vendor
specific
stuff,
direct
isis
under
best
practice
may
not
be
received
bad.
I
know.
A
Maybe
just
linking
to
it,
maybe
like
maybe
in
the
learn
section
like
a
references
section,
we
could
just
add
a
link
back.
E
A
Yep
I
like
it.
Let's
do
that
anyone
want
to
take
that
on
just
to
open
a
pr
with
a
link.
Perhaps
we
can
start
there.
A
A
A
A
A
Okay,
next,
we
have
oh
scheduling,
presentation
time.
So
we
had
the
new
project.
Go
sem,
show
some
interest.
There
was
some
emails
going
back
and
forth
with
them
about
scheduling
a
time
getting
them
involved
with
setting
up
a
presentation.
I
have
not
heard
back
yet
when
would
be
available,
but
they
haven't
had
a
lot
of
time
to
think
about
it.
So
I've
given
them
the
possible
dates,
I
believe
the
15th
of
september
or
the
first
meeting
in
october.
A
I
did
send
out
a
question
to
tim
miller.
He
was
the
one
who
presented
it
last
time
at
our
meeting
and
I
haven't
heard
back
from
him
yet
but
same
same
story.
He
hasn't
had
much
time
to
think
about
it,
so
it's
possible.
We
may
have
some
more
presentations
lined
up
here
soon.
A
D
You
can
start
just
a
couple
of
words
about
it.
If
you
are,
if,
if
some
of
you
write
go
code,
you
may
be
familiar
with
a
tool
called
go
release
which
allows
you
to
publish,
go
binaries
in
through
many
different
package.
Managers
create
git
releases,
and
so
many
other
things.
D
Jr
release
here,
on
their
hand,
is
kind
of
a
similar
tool,
but
works
for
any
other
kind
of
source
language.
It
began
live
in
the
java
space,
but
it
can
do
so
same
things
for
rust,
javascript
or
anything.
You
name
it.
So
that's
the
reason
why
I
would
like
to
talk
about
this
tool,
because
well,
if
you're,
building,
binaries
or
just
creating
git
releases
on
the
go
on
the
pipeline,
I
mean
the
tool
can
just
do
the
work.
A
I've
taken
a
look
at
it
too
and
seen
a
couple
presentations
now
by
andres
and
other
conferences
and
stuff,
and
it
looks
really
interesting
and
also
deals
with
you
know
things
you
don't
think
about
necessarily
like
posting,
your
updates,
letting
everyone
know.
A
new
release
is
available.
A
Those
kinds
of
things
that
are,
you
know
we
all
just
kind
of
do
manually
and
on
the
side.
So
that's
what
I
I
really
like
about
this
this
project,
there's
a
lot
in
there
that
you
know
handles
things
we
do
on
the
day
day-to-day
that
we
just
haven't
really
automated
in
any
way.
Yet
so
pretty
cool
excited
for
that
presentation,
that'll
be
on
september
1st,
our
next
meeting
and
then
we'll
we
can
have
an
open
discussion
about
it.
So
start
tweeting
about
it.
A
I'll
put
some
stuff
out
on
social
media.
Get
some
interest
see
if
we
can
get
some
folks
to
come.
Watch
that
thanks,
thank
you,
andres
all
right
and
then
cara.
We
had
a
meeting
at
the
toc
last
week
and
or
or
was
it
this
week,
I'm
losing
time
now
someone
brought
up
that
we
have
yet
to
change
our
branch
default
names
from
master
domain
and
that's
something
that
we
just
kind
of
you
know
want
to
get
moving
on
across
the
board.
So
we
took
the
first
step.
A
Cara
went
ahead
and
got
our
sig
github
repo
set
up
for
that.
It's
pretty
cool.
It's
all
been
changed.
It
looks
like
everything
is
working
every
time,
I've
clicked
on
a
link,
even
in
the
past
that
you
know
had
master
in
it.
There's
some
redirects
going
on
that
sends
you
to
maine
so
that
works
out
really
nicely
so
far.
I
haven't
seen
anything,
but
you
know,
keep
your
eyes
open
for
any
broken
links
or
anything.
That
might
surprise
us.
E
Anything
else,
no,
just
quick,
thank
you
to
the
interop
sig,
because
you
all
have
volunteered
to
be
our
first
sig
to
do
this
shift.
Yeah
github
does
the
redirects
automatically,
and
so
there
hopefully
won't
be
any
trouble.
The
only
thing
potentially
is
hackmd,
so
we
will
find
out
today
so,
but
thank
you
very
much.
It's
great.
A
Oh
good,
I'm
glad
you
said
that
I
did
like
a
get
pull
and
I
get
pushed
and
stuff
from
hackmd
in
order
to
update
our
notes
on
the
github
site,
and
it
gave
me
a
warning
first
thing:
saying
branch
doesn't
exist,
but
it
was
really
easy
just
to
change
it
right
then,
and
there,
and
then
I
haven't,
had
to
do
that
again.
So
it
worked
out
very
well
and
it
looks
like
it
was.
Success
successfully
put
our
notes
on
the
github
page
where
it
belongs.
So
good
worked,
worked
great.
E
A
All
right
all
we
have
left
future
topics
for
the
interoperability
sig
justin
reached
out
and
asked
you
know
what
else
do
we
have
to
talk
about?
Are
there
any
other
avenues
that
we
want
to
go
down
anything
that
we
want
to
start
working
on,
and
he
suggested
that
you
know,
maybe
speaking
to
the
projects
that
are
in
the
cd
foundation,
asking
if
there's
any
specific
interoperability
issues
that
have
come
across
there.
C
No,
no
direct
ideas
at
the
moment.
My
my
feeling
is
that
we
a
lot
of
these
meetings.
The
interop
meetings
are
check
out
this
really
cool
tool
which
is
awesome
and
but
there's
not
a
lot
of
talk
about
actual
interop
stuff
that
we
we're
not
solving
interoperability
problems
and
that
might
be
because
we
don't
have
any,
which
would
be
awesome,
but
I
suspect
there
might
be
one
or
two.
A
A
Try,
you
know
we
have
the
whole
best
practices
effort
going
on
right
now
for
making
it.
You
know
a
a
spec
for
pipelines.
Basically,
is
there
a
way
we
can
jump
in
and
maybe
discover
interoperability
problems,
things
that
we've
forgotten
since
the
last
time
we
tried
to
put
a
bunch
of
tools
together.
Maybe
there's
some
kind
of
this
is
crazy,
but
maybe
some
kind
of
event.
We
could
pull
off
where
we
could
have
a
hackathon
that
gives
people
challenges
to
put
stuff
together
and
and
observe,
see
what
happens.
A
Let's
take
your
suggestion,
justin
first
and
reach
out
to
the
projects
that
we
have
and
just
see.
If
we
can,
you
know,
get
any
ideas
from
there
if
there's
anything
that
needs
addressing
that
has
popped
up
in
the
you
know
last
few
months
that
would
fit.
I
think
that's
a
good
idea,
good
place
to
start.
C
B
Maintainers
of
all
our
projects,
the
list,
so
we
we
can
perhaps
look
at
that,
and
then
you
can
reach
out
to
both
individuals
from
projects.
Well,
I
think
we
have
andre
and
ankit
as
we
discussed,
he
could
join
our
meeting
to
give
background
about
this,
their
dsl
stuff
and
and
for
others
yeah.
I
can
definitely
help
you
with
that
awesome.
B
A
Okay,
awesome,
as
you
find
things
or
come
up
with
ideas,
let's
put
them
in
the
slack
channel,
get
an
open
discussion
going,
there's
a
lot
of
members
in
there
that
are
not
in
this
meeting
today.
So
I'm
sure
there's
a
lot
of
ideas
that
could
be
floating
out
there.
We
just
aren't
hearing
today.
A
So
let's
start
that
I'll
take
that
on
just
to
start
the
conversation.
E
Yes,
actually,
I
would
love,
I
would
love
feedback
from
you
all
on
this
tim
miller.
This
is
what
I
think
about
when
you're
talking
about
fresca.
He
put
an
interesting
issue
in
the
cdf
landscape,
repo
saying
one
of
the
categories:
that's
not
on
the
landscape
that
we
may
want
to
consider
is
something
he
called
it
abstractions,
which
is
really
hard
to
figure
out
what
that
would
be
from
that
title.
But
I
from
his
suggestions,
I
understand
what
he
means.
E
I
put
the
link
in
the
our
chat
right
here
to
the
issue
he
raised,
but
he
he
said
we
should
have
a
category
for
things
like
fresca
and
dagger
that
are
working
at
maybe
more
of
a
higher
level,
and
I
just
feel
like
that's.
You
know:
they're,
both
using
q
he's
not
he's
not
wrong
with
what
they
do
and
it
would
be
interesting.
How
would
we?
E
E
A
C
E
D
C
E
Sure
but
I'm
happy
to
talk
more
with
you
all
about
it
and
and
do
jump
on
the
issue,
and
I
mean
you
can
say
actually.
This
is
the
best
name
when
you
think
of
maybe
higher
level
obstructions,
but
it's
yeah
is
that
necessary.
A
E
D
E
Plan
is,
we
add
this
category
with
those
two
initial
projects
to
the
to
the
landscape
and
we
leave
open
a
name
change.
We
just
put
a
comment
like
this
is
this
is
actually
the
best
name
we
can
think
of,
and
it
you
know,
does
capture
it.
But
if
anyone
thinks
of
something
else,
as
we
move
forward,
we
can
always
change
it.
A
E
Yeah,
I've
spoken
with
the
tiger
folks,
do
you
have
a
logo.
A
E
A
A
E
I
figured
this
is
the
group
that
would
be
have
the
most
interest
and
context
around
that
category.
D
A
If
not,
I
think
we
can
give
everyone
a
little
bit
of
time
back
today
and
between
now
and
next
meeting
get
involved
in
this
conversation
on
slack
about
ideas
for
the
future
again
I'll
reach
out.
You
know
regarding
more
presentations
and
stuff.
I
did
ask
you
know
it
came
up
whether
or
not
it
makes
sense
to
do
more
than
one
presentation
during
the
meeting,
and
I
think
cara
made
a
point
that
no
we
shouldn't
do
that.
A
I
didn't
want
to
schedule
one
today,
just
because
I
knew
so,
many
people
were
out
and
august
is
just
not
the
best
month,
but
we'll
get
on
the
ball
with
it
starting
september.
A
All
right
good
to
see
you
all,
as
always
I'll
see
you
next
time
september,
1st.