►
From YouTube: Best Practices SIG - May 3, 2023
Description
For more Continuous Delivery Foundation content, check out our blog: https://cd.foundation/blog/
B
Been
offline
for
a
while,
my
my
dad
got
coveted
and
got
really
sick
and
then
looked
like
he
might
be
getting
better
and
then
went
downhill.
So
he
passed
away
a
couple
weeks
ago,
I'm.
B
It's
it's
frustrating,
you
know
because
didn't
want
to
get
a
vaccine
didn't
wear
masks
had
numerous
high-risk
health
issues.
B
B
All
right,
the
dogs
are
being
annoying
as
usual
or
was
I.
Oh
I
took
our
little
RV
down
and
you
know
it's
California,
which
is
like
three
times
the
size
of
the
UK.
B
You
know
it
basically
turned
into
a
long
road
trip
where
I
had
lots
of
sort
of
just
quiet
driving
time
and
and
then,
when
I
got
back,
then
you
know
I
was
helping
his
wife
with
Logistics
and
then
neither
of
them
were
very
technical
and
they
had
these
ancient
iPhone
se's,
with
lots
of
pictures
that
had
never
been
backed
up.
B
So
you
know,
I
was
trying
to
figure
out
how
to
get
the
pictures
offline
and
anyway,
and
then,
when
I
got
home,
I
decided
that
my
path
to
emotional
well-being
being
was
should
be
through
hard.
Labor
I
wanted
to
do
something
productive,
so
I
hauled
about
I,
don't
know
three
thousand
pounds
worth
of
rocks
from
my
backyard
and
the
landscaped
and
built
new
veggie
boxes
with
my
daughter
and
and
then
my
body
was
like
you're
in
your
50s,
you
so
now,
I'm
in
pain,.
A
Yeah
I'm
well,
as
you
can
probably
see,
I,
had
an
interaction
with
a
cat
recently.
A
B
Oh
man
I,
you
know
I
I
noticed
so
I
I.
Would
you
know,
try
to
wear
gloves
as
much
as
possible,
but
if
you
know
I
don't
like
wearing
gloves
around
the
chop
saw
for
for
obvious
reasons
and
then
I
would
forget
to
put
them
back
on
and
then
I
would
like
get
a
little
Nick
and
I've
noticed
they
take
a
lot
longer
to
heal
than
they
used
to
and
they
happen
much
much
more
readily
than
they
used
to.
B
So
my
hands
are
all
ripped
to
pieces.
Yeah
this
whole
getting
older
thing,
I'm,
not
a
fan.
B
Yeah
there
you
go
so
I
saw,
there
was
oops
hang
on
a
second,
oh,
hey,
GitHub
logged
me
out
so
I'm
trying
to
get
back
in
here
so
I
saw.
There
was
further
discussion
about
the
Mainframe
document.
Did
did
a
document
actually
get
started?
I
didn't
read
the
whole
thing
yet.
A
So
so
there
is
a
there
is
a
document,
but
at
the
moment
it's
it's
a
very
general
discussion
about
sort
of
their
box
and
processes
in
general,
so
it's
not
currently
feeding
into
what
we
would
need
to
to
put
something
on
the
site,
but
I
think
it's
it's
a
good
place
to
start
the
conversation.
A
What
really
needs
to
happen
is
needs
to
identify.
What
are
the
exceptions
that
are
special
for
the.
B
A
Scenario,
though,
where
you
know
what
what
difference
is
do
there
need
to
be
for
for,
for
that
particular
application
and
I
think
I
think
it's
about
much.
Actually,
there
are
there
are
some
physical
constraints
and
probably
it's
more
of
a
challenge
in
the
tooling
space,
simply
because
a
lot
of
the
standard
tools
won't
account
for
the
fact
that
you
need
to
be
doing
your
compilation
on
a
different
platform.
B
Great
right-
and
you
know
it's
funny-
I,
don't
know
if
I
was
telling
you
this
or
Fati.
You
know
I'm
I'm
I'm
now
at
a
company
that
does
builds
for
mainframes
I
was
like
and
I
had
no
idea.
That
was
still
a
thing
that
people
were
still
and
then
I
was
like.
Of
course
it
is
right.
You
know,
I
mean,
like
the
whole
coveted
thing,
at
least
in
the
U.S.
B
B
Why
on
Earth,
would
we
would
we
would
we
change
that?
Oh
man,
all
right
am
I,
actually
editing
here.
B
B
A
It
comes
out
you're.
B
A
Was
two
weeks
ago,
yeah.
B
That
was
apologies,
I
I
was
I
meant
to
to
drop
a
note
to
say
in
the
channel
and
I.
Just
I
was
in
the
midst
of
all
of
my
family
chaos.
B
A
B
B
A
A
A
I'm?
Assuming
that
it's
a
fairly
closed
shop
in,
in
which
case
it
would
be
a
matter
of
persuading
the
vendors
to
include
the
the
events
apis
and
and
then
allow
external
systems
to
invoke
those
to
trigger
the
build
process.
B
Yeah
I
dropped
a
note
and
there's
kind
of
a
reminder
for
myself,
because
if
I
type
it
or
right,
it
helps
me
remember
better,
but
I'm
I'm
thinking
like
as
the
as
the
principal
Mainframe
vendor
I
I,
have
become
recently
become
aware,
as
we
are
producing
software,
that
one
could
run
on
them.
B
Ibm
in
in
our
in
our
interactions
comes
across
as
really
wanting
to
prove
the
legitimacy
of
the
platform
on
a
routine
basis
like
they
and
what
I
mean
by
that
is
they've
got
this
whole
thing,
for
example,
for
oeming
software
and
what
the
requirements
are
for
having
your
software
be
part
of
their
OEM
ecosystem,
which
has
got
some
pretty
like
well
considered
and
aggressively
a
aggressive
requirements
that
they're
trying
to
drive
around
like
start
curious
software
supply
chain
like
they
talk
a
lot
about.
B
You
know
the
the
sorts
of
things
that
that
we
that
we
would
consider
a
best
practice,
or
at
least
in
the
vein
of
that
I,
should
see
if
that,
if
that
document
that
I
was
looking
at
is
actually
a
public
document,
because
if
it
is
I'll
share
it
with
you,
because
it
was
kind
of
interesting
I
was
surprised,
maybe
I
shouldn't
be.
Maybe
they
pulled
some
red
hat
people
over
I.
Don't
know,
okay,
well,.
A
B
A
very
good
point,
yes,
is
that
that
might
be
an
excellent
thing
to
reference
in
this
document.
A
Of
us
can
it's
probably
also
worth
thinking
about
the
the
bigger
picture,
because
typically
the
Mainframe
doesn't
sit
in
isolation.
If
you're
developing
an
application,
then
the
Mainframe
is
just
one
component
of
of
that.
You
know
so.
You're
the
UI
stuff
is
typically
sitting
on
other
platforms,
so
you
may
have
several
technology
layers
before
you
get
down
to
the
to
the
Mainframe
component
of
the
solution.
A
B
B
It
will
never
pass
requirements.
I
have
no
way.
I
have
no
way
of
building
a
legit
community
around
it.
It
is
so
specialized
for
what
it's
good,
for
it
really
is
not
a
a
generic
solution
at
all
and
there's.
There
would
be
no
reason
to
make
it
so
so
I
was
like
oh
well,
it
was
worth
the
thought
if
I
did
finally
kind
of
sit
down
and
go
through
like
reviewing
how
we've
approached
some
of
the
different
project.
Onboardings
I'm,
like
it's
just
not
going
to
happen.
A
Yeah,
oh
well,
I
think
we're
in
the
awkward
time
at
the
moment
where
you
know
we
can
see
that
there's
a
desperate
need
for
more
overarching
end-to-end
systems,
but
the
the
investment
and
the
effort
is
all
sitting.
You
know
down
in
narrow
niches,
yes
very
hard
to
to
get
enough
work
going
on
at
a
more
generic
level,
getting
people
to
agree
to
collaborate
and
span
different
domains.
B
Or,
and
and
right
this
is
not
a
full-fledged
thought.
It's
just
been
kind
of
tickling
in
the
back
of
my
head,
as
we've
been
talking
like.
So
one
of
the
things
that
we've
been
doing
is
a
lot
of
instrumentation
work
using
open,
telemetry
framework
right
into
Evergreen,
and
then
we're
that
was
kind
of
the
proof
of
concept
and
for
Evergreen
itself.
It's
like!
Oh,
okay!
Well,
here's
this!
You
know
distributed
systems
tooling,
that
that
manages
an
amazing
amount
of
volume
and
we're
already
starting
to
see
some.
B
You
know
some
lightweight
benefits
on
on
having
this
type
of
instrumentation,
but
what
we
really
want
to
do
is
get
it
to
the
point
where
we
have
a
standard
for
how
our
product
teams
are
developing
our
instrumenting
the
tests
themselves
right.
So
then
we
can
see
through
the
open,
Telemetry
spans.
Okay.
Well,
here
the
Evergreen
task
kicked
off
and
it
did
a
bunch
of
stuff
and
oh
look.
You
know
that
one
waited
far
longer
than
it
should
have
for
that
particular
resource.
B
Whatever
we'll
look
at
that,
but
then
now
it
you
can
follow
it
all
the
way
down
into
the
subprocesses,
which
are
the
actual,
build
test
execution
and
we're
figuring
out
a
way
to
to
be
able
to
say,
okay,
you
know,
query
Evergreen
metadata,
because
there's
an
agent
on
each
resource
that
gets
spun
up.
That
will
tell
you
what
the
context
the
trace
context
is,
so
you
can
pass
it
through
your
tests,
even
if
the
tests
themselves
are
subsequently
distributed
to
other
resources.
So
we
get
this.
B
B
Concepts
like
that,
it's
like.
What's
the
threshold
of
context
like
an
Hotel
Trace
object
or
a
CD
event
or
right
like
what
are
those
anchor
points
that
with
a
sufficient
number
of
those,
it's
not
about
an
individual
project
implementation?
It's
about
now
it's
about
like
integration,
best
best
practices,
or
you
know
what
I
mean
I'm
I'm
struggling
with
this
idea
to
articulate
it,
but
it
kind
of
makes
sense
where
I'm
going
with
that.
A
B
We
have
enough
or
what
would
be
what's
the
missing
thing
right.
Is
it
like
see?
The
events
is
coming
along
hotel?
Is
there
testing
I
mean
you
know
this?
That's
really
kind
of
a
framework
thing,
rather
than
anything
you
can
anchor
on
like
if
you're
Java,
your
junit
or,
if
you're
python,
your
Pi
test
whatever.
But
what's
you
know,
but
maybe,
if
there's
one
more
thing
that
we
could
get
those
projects
to
pull
into
their
Frameworks
that
opens
up.
B
A
A
How
do
you
get
a
technology
stack
and
a
delivery
process
which
is
best
practices
compliant
but
which
you
know
Works
in
an
opinionated
way
out
of
the
box,
so
you
don't
need
to
already
have
a
complete
team
of
experts
who
are
all
in
agreement
over
how
this
stuff
should
work.
A
You
just
you
just
yeah
click
a
button
and
you
get
a
default
set
up,
and
then
you
just
extend
that
to
make
it
do
what
you
need
and
unless
it's
you
know,
really
been
brought
home
to
me
recently,
because,
obviously,
over
the
past
few
years,
I've
been
happily
playing
in
the
you
know
the
Jenkins
X
the
kubernet
in
space
and
got
used
to
what
you
can
achieve
when,
when
you're
at
that
level
of
granularity,
but
recently
I've
gone
back
to
you're.
A
Looking
at
you
know,
what's
the
default
offering
from
one
of
the
major
Cloud
vendors,
what's
the
entry
level
distributed
Services
solution
that
the
average
customer
is
going
to
report
to
if
they
come
to
a
major
Cloud
vendor
and
it
doesn't
work.
A
It's
broken
and
I
I
have
been
using
this
stuff
for
a
few
weeks
now
and
there
are
just
absolutely
gaping
issues
like
the
system
provides
Quick
Start
who
are
setting
up
new
project,
but
what
they
actually
generate
is
code,
that
is
two
to
three
years
at
a
day:
stuffed
full
of
deprecated,
libraries
and
thousands
of
cve,
and
if
you
set
one
up
I'm
trying
to
run
it
one
execute,
so
you
actually
have
to
do
software
archeology
on
the
Quick
Start
to
work
out
how
you're
supposed
to
use
the
platform
now-
and
you
know
that
that
always
strikes
me
as
being
you
know,
a
really
bad
sign.
A
If
you'd
be
any
people
who
can
use
your
platform
for
people
who
are
already
fluent
experts,
then
you
know
you,
you
really
got
a
problem
because
you,
you
can't
expand
your
Market
any
further.
B
Oh,
my
God,
so
you
know,
I
I
haven't
tried
the
AWS
Solutions,
but
I've
anecdotally,
I've
heard
it's
it's.
It
sounds
like
it's
pretty
much
the
same
thing.
What
you're
saying
on
all
three
of
the
big
cloud
platforms:
they're,
really
not
interested
in
selling
that
level
of
solution.
B
They
just
want
to
sell
compute
resources
or
storage
right,
and
you
know
I
I
can't
I
can't
even
tell
you
the
number
of
times
I
had
I
had
it
out,
but
you
know
to
have
these
really
intense
conversations
is
like
you
can't
compare
Cloud
build,
for
example,
with
Jenkins
or
any
other
solution,
because,
yes,
if
you
set
it
up
to
do,
if
you
do
all
the
work
to
set
it
up
it
can
it
can
be
a
very
highly
efficient
way
of
of
especially
if
you're,
using
containers
a
highly
efficient
way
of
spinning
up
a
whole
bunch
of
resources
to
do
a
bunch
of
stuff
and
then
spin
it
back
down
for
you
right.
B
But
that's
exactly
your
point.
You,
the
com,
the
customer
would
have
to
do
all
of
the
work
to
figure
out
what
those
tasks
are.
Nothing
comes
for
free.
The
only
thing
that
you
would
would
get
for
free,
which
was
good,
but
it
was
only
the
one
piece-
is
that
if
you,
if
what
you
produced,
was
a
container-
and
you
put
it
into
our
artifact
registry-
we'd
automatically
scan
it
for
you.
B
Well,
how
nice
of
us
right
like
really
that's
it
yeah
and
and
I
found
it,
and
people
were
so
disparaging
of
Jenkins
as
being
a
20
year
old,
too,
and
I'm
like
yeah.
What
people
have
already
done?
The
work
like
the
Jenkins
plug-in
ecosystem
is
both
the
most
awesome
and
the
most
wretched
place
on
Earth
awesome,
because
everybody
has
figured
out
something
and
wretched,
because
it's
not
being
maintained
and
it's
a
disaster
right,
but
that's
I
you're,
you
are
so
right.
B
It's
not
worth.
Nobody
has
figured
out
how
to
make
it
worth
the
business
investment
to
actually
solve
that
problem,
for
real
and
and
and
I
completely
agree,
and
this
is
why
I
came
back
to
well.
You
know:
is
there
a
middle
ground
right
and
the
Jenkins
plug-in
ecosystem
is?
Is
a
bunch
of
very
s?
It's
it's
at
the
level
of
granularity.
Where
it
is
it's
easier
right,
it's
like
oh
I
need
to
be
able
to
hook
up
these
two
things
and
and
I
want
to
I
want
to
be
able
to
see.
B
You
know
a
nice
little
UI
element
when
it's
done,
and
here
are
the
the
goofy
icons
that
I'm
gonna
add
you
know,
have
it
produce?
Okay?
So
if
you
want,
if
you
do
that,
one
thing
you
know,
Chuck
Norris
will
come
up
and
give
you
a
thumbs
up
and
you
move
on
with
to
the
next
thing
right,
but
that's
too
low
a
level
of
granularity
right.
That's
why
it
never
got
past
the
plug-in
ecosystem.
So
what's
what's
the
middle
ground
right
and
that's
when
I
I
came
to
the
whole?
B
Like
everybody,
you
see
the
events,
everybody
use,
otel,
Trace
events,
everybody
use
because
then,
instead
of
having
like
the
box
of
Legos,
that's
just
the
box
of
Legos.
Maybe
then
we
have
like
the
kits
right,
so
the
level
of
customization
is
is
more
truly
building
block
like
oh
I
need
to
be
able
to
do
this
type
of
thing.
B
All
right
all
right,
there's
a
tool
and
all
I
have
to
do-
is
put
this
Trace,
ID
or
whatever,
and
all
of
a
sudden
I
can
I
can
do
these
types
of
things
right,
but
yeah
I,
don't
know
how
to
articulate
that
very
well.
B
How
are
things
going
in
CD
events?
Is
there
like?
Are
you
still
lurking
around
in
there
and
doing
things
I.
B
Yeah
I
keep
we
I
was
talking
about
that
idea
and
I
sent
a
bunch
of
my
Engineers
off
to
read
the
specs
but
they're,
not
quite
in
the
headspace
I.
Think.
A
lot
of
my
Engineers
have
never
worked
anywhere
other
than
mongodb.
B
Oh
yeah,
all
right,
I
think
I
have
now
that
I'm
sort
of
lifting
my
head
back
up
from
catching
up
for
being
out
for
a
couple
weeks
and
having
all
the
email
and
slack
threads
I've
had
to
read
up
on
I.
Think
I
still
have
some
outstanding
PRS
I'll
try
and
get
those
done
by
the
end
of
the
week.
Just
clean
up
I
know
the
translation
stuff
had
some
tweaks
that
needed
unless
Fati
took
care
of
it.
I
said.
Is
there
anything
else?
A
I
think
we
have
we're
sort
of
a
little
bit
in
limbo
at
the
moment,
so.
A
Yeah,
well,
we
we!
What
we
need
to
do
really
is
probably
sit
down
and
work
out
what
we're
going
to
do
later
in
the
year
and
what
we
want
to
try
and
get
achieved,
and
then
he'll
run
around
and
start
chasing
people
up
again,
because
we
got
we
got
so
far
with
that
reference
architecture
and
then
that's
kind
of
stalled
out,
because
we
didn't
manage
to
get
any
additional
contributions
in
the
in
the
right
spaces,
so
yeah.
But
we
need
to
put
some
energy
back
into
again.
B
Okay,
all
right!
Well,
if
you
don't
mind,
I
need
some
coffee.
Unless
you
have
another
topic
you
wanted
to
touch
on,
then
maybe
I
could
use
the.