►
From YouTube: CDF SIG Best Practices - Apr 18, 2022
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
You
go
okay,
so
I
saw
your
note
so
I
was
working
on
this
over
the
weekend
and
I
was
like
oh,
I
just
have
to
swap
out
the
deployments
for
delivery
and
then
the
more
I
was
looking
at,
I'm
like
no.
This
is
just
all
just
wrong.
It's
not
in
alignment
with
like
it.
You
know
it
was
looking
at
the
glossary
and
I
was
trying
to
pull
stuff
over
and
I
think
it
just
needs
a
refresh.
A
So
I
have
another
pending
an
uncommitted
update
where
I'm
trying
to
to
work
on
that,
and
then
I
notice
all
of
justin's
comments.
A
B
So
originally
we
were
just
going
to
do
the
show
stoppers,
which
was
you
know
this
chapter's
not
not
got
the
right
name
right
and
and
then
go
through
and
review
the
content
and
and
then
refine
it,
because
what
we
really
need
to
do
is
get
something
that
other
people
can
contribute
to
as
a
baseline.
So
my
suggestion
would
be
to.
B
Yeah
so
get
the
let's
just
sort
the
that
one
piece
about
getting
the
the
chapter
title
right,
because
that
that's
a
a
bit
of
a
showstopper
and
then
everything
else.
Let's
move
that
into
a
you
know
a
subsequent
review
phase
because
we
can
argue
over
the
semantics
of
individual
sentences
till
the
cows
come
home,
but
sure
yeah,
okay,.
A
B
A
Okay,
so
what
I'll
do
then?
I
is,
I
will
capture.
A
I
don't
feel
so
good.
I
will
capture
the
comments
and
start
and
create
an
issue,
so
we
don't
lose
them.
So
I'm
not
sure
what
happens
in
the
comments.
A
B
C
A
A
B
A
I
do
that
okay
cool
all
right,
so
that
part
is
done.
I
completely
forgot
to
ask
kara
about
the
publishing.
I
will
let
me
get
that
email
going
right
now
and
since
it's
just
the
two
of
us
it
is
just
the
two
of
us
right.
B
A
However,
the
company
that
I
am
going
to
one
of
the
things
that
appealed
to
me
is
they
have
their
own
open
source.
Continuous
integration
system
that
it
was
built
was
was
built
with
specifically
around
doing
ci
cd
around
databases,
so
it's
called
evergreen
ci
so
and
I'm
going
to
be
vice
president
of
developer
productivity
and
the
company
is
mongodb,
and
so
I'm
hoping
to
bring
mongodb
into
the
cdf
fold.
A
A
Right,
well,
I'm
not
sure
how
many
people
look
at
that.
I
don't
personally
care,
I
mean
I'm
just
shut,
my
my
yeah
anyway,
okay.
A
A
A
Wow,
okay,
I
think
if
I
remember
correctly-
and
we
could
probably
ping
tracy
to
confirm-
but
you
had
done
a
really
lovely
job
on
the
other
section
on
the
site.
A
As
far
as
sort
of
introing
the
the
understanding
the
problem
around
the
broader-
you
know,
you
know
continuous
delivery,
meta
topic
it
it
felt
like
there
was
a
good
opportunity
to
kind
of
take,
take
a
more
just,
a
specific
version
of
that
around
secure
software
supply
chain.
You
know
a
lot
of
times,
particularly
when
you're
ramping
up
security
is
not
necessarily
as
important
in
your
early
requirements
as
you
might
want
to
consider
it,
and
what
are
the
circumstances
within?
You
might
want
to
consider
that.
A
A
Okay
but
yeah,
it's
been
a
it's
been
a
hot
minute,
so
I've
quit
my
job
since
then.
So
tracy
probably
will
have
some
details
to
remember
as
well.
B
Well,
I
can
probably
go
back
and
look
at
the
the
recording
of
the
last
session
and
get
what
the
context
was
from
that
anyway.
A
I
hope
there
was
one
it
was
left
to
me.
I
always
forget.
Hopefully,
tracy
did
okay.
That
is
my
recollection
anyway.
B
Yeah
and
then
I
just
wanted
to
make
sure
that
we
have
a
shared
understanding
of
the
the
structure
that
we're
doing
on
on
this
stuff
at
the
moment,
because
I
I
think
what
we've
got
is
a
bunch
of
independent
aspects
that
we're
talking
through
in
that
learn
section
and
then
we're
trying
to
pull
all
of
that
together
under
the
umbrella
of
continuous
delivery.
B
B
Why
do
it
that
way,
rather
than
just
have
a
one
narrative
about
continuous
delivery
as
a
as
a
whole
thing-
and
I
think
it
it
makes
sense
to
chop
it
up
into
some
of
the
perhaps
historical
pieces
like
continuous
integration
and
continuous
deployment,
because
there
are
a
lot
of
organizations
out
there
that
are
doing
bits
of
those
components
and
not
necessarily
doing
the
what
we
would
consider
to
be
continuous
delivery
or
we've
also
got
some
situations
where
organizations
are
able
to
streamline
their
process
because
of
the
nature
of
their
product.
B
B
And
I
think
it's
important
to
be
able
to
have
the
discussion
that
right
if
it
doesn't
matter
whether
your
product
works
or
not,
then
you
can
argue
that
you
don't
need
the
investment
in
all
of
that
testing,
because
as
long
as
you
can
recover
quickly,
that's
sufficient
right.
But
if
you.
A
It
means
that
you
are
investing
significantly
more
in
your
ops
team
right
in
order
to
make
that
work
versus
putting
more
of
distributing
more
of
the
load
and
kind
of
the
shared
model,
the
devops
model
on
your
developers
right
and
that
that's
an
explicit
choice.
So
if
you're
not
going
to
do
this,
then
then
you
don't
you
don't
have
a
choice
about
that.
A
A
I
don't
know:
is
that,
like
worth
a
whole
another
section
under
getting
started
or
like
what?
How
do
you
think
would
be
best
to
do
that?
Because
I
was
thinking
about
it
in
terms
as
we
started
getting
examples
that
maybe
we
could
use
those
examples
to
showcase
different
types
of
narratives
that
way,
but
that
was
also
sort
of
reliant
on
what
types
of
examples
we
get.
B
B
What's
an
acceptable
trade-off
and
where
do
you
invest
with
within
this?
It
may
be
that
we
want
to
do
a
piece
on
tailoring
because
realistically
that's
what
you're
doing
is
you're
adopting
a
methodology
but
tailoring
it
to
your
particular
environment.
A
Does
it
just
it
made
me
think
about
blogging?
We
talked
about.
A
A
Trying
to
think
what
blood
does
does
hugo
have
a
blogging
element
to
it
or
is
there?
Is
there
a
cd?
I
should
know
this.
We
have
a
cd
foundation
vlog,
you
know
we
have
a
youtube
channel.
B
Yeah
we've
we've
got
a
blog
which
goes
out
periodically,
so
that's
a
that's
another
vector
that
we
could
use
for
some
of
this
conversation.
A
C
C
B
I
I
think
that
some
of
the
netflix
examples
are
a
bit
like
that
in
that,
because
the
it
because
it
doesn't
matter
that
much
if
your
recommendations
are
not
online
24
7.,
there's
a
different
focus
on
where
you
put
the
investment
in
in
testing.
Some
of
this.
C
B
C
A
A
B
We've
got
stuff
to
get
us
to
first
release
yep
and
then
we've
got
the
you
know
the
ongoing
refinement
of
this
site
and
iterative
improvement,
and
a
lot
of
that
is
where
we're
going
to
be
doing
those
your
white
papers
and
additional
content,
blogs
and
stuff
like
that
yep,
because
in
many
cases
we're
going
to
find
examples
of
things
that
happen
in
the
real
world
that
we'll
want
to
refer
to
and
discuss
the
process
in
the
context
of
something
that's
happened.
A
No
not
at
all.
B
C
A
I
think,
after
all
that
sorry
I
talked
about
okay
getting
this
in
okay.
What
was
the
other
thing?
I'm
feeling
like?
I,
I
didn't
capture
one
of
the
things
you
said.
B
So
now
there's
there's
nothing
majorly
urgent
in
all
of
that,
I
think
we're
just
agreeing
a
shared
understanding
of
where
we
are
at
the
moment.
Okay,.
A
All
right,
okay,
let
me
get
the
notes
published
and
then
I'll
clean
up
and
get
that
pr
submitted,
create
the
new
task
to
capture
the
feedback
and
get
that
out
sounds
good.
B
Okay
I'll
review
that
as
soon
as
it
comes
in
and
commit
that,
and
then
we
can
then
move
on
to
polishing
the
rest
of
the
stuff.
I
think
the
the
one
area
where
we've
probably
got
gaps
at
the
moment
is
in
the
supply
chain.
B
Was
there
but
it
it
looks
like
it
was
just
the
beginning
of
a
work
in
progress
rather
than
actually
ready
for
every
year.
B
And
also
that
piece
is
focused
on
supply
chain
security,
but
I
think
we
need
to
cover
off
supply
chain
management
in
general,
so
we
need
to
look
at
the
licensing
aspects
as
well
as
the
security.
Oh.
A
Get
that
pr
yeah
me
too,
whatever
it
was,
I
need
to
figure
out
if
that
was
something
I
ate,
so
I
never
eat
again,
dear
god,
all
right
cheers.