►
Description
In this episode, we sat down with Fatih Degirmenci, Executive Director of the Continuous Delivery (CD) Foundation, at the Open Source Summit in Vancouver to talk about the evolving goals of the foundation and the role it is playing in the modern cloud-centric world.
A
And
we
are
here
at
open
source
Summit
in
Vancouver.
Today
we
have
with
us
once
again
and
once
again
we
have
with
us.
You
are
executive
director
of
The
Continuous
delivery
foundation,
so
this
is
great
to
have
you
back
on
the
show
in
person
right.
Yes,
we
saw
extra
like
as
you're,
reminding
me
very,
very
early
days
of
Spinnaker
after
that
will
happen
and
we
have
been
talking
remotely,
but
it's
great
to
see
you
again
in
person
which
brings
me
to
the
point
or
last
time
we
talked
about
when
the
Syrian
Foundation
was
like
announced.
A
But
now
I
want
to
talk
a
bit
about.
You
know
the
state
of
the
foundation
today
what
you
folks
have
achieved
some
Milestones,
where
we
are.
B
Thanks
for
having
me,
as
you
mentioned,
it's
great
to
see
you
again
after
six
seven
years
in
person,
as
you
noted
the
last
time
when
we
met
over
zoom
and
discussed
what
is
CD
foundation
and
what
are
our
goals
and
what
is
our
vision?
It
was
old
days
for
me
as
well.
B
Within
the
foundation
I
joined
June
2012
to
see
the
foundation
as
the
executive
director
and
since
then,
we
have
been
working
on
identifying
key
use
cases
of
our
end
users,
the
changes
they
are
facing
and
how
we
can
help
address
those
challenges
to
help
our
end
users
and
make
them
part
of
our
community
and
just
to
recap,
contents.
Their
Foundation
is
an
open
source,
commit
to
provide
neutral
forum
for
anyone
who
wants
contributing
contents
literally
domain,
and
we
provide
home
to
funding
Dairy
projects
and
we
have
nine
projects.
B
Cd
events,
Jenkins
Jenkins,
X,
ortelius,
tecton,
Persia's,
shiplight,
Spinnaker,
I,
think
that's
sold
and
the
great
thing
about
contractor
Foundation,
which
is
relate
to
what
we
have
been
working
on.
Achieving
is
our
community
has
lots
of
practitioners
from
end
user
organizations
from
big
cloud
providers
and
we
are
all
working
together
to
find
out
how
we
can
make
our
lives
easier
when
it
comes
to
establishing
and
running
countries
through
pipelines
and
running
with
the
transformation,
of
course,
within
our
organizations
as
well
as
we
are
looking
to
different
Technologies
to
see
how
they
can
help.
B
Organizations
to
you
know
bring
new
features
plug
fixes
security
fixes
to
their
products
in
a
much
faster
manner.
So
that
is
literally
the
vision
of
contractor
foundation
and
personally
I
think
the
contents.
Their
Foundation
is
the
place
where
anyone
wants
to
take
part
in
evolving
the
continents,
their
ecosystem,
because
we
are
working
with
very
cool
stuff
that
will
transform
the
ecosystem
and
will
have
greater
impacts
on
broader
industry.
A
B
If
we
go
back
maybe
10
years
ago,
when
this
whole
virtualization
I
force
started,
everyone
was
like
okay.
This
will
make
our
you
know
life's
much
better
when
it
comes
to
Bringing
new
products
to
Market,
faster
and
so
I'm
in
Cloud
native
transformation
style
and
the
virtualization
Cloud
native
microservices.
The
cloud
itself
made
out
of
things
possible
like
we
can
simply
use
a
cloud
provider.
You
get.
You
know
your
development
environment
set
up
in
minutes.
B
You
develop
your
microservice,
you
get
that
microservice
and
all
built
into
the
Container,
which
you
get
that
container
image
test
and
deploy
it
to
your
production
environment,
and
that
is
a
great
thing
for
organizations
to
again
go
to
market
faster,
bring
cool
features,
new
products
to
their
users
faster
and
gain
competitive
Advantage
when
it
comes
to
you
know,
being
first
with
certain
things,
but
that
also
brings
additional
challenges.
Because
again,
if
you
think
about
the
you
know
traditional
way
of
doing
stuff
with
you
know
very
tightly
integrated,
you
know
software
and
hardware
and
open
source.
B
Wasn't
this
big
things
were
slow
but
kind
of
manageable?
But
now
cloud
is
bringing
additional
complexities
as
well,
because
Developers
need
to
learn
a
lot
of
new
technologies.
They
need
to.
You
know,
spend
time
on
different
activities
that
weren't
traditionally
part
of
their
job
description,
so
that
increases
you
know,
cognitive
law
load
on
are
developers,
and
then
we
need
to
make
sure
that
our
developers
could
focus
on
value-adding
activities
and
continuous
delivery
is
one
of
the
key
pieces
in
this.
B
You
know
picture
like
all
this
platform:
engineering,
SRE
and
SRE,
and
all
those
things
they
are
actually
there
to
address
these
complexities
and
difficulties.
Our
developers
may
be
facing
day
in
day
out
and
again,
conscious.
Dairy
is
an
enabler
for
organizations
to
actually
remove
that
complexity,
so
they
do,
of
course
again
could
continue
what
they
are
doing.
Creating
new
products
developing.
A
New
features
and
complexity
is
not
just,
you
know,
consumes
more
time
developers,
it's
also
cost
exactly
last
week
when
AWS,
you
know,
Prime
day
talked
about,
you
know,
microservices,
and
so
it
had
it
had
nothing
to
do
with.
Microservices
is
more
about
using
the
right
tools,
writing
modules
and
also
to
simplify
the
complexity,
because
sometimes
I
think
we
had
this
discussion
with
you
earlier.
Also
new
companies.
They
get
overwhelmed
with
new
technologies
instead
of
looking
at
what
we
need.
They're
like
hey.
A
This
is
what
we
should
use
so
talk
once
again
a
bit
about
where
you
see
the
right
approach
right
tools,
it's
not
just
because
something
is
shiny
and
new.
You
should
embrace
it
exactly
like.
B
I
I'm,
a
software
engineer:
I
will
continue
to
take
a
technical
engine.
Look
at
these
things
and
when
we
meet
with
other
you
know,
fellow
friends
from
Community,
we
start
talking
about
high
level
topics.
I
know.
After
a
while,
we
find
ourselves
talking
about
certain
tools
and
everyone
has
their
own.
B
You
know
favorite
tool,
and
so
when
it
comes
to
instigation,
people,
observative,
testing
and
so
on,
and
the
thing
I
try
to
you
know
share
with
my
fellow
friends
is
like
instead
of
us,
you
know
looking
at
what
is
the
coolest
and
let's
bring
it
to
our
organization.
We
should
look
at
what
can
help
us
to.
You
know,
move
us
forward
faster,
better
tools,
shouldn't
dictate
what
we
can
achieve.
We
should
find
the
right
tools
and
use
them
if
a
tool
doesn't
help
us,
it
could
become
an
issue.
B
You
know
you,
you
have
one
more
thing
to
look
after,
and
that
is
pretty
key
thing
and
that
is
actually
related
to
our
state
of
report.
We
published
this
week
on
Monday
and
one
of
the
interesting
findings.
There
is
the
organizations
who
are
using
modern
tools
and
techniques
for
their
devs
activities,
show
greater
Improvement
when
it
comes
to
Performance,
but
the
key
thing
there
is
not
just
any
tool
tool
that
actually
helps
you
removing
manual
work.
B
You
might
be
doing
in
the
past
and
automating
that
using
that
modern
technology,
so
you
can
spend
that
time.
You
were
spending
in
the
past
for
manually
handing
tasks
for
some
other
creative
work,
for
example.
So,
yes,
tools,
Technologies
are
important,
but
we
need
to
be
careful
when
it
comes
to
making
those
selections
and
bringing
them
to
our
organizations
and.
A
Then
we
look
at
you
know
the
trends
in
the
market.
Of
course
you
know
vendors,
you
know
when
they
come
and
also
actually
this
is
the
beauty
of
Open
Source.
Actually
that,
as
folks
create
new
tools,
you
know
hey,
there's,
there's
a
neutral
platform
that
you
can
bring,
but
at
the
same
time
it
should
also
be.
The
focus
is
also
that
hey.
This
is
what
it
tools
do
and
bring
all
the
people
together.
A
B
I
think,
like
again,
I
can
give
the
contents
their
Foundation.
As
an
example,
as
I
mentioned,
we
have
nine
projects
and
they're
all
great
projects
and
events
like
open
source,
Summit
or
audio,
and
we
had
Monday
and
Tuesday
this
week.
Cd
coin
guitar.
These
are
great
opportunities
for
our
community
members,
because
I
might
be
doing
something
at
home
and
I,
I-95
and
I
proud.
My
writing,
something
which
may
become
a
cool
thing,
but
at
the
same
time
someone
might
have
already
done
something
about
it.
B
Instead
of
me,
going
with
my
own
thing,
I
could
find
about
that
work
as
part
of
such
open
source
events
and
say:
oh,
this
looks
really
cool
and
that
actually
solves
my
problem
instead
of
me.
Creating
my
own
thing.
I
should
contribute
to
the
existing
efforts
so
like
the
collective
efforts
of
open
source
code
is
greater
than
you
know,
individual
enforce.
So
that
is
pretty
key.
You
know
think
about
these
events
and
broader,
open
source
moment
like
if
we
come
together
and
when
we
come
together.
A
B
This
is
actually
building.
On
top
of
our
conversation,
we
had
last
year's
in
August
like
when
we
talked
that
time.
We
touched
different
topics
on
a
high
level,
for
example
software
supply
chain
security.
You
know
overrated
or
to
executive
orders
European,
you
know
issuing
you
know,
regulations,
rules
around
these
things,
so
software
supply
chain
is
one
of
the
Hot
Topics.
We
encounters
their
Foundation
as
well.
So
when
you
think
about
software
supply
chain,
it
is
like
okay,
it's
it's
huge
thing.
B
Improved
state
of
software
supply
chain
and
one
of
the
announcements
we
made
this
week
is
about
one
of
our
projects,
stacked
on
which
actually
brought
in
four
new
features
for
use
for
their
users.
For
example,
salsa
like,
if
you
use
tactone,
you
will
get
salsa
level,
2
support
out
of
the
box
or
trusted
resources
and
artifact,
Hub
and
so
on.
B
So
these
things
all
help
organizations
to
secure
their
supply
chain
using
such
Technologies,
and
it
brings
multiple
open
source
projects
together,
which
is
led
to
the
question
you
asked
earlier
all
these
communities
projects
coming
together
without
thinking
like
which
project
which
Foundation
we
are
here
to
solve
this
problem.
So
that
is
a
key
effort,
our
project
and
Community
put
into,
and
that
is
one
of
things
we
announced
the
second
and
perhaps
pretty
critical
talk
which
is
related
to
security
as
well
is
interoperability.
B
But
this
is
one
of
the
key
things
we
hear
a
lot
from
our
end
users.
Again,
if
you
think
about
typical
controversary
pipeline,
when
a
developer
commits
the
code
to
Main
Branch,
it
goes
through
this
long
pipeline
until
hits.
It
hits
the
production
as
an
artifact
as
a
product,
and
that
code
interacts
with
many
systems
such
as
cold
repositories,
build
tools,
artifact
repositories,
test
Frameworks
and
all
these
things
are
orchestrated
by
contents.
B
B
For
example,
CDF
cdms
has
been
working
with
multiple
open
source
projects
such
as
Jenkins,
Spinnaker,
tecton
and
test
Cube
to
get
those
Technologies
took
using
same
language,
so
those
projects
could
speak
same
language
out
of
the
box,
which
further
enables
securing
software's
watching,
because
then
you
can
create
this
stack
graph
to
find
out
which,
from
it
caused
that
security
issue
and
go
back
and
fix
that
problem
thanks
this
common
vocabulary.
So
that
is
the
second
announcements
we
may
announcement
made
and
the
last
announcements
was
about
a
new
project.
So
we
have
an
artelius
project.
B
We
didn't
see
the
foundation,
which
is
a
microservices
framework
with
supply
chain,
coverabilities
built-in
right
that
contributed
project
emporos
to
ortelius
as
a
sub
project,
so
they
will
join
for
switches
again
led
to
the
question
you
asked
like.
Instead
of
having
two
separate
projects
working
on
relevant
areas,
they
instead
come
together
and
give
the
best
possible
experience
to
their
users.
So
these
are
three
Project
Specific
announcements
we
made
on
Monday
during
the
first
day
of
our
silicon
top
scoring
event
and
again
question
you
asked:
where
do
we
see
the
city?
B
Foundation
I
think
we
are
current
on
really
of
work
trajectory
and
our
comment
is
showing
a
lot
of
you
know
passion
putting
out
of
effort
into
solving
these
very
difficult
problems,
because
these
are
really
hard
questions
and
we
are
trying
to
find
answers
to
those
questions
and,
thanks
to
you
know
our
members,
our
end
user
contributors.
We
are
actually
moving
forward
together,
so
that
is
Project
like
seeing
this
type
of
a
force,
counter
fruition
and
get
interest
of
other
organizations.
B
A
B
So,
in
addition
to
project
updates,
we
also
announced
the
fourth
release
of
state
of
City
report.
State
of
City
report
is
a
tradition
of
contester
foundation.
We
release
the
new
iteration
of
state
of
City
report,
doing
silicon
our
Flagship
event
and
the
fourth
one
was
released
on
Monday
and
it
is
similar
to
previous
reports,
but
there
are
differences
compared
to
last
year.
B
One
of
the
key
findings
within
report
is:
it
shows
that
the
devops
adoption
is
increasing,
which
is
good,
but
at
the
same
time
the
adoption
might
be
slow
down,
because
in
previous
years
the
increase
was
larger
than
this
year's
increase.
I
think
this
year
it
was
two
percent
more
than
last
year,
and
that
brings
up
questions
like
why.
Why
speed
slow
down
and
some
of
the
reasons
could
be
again.
Devops
is
not
just
about
using
the
Technologies
or
you
know,
creating
pipelines
or
making
sure
that
there
and
Ops
teams
comes
together.
Is
it
actually
impacts?
B
Many
parts
of
the
organization?
Organizational
structure
needs
to
be
adjusted.
The
cultural
aspects
should
be
explained
to
organizations,
so
they
can
Embrace
change.
In
addition,
that
product
structure
may
need
to
be
adjusted
to
support
the
speed.
You
know
sustainability
that
comes
with
devops,
so
that
may
be
these
three
four
things
may
be
reasons
why
the
devops
adoption
is
not
that
fast
compared
to
how
it
was
previous
years.
B
Another
interesting
finding
is
that
again,
this
goes
back
to
Technologies
if
the
organizations
employ
right
tool
or
technology
for
their
their
Ops
activities,
which
could
be
test
framers,
build
automation,
tools,
observability
application,
Performance
Management,
that
helps
organizations
to
become
better
performance.
So
that
is
again,
it
was
same
last
year
and
it
is
still
great
to
see.
People
are
actually
automating
things
rather
than
doing
things
in
a
manual
manner,
which
is
again
very
difficult
to
maintain
and
you
know,
transform
a
new
finding
in
this
year's
sport,
which
wasn't
there
last
year
is
application.
B
Security
testing
is
actually
second
most
popular
activity
by
the
organizations,
and
that
also
highlights
that
if
organizations
automate
application
security
testing
and
make
those
things
part
of
their
pipelines,
that
actually
improves
their
performance
as
well.
So
that
is
a
key
finding
of
this
year's
support,
and
obviously
there
are
things
we
need
to
improve.
B
Otherwise
we
just
you
know,
quit
our
jobs,
so
one
of
the
things
we
find
found
while
we
looked
at
respondent
response
responses,
we
got
from
thousands
of
people
increasing
number
of
devopsy
Technologies
help
organizations
to
become
better
but
increase
in
number
of
hosted.
Ci
CD
tools
doesn't
show
that
greater.
You
know
performance
Improvement
like
when
an
organization
uses
like
four
or
five
cic.
It
was
that
actually
has
a
weird
curve.
B
Sometimes
it
impacts
the
performance
negatively
and
the
way
we
look
at
that
data
is
maybe
lack
of
this
interability
across
these
different
Technologies,
the
contributing
factor
why
the
performance
is
not
showing
Improvement.
So
that
is
kind
of
confirms
like
why
we
have
been
putting
other
effort
into
this,
and
hopefully,
since
CDs
adoption
started
right
now,
with
Jenkins
Spinnaker,
protect
on
and
test
script
leading
the
way
next
year
or
the
year
after
next.
B
We
should
see
some
improvements
there
as
well,
because
then
organizations
will
not
need
to
deal
with
increased
complexity
of
the
pipeline
stem
cells
as
well,
because
products
are
already
causing
difficulties.
Maybe
some
developers-
and
we
need
to
remove
this
complex
from
the
supporting
you-
know,
infrastructure
pipelines
and
so
on.
Perhaps
the
type
of
platform,
engineering,
kind
of
approaches.