►
Description
The State of Continuous Delivery - Christie Wilson, Google
Continuous delivery is a software development practice in which teams release software changes to users safely, quickly and sustainably. Delivering new software features faster, while making sure services are solid and secure is a key differentiator for every organization today. As organizations grapple with continuous delivery adoption, they have to contend with the space going through a renaissance with the onset of microservices, containers and cloud-native technologies. In this keynote, Tracy Miranda and Christie Wilson take a look at the current state of continuous delivery, how it continues to evolve and how we can all work together in open source to drive its future.
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
Well,
actually,
that's
not
true,
oh
really!
Well,
first
of
all,
most
people
don't
even
know
what
continuous
delivery
really
is
and
second
of
all
I
do
know
my
stuff,
because
I
am
doing
continuous
delivery.
Oh,
could
you
explain
a
bit
more
yeah.
I
work
at
a
really
cool
company
where
web
scale,
when
I
write
a
commit
within
an
hour,
a
blue
green
deployment
has
safely
rolled
it
out
straight
to
production.
So
I
know
what
I'm
talking
about
and
you
are
probably
not
doing
continuous
delivery.
A
A
I
guess
this
is
your
first
job.
No,
I've
been
working
for
a
few
years
now.
Well,
you've
been
doing
it
wrong,
they're
all
idiots.
That
thing
is
hot
garbage.
Oh
none
of
you
understand,
cap
theorem,
you're
all
doing
it
wrong.
Is
it
really
surprising
that
so
many
people
have
imposter
syndrome?
Sometimes
it
feels
like
you
have
to
have
perfect
execution
of
everything
all
the
time
or
someone's
going
to
tell
you,
you've
been
doing
it
wrong.
What
is
up
with
all
this
gatekeeping?
A
It
doesn't
really
matter
if
it's
being
done
on
purpose
or
not,
because
it's
keeping
people
out
fortunately
we're
starting
to
realize
that
keeping
people
out
is
not
the
way
to
make
the
best
software.
What
we
really
want
is
to
be
inviting
people
in
and
hearing
from
more
perspectives.
We
need
to
be
inclusive,
hey
there.
A
Well
because
earlier
that
person
said
that
I
wasn't
really
doing
continuous
delivery,
I
mean
my
company
is
so
far
behind.
We
deployed
a
production
twice
a
year
after
a
long
code.
Freeze,
I
shouldn't
even
bother
now.
This
is
why
I
think
definitions
are
so
important.
You
don't
have
to
be
doing
continuous
deployment
to
be
doing
continuous
delivery.
A
A
Why
do
so
many
people
have
different
understandings
of
these
terms?
Why
do
some
people
think
cd
stands
for
continuous
delivery
and
some
people
think
it
stands
for
continuous
deployment?
Why
do
some
people
think
that
continuous
delivery
is
this
thing?
That's
separate
that
you
do
once
you're
done
with
continuous
integration.
Why
do
some
people
think
continuous
integration
is
dead?
It's
because
we're
all
really
excited
about
these
ideas.
A
People
want
to
be
doing
a
better
job
of
delivering
software,
so
they've
taken
these
ideas
and
run
with
them
and
that's
okay,
but
it
can
make
it
really
hard
when
you're
new
to
the
space
and
that's
why,
with
the
cdf,
I've
been
working
on
a
place
where
we
can
all
collaborate
on
these
definitions
and
here's
what
I've
found
so
far.
Continuous
delivery
is
an
umbrella
term
for
the
practice
of
releasing
software
safely
and
sustainably.
The
goal
is
to
always
be
ready
to
release
and
to
automate
your
release
processes.
That's
the
goal,
that's
the
practice.
A
Does
that
mean
that
if
your
code
base
is
sometimes
broken,
you're
not
doing
continuous
delivery?
No,
it
means
you've
got
improvements
to
make
think
about
other
practices.
You
might
take
part
in
what
do
you
have
to
do
to
be
a
painter?
Well,
you
have
to
paint
that's
it
if
you
paint
you're
a
painter,
what
about
being
a
runner?
What
does
that
take
well
running?
If
you
run
you're
a
runner?
Does
that
mean
you're
doing
it?
Well,
maybe
maybe
not
do
you
have
to
be
setting
records
and
winning
races
to
be
a
runner?
A
No
in
each
of
these
practices,
when
you
want
to
improve,
there
are
elements
to
improve
in.
There
are
lenses
through
which
you
can
look
at
your
practice
and
decide.
What
you
want
to
improve
and
continuous
delivery
is
no
different.
Here
are
some
of
the
lenses
through
which
you
can
look
at
your
continuous
delivery
journey
and
evaluate
it
version
control
is
the
foundation
for
everything
else
if
you're
not
using
version
control.
This
is
absolutely
where
you
want
to
start
on
top
of
version
control.
A
We
add
practices
that
let
us
verify
changes
as
we
integrate
them
like
static
analysis
and
testing,
and
we
want
these
tests
to
be
running
regularly,
giving
us
feedback
on
every
change.
Once
we
start
looking
beyond
integrating
and
verifying
changes,
we
start
looking
at
practices
around
building
and
releasing
like
configuration,
management
and
automating
deployments
and
releases
as
much
as
possible
and,
of
course,
interleaved
through
all
of
these
practices.
A
We
need
enough
security
to
trust
the
results
if
you're
interested
in
more
in
the
cdf,
the
best
practices
special
interest
group
is
working
on
fleshing
out
recommendations
around
these
best
practices
and
more
who
here
isn't
in
some
way
contributing
to
releasing
software.
We
all
are
we're
all
in
some
way
or
another
building
software
and
releasing
it.
Maybe
the
process
is
more
manual
than
you'd,
like
maybe
you're,
delivering
burnt
cds
by
carrier
pigeon,
but
you're
still
doing
continuous
delivery.
A
Am
I
doing
continuous
delivery?
Are
you
making
software
well
yeah,
then
you're
doing
continuous
delivery,
but
we
haven't
even
run
our
unit
tests
in
three
months.
Okay,
so
you've
got
some
work
to
do
who
doesn't
instead
of
comparing
your
company
to
some
other
company
and
lamenting
how
far
behind
you
are
on
your
continuous
delivery
journey
meet
yourself
where
you
are
and
remember
this
whole
space
is
continually
evolving.
What's
cutting
edge
right
now
will
be
old
hat
five
years
from
now,
git
didn't
exist
until
2005.
A
github
is
only
13
years
old,
continuous
delivery,
as
a
concept
came
into
existence
only
11
years
ago.
Where
will
we
be
11
years
from
now
meet
yourself
where
you
are
and
when
you
hear
all
the
speakers
at
cdcon
talking
about
the
future
of
continuous
delivery,
pick
one
thing
you
can
improve
for
the
projects
that
you
work
on
and
feel
really
good
about
it.
Even
if
it's
small,
because
even
if
you
don't
change
anything,
you
are
already
doing
continuous
delivery.