►
From YouTube: Best Practices SIG - May 17, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
A
A
Okay,
well,
what
was
your
interest.
B
Yeah
so
I
work
at
Google,
I'm,
a
CI,
CD,
developer
Advocate,
so
I
primarily
focus
on
tecton
scaffold,
Cloud,
build
Cloud,
deploy
all
that
stuff
and
Tech
Town's
always
been
a
passion
of
mine
and
I
want
to
get
more
involved
in
the
CDF.
So
this
is
my
first
attempt
at
joining.
A
Okay,
cool:
have
you
seen
the
the
best
practices
work
that
we've
been
doing
on
the
website.
A
Okay,
have
you
seen
best
practices.cd
DOT
Foundation.
A
That's
our
actual
documentation
site.
So
that's
what
this
this
special
interest
group
is
is
about.
Basically,
is
never
mind.
A
Cool
so
yeah,
let
me
probably
the
best
way
is
for
me
to
just
give
you
an
overview
of
what
what
we've
been
up
to.
Let
me
just
get
to
a
point
where
I
can
share
that.
B
B
Yeah
I
wonder
if
it
might
be
helpful
on
the
Sig
best
practices
repo
in
GitHub,
to
have
a
link
to
best
practices.cd.foundation.
A
Yeah,
so
it
should
be
links
on
there's
a
couple
of
different
routes
into
to
this.
There
should
be
links
in
in
all
of
them.
B
Yeah
I
don't
see
it
on
GitHub,
but
maybe
it's
in
the
notes
or
something.
A
Okay,
unfortunately
Chrome
was
decided.
It
doesn't.
Let
me
screen
share.
Okay,
no
worries.
Let
me
try
again
from
different
atmosphere.
If
that
works,
any
better
foreign.
A
It
did
the
classic
you
just
enter
into
the
meeting,
Zoom
updates
so
and
then
yeah
everything
stops
working.
A
A
A
So
this
is
this
is
what
we
were
working
on
and
the
idea
really
is
just
to
try
and
communicate
the
if
you,
like,
the
the
sort
of
design
patterns,
the
ways
of
thinking
about
continuous
delivery,
because
most
people
come
to
continuous
delivery
because
they've
adopted
a
tool
or
are
exploring
one
cell
or
another.
A
A
So
the
intent
here
really
will
understand
the
context
and
how
to
think
about
working
in
a
continuous
delivery
methodology.
A
So
yeah
feel
free
to
to
jump
in.
If
you
one
more
detail
on
specific
things,
the
the
learn
section
is
where
we
cover
the
general
bits
and
pieces.
C
A
A
We
we
see
a
a
very
common
misunderstanding
when
people
are
adopting
continuous
delivery,
because
they're
they're
either
coming
out
here
from
an
organization
that
has
never
done
it
before
or
they're
coming
at
it
typically
from
within
an
organization
that
does
it
all
the
time,
so
everyone
is
doing
it,
but
nobody
is
talking
about
why
they're
doing
it
because
those
decisions
were
you
know
five
ten
years
ago,
and
everyone
has
has
kind
of
moved
on
from
that
that
piece
of
thinking
right,
so
it's
very
difficult
for
people
who
joining
an
organization
to
to
really
understand
why
they're
doing
things
this
way
and
how
that
could
shape
the
the
way
they
think
about
the
building
their
Solutions.
A
So
what
we
try
and
communicate
here
is
the
fact
that
this
is
actually
not
an
engineering
methodology.
This
is
a
business
methodology.
D
A
Yeah,
so
it's
that
that
whole
idea
of
you
know
what
what
you're
trying
to
do
is
that
iterative
lean
software
delivery
process
where
you're
doing
product
discovery,
and
so
you
need
to
be
doing
things
in
production
environments
with
real
customers.
D
A
D
A
And
so
the
rest
of
the
methodology
is
is
therefore
how
can
you
get
as
efficient
as
possible
delivering
in
that
way?
A
So
so
that's
what
we
we
cover
off
in
here
really
and
you
know,
covering
off
how
to
how
to
do
it
wrong
in
in
the
bad
and
dangerous
ways,
and-
and
just
you
know
getting
people
to
start
to
have
the
thought
process
is
to
say
well
what
what
is
the
important
thing
here
is
it
is
it
the
tool?
Is
it
the
process?
Is
it
actually
the
structure
of
the
business.
C
A
And
also
to
to
get
people
to
understand
that
this
is
not
just
software
delivery.
This
is
you
know,
ml
assets,
and
you
know
all
the
AI
process
can
also
be
managed
in
the
same
way
and
and
what
the
what
the
risks
and
challenges
are
in
in
that
space
and,
in
fact,
in
our
next
meeting,
we'll
be
progressing.
Some
work
that
we're
doing
on
mainframes
and
continuous
delivery.
C
A
C
D
A
A
Is
the
people
try
to
adopt
continuous
delivery
at
an
engineering
level,
but
they
don't
get
buy-in
at
a
business
level
for
the
business
change,
that's
necessary
in
order
to
succeed
overall,
and
so
you
know,
you
end
up
with
people
trying
to
deliver
stuff
on
a
daily
Cadence.
But
the
commercial
sign-off
to
go
into
production
is
a
six
to
eight
week
process.
D
A
So
yeah
that
that
gets
messy
really
quickly
and
lots
of
people
get
very
angry.
D
A
That's
right
yeah,
so
so
then,
the
rest
of
this
section
really
is
more
of
the
detail
of
you
know
what
what
problems
are
you
trying
to
solve
with
this
methodology?
A
D
A
But
actually
there's
at
least
four
aspects
to
managing
your
supply
chain,
because
you've
also
got
licensing
and
how
those
licenses
flow.
Yeah
through
you
and
potentially
on
to
your
customers,
life
cycle
management
for
all
the
components
and
Regulatory
Compliance.
How
you
you're
able
to
prove
that
your
whole
supply
chain
is
compliant.
E
D
C
A
And
then
yeah,
we
look
at
things
like
configuration
management
and
how
that
falls
into
scope.
Then
one
of
the
pieces
that
we
are
looking
to
expand
now
on
is
the
assessment
of
your
current
state.
If
you
like
so
as
an
organization,
what
are
you
capable
of
doing
right
now
and
and
I?
You
know
how
do
you
know
where
you
are
on
day,
one
versus
where
you
want
to
be
so?
A
Yeah
and
then
we've
also
got
a
section
which
is
unpopulated
at
the
moment,
which
is
domain
specific
stuff.
So
this
is
where
you
you
get
into
real
Niche
application
problems.
Where
there
are,
you
know
additional
challenges.
We
we
need
to
to
flesh
out
so.
B
Yeah
I
might
be
able
to
help
with
some
of
this
I
work
closely
with
the
Dora
Team,
and
so
that
might
be
something
I
could
help
expand
on.
A
That
that
would
that
would
be
cool
and
we're
we're.
Looking
for
people
who
had
the
experience
of
you
know
high
performance,
Computing
or
you
know
large
ml
applications
where
there's
there's
a
lot
of
Niche
challenges.
You
know
where
you're
trying
to
distribute
assets
to
you,
know
very
large
numbers
of
nodes
or
trying
to
solve
problems
that
are
extremely
complex,
so
that
that's
basically
the
learn
section
then
the
other
piece
that
we're
doing
a
lot
of
work
on
right
now
is
the
the
reference
architecture.
A
So
this
is
the
idea
of
looking
at
this
from
a
very
high
level
perspective.
You
know,
how
do
you
manage
the
business
change
and
then
the
technology
change
involved
in
adopting
continuous
delivery
as
a
as
an
end-to-end
methodology?
A
Sogaf
is
it's
an
architecture
framework
and
it's
it's
typically
used
on
the
large
Enterprise
projects,
DOD
projects,
things
like
that,
where
you
you
know,
you're
gonna,
have
to
spend.
You
know
a
hundred
million
on
doing
a
business
and
technology
change,
and
you
want
to
understand
what
the
what
the
risks
Associated
are.
A
What
you've
got
right
now,
what
you
need
to
have
what
the
gaps
are
and
therefore
you
know
what
should
you
actually
be
building
but
from
a
an
architectural
perspective,
so
they're
not
not
really
a
requirements
level,
but
more
at
the
you
know.
Do
we
have
the
infrastructure
that
can
cope
with
this?
A
Do
we
have
the
resources
to
be
able
to
build
this?
Do
we
know
what
the
processes
and
behaviors
are,
so
what
that
model
model
really
brings?
Is
this
thing
called
using
viewpoints,
and
so
this
is
the
the
challenge
that,
in
on
most
large
pieces
of
work,
everyone
involved
can
only
see
a
small
part
of
the
problem
and
they
all
see
it
from
a
slightly
different
perspective.
A
You
what
you
need
to
be
able
to
do
is
say
well,
okay,
what
is
the
CEO
think?
Well,
their
Viewpoint
is
that
yeah
they're
responsible
for
scaling
the
company
they're
all
about
driving
profitability
and
and
so
they're
shaping
the
business
model,
the
target
operating
model
of
that
company
right.
A
So
what
their
view
is.
So
this
is
where
they're
standing-
and
this
is
what
they're
seeing
from
that
viewpoint.
D
A
It
is,
it
is
very
much
like
that
Persona
model,
but
what
you
can
do
with
this
is
you
can
you
you
can
be
very
clear
about
where
they're
standing
and
what
they
can
see
from
there
and
therefore
get
an
understanding
of
what
their
key
concerns
are
and
then
off
the
back
of
that
you
can.
You
can
easily
categorize
what
the
value
add
that
they
would
see
from
this
methodology.
C
A
Here,
in
order
to
get
this
individual
to
agree
to
continuous
delivery
process,
you're
going
to
have
to
show
them
two
things
that
gives
them
automated
compliance
processes
right,
make
their
life
easier
and
that
can
always
provide
them
with
an
audit
Trail
and
the
potential
for
forensic
data
management
on
everything.
That's
happened.
D
A
A
A
So
we
get
people
who
are
very
focused
on
Dora,
but
are
unaware
of
all
of
these
other
opinions
that
are
key
to
the
to
the
process.
A
So
so,
by
developing
this
this
model,
you
can
help
everyone
involved
to
understand
each
other's
viewpoints
and
what
each
individual's
concerns
are
and
then
show
how
the
methodology
addresses
all
of
the
those
concerns
in
a
way
that
benefits
everybody.
B
Right
totally
and
then
also
like
I,
don't
know
if
this
is
mentioned
anymore
but,
like
you
know,
doing
a
proof
of
concept
and
proving
the
reliability
of
a
pipeline
and
like
building
confidence
in
it
before
you
know
deciding
to
deploy
every
four
hours.
You
know
yep.
A
A
What
things
are
going
to
get
in
the
way
of
succeeding
with
that,
and
then
we
move
on
to
capabilities
are,
which
is
you
know
whatever
you
can
do
right
now?
That's
beneficial
versus
what
gaps
are
there
and
then
we
have
a
if
you
like
an
assessment
of
readiness,
so
that
you
understand
you
know,
are
you
safe
to
push
the
button
on
this
to
start
working
with
it
or
do
you
need
more
skills?
You
know:
do
you
need
more
tools,
I,
it's
all
about
building
confidence
in
adopting
and
scaling
this
methodology.
A
Now
this
this
piece,
we
we've
really
only
done
the
first
section
of
the
reference
architecture.
What
we
need
to
move
on
to
next
is
what
would
be
thought
of
as
business
architectures
and
technology
architectures.
A
And
then
Community
section
where
we
expect
to
add
in
other
projects
that
are
associated
with
this.
A
So
here
we
have
supply
chain
maturity,
metrics,
which
is
another
CDF
piece
of
work,
which
is
help
helping
people
to
understand
how
to
measure
their
maturity.
A
C
A
Whole
section
will
continue
to
add
more
more
pieces
to
over
time,
we'll
start
to
bring
some
of
the
CDF
tool
projects
into
here.
So
with
tecton
and
Jenkins
Jenkins
X
will
get
them
to
contribute
white
papers
on
your
best
practices
for
using
that
tooling
in
in
a
continuous
delivery
context.
A
Then
finally,
we
have
our
resources
section,
which
is
a
a
lot
of
sort
of
peripheral
bits
that
that
relate
to
continuous
delivery
and
I
mean
terminology
is
an
interesting
one,
because
getting
everyone
to
agree.
What
half
of
these
phrases
actually
mean.
A
It's
a
difficult
one,
because
the
the
whole
continuous
delivery
versus
continuous
deployment
I
about
50
of
people
have
the
meanings
of
those
reversed.
A
So
we
we
Define
continuous
delivery
as
the
overarching
process
of
taking
you
know
a
product
from
an
idea
to
something
that's
running
in
front
of
a
customer,
mm-hmm
and
continuous
deployment
as
the
bit
where
you
are
taking
your
tested
code,
that's
packaged
and
actually
shipping
it
into
a
production
environment.
B
Interesting
yeah
I've
seen
multiple
definitions
of
that
you
know.
Some
people
say
that
it's
like
oh
you're,
continuously,
deploying
to
a
test
environment
and
some
people
are
saying
you
know
it
describes
a
methodology
where
you're
going
directly
to
production
after
testing
and
everything
so
yeah
yeah,
definitely
a
lot
of
different
perspectives.
There.
C
C
A
So
again,
it's
all
just
little
useful
resources
to
help
people
understand
what
they
what
they
need
to
be
thinking
about,
and
then
the
other
big
CDF
project
is
see
the
events
which
is
an
abstraction
there
across
continuous
delivery.
A
Yes,
so
it's
just
a
standard
terminology
set
of
apis
for
managing
all
of
the
problems
that
occur
in
continuous
delivery
environment
and
then
a
big
effort
to
try
and
get
everyone
in
full
space
to
to
adopt
and
integrate
with
this,
so
that
you
can
use
multiple
Tools
in
a
consistent
way
to
to
manage
your
your
overall
environment.
A
It's
very
exciting
Rick,
so
so
I
hope
that
gives
you
an
overview
of.
You
know
what
what
it
is
that
we
are
actually
trying
to
achieve
here
and
you're
more
than
welcome
to
to
dive
in
anywhere
and
and
start
contributing.
A
D
A
A
You
know
we're
we're
very
open
to
contributions,
so
you
know
you'll
you'll
quickly,
pick
up
the
sort
of
style
that
we're
we're
using
and
typically
the
the
style
is
is,
is
fairly
similar
to
Google
standards
so
and
the
whole
thing
is
doxy,
so.
B
Yeah
great
Okay
cool,
so
so
yeah,
you
know,
I'll,
look
through
it
and
and
if
I
find
anything
else
fork
and
submit
pull
requests
and
then
do
people
in
this
sig
normally
join
every
meeting
like
what's
the
Cadence.
How
do
things
normally
run
here.
A
We
treat
this
as
a
fairly
offline
process
anyway,
so
you
know
you're
more
than
welcome
to
to
join
the
slack
or
to
message
me
and,
and
just
you
know,
get
involved
in
stuff
and
or
start
stuff
off.
If
you
you've
got
you,
you
think
you
specifically
want
to
contribute
and
then
the
the
meetings
are
generally
just
to
help
introduce
people
like
we've
been
doing
today
and
to
cover
off
specific
activities
where
we
we
need.
A
You
know
half
a
dozen
people
or
all
contributing
on
a
larger
piece
of
work
and
then
so
we'll
we'll
sometimes
have
little
phases
where
there'll
be
three
or
four
meetings,
where
we're
all
focused
on
getting
something
out
the
door
and
and
then
it
goes,
It
goes
back
to
being
quiet
again
like
it
is
at
the
moment.
D
B
Cool
all
right.
Well,
thank
you
so
much
for
the
tour
through
all
the
documentation.
It
really
helped
me
get
a
sense
of
the
tone
and
you
know
what
we're
aiming
for
I,
really
like
the
the
high
level
overview
of
helping
people
understand
how
to
properly
implement
this.
So
so
yeah
I
mean
I'll,
look
through
and
see
where
I
can
contribute,
maybe
with
some
Dora
stuff
and
yeah,
we'll
go
from
there.
D
A
No
we're
a
very
friendly
group,
we
don't
buy
and
you
you'll
find
that
people
come
and
go
over
time.
So
typically,
what
will
happen
is
that
some
somebody
will
come
along
and
have
a
particular
Viewpoint
that
they
think
is
missing.
So
they'll
contribute
a
lot
of
detail
on
that
viewpoint,
so
you
know
and
there's
no
requirement
that
you
tune
up
every
time.
You
know
just
drop
in
and
out
yeah
and.
D
A
A
But
there's
there's
no
sacred
chaos,
so
don't
be
afraid
to
say
you
know
what
the
hell
are.
You
thinking
putting
this
in,
because
you
know
we're
always
open
to
making
sure
that
we
got
lots
of
eyeballs
on
this
and
that
we're
getting
a
very
diverse
Stir
of
experiences
adding
into
to
this
process.
B
Okay,
great
and
then
for
meeting
notes
do
I
need
to
log
that
I
was
here
or
how.
A
Does
that
yeah?
Have
you
got
the
link
to
the
as
I
can
stick
that
in
the
chat
hang
on
a
sec.
D
D
D
B
Yeah
thanks
so
much
again,
nice
to
meet
you
and
I
should
be
around.
A
Cool
yeah,
you
too
take
care
I'll
close
to
meeting
there.
I
think
yeah.