►
From YouTube: Keptn Refinement Meeting - Apr 11, 2023
Description
Meeting notes: https://docs.google.com/document/d/10Fig1eYFZ9iQFSYWkz0c4eTwzgJiPtQI5IsczbvLsuE/edit
Learn more: https://keptn.sh
Get started with tutorials: https://tutorials.keptn.sh
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/keptn
Follow us on Twitter: https://twitter.com/keptnProject
Sign up to our newsletter: https://bit.ly/KeptnNews
A
Welcome
everyone
again,
please
add
yourself
to
the
list
of
attendees
here
at
least
I
shared
this
link
again,
I,
don't
know
if
everyone
had
already
access
to
it
so
for
today
we
have
so
far
a
single
issue
to
discuss
this
exposed.
Captain
metric
integration
test
that
Works
only
one
time.
Moritz
do
you
have
anything
to
add.
Besides,
you
cannot
run
multiple
times
locally.
B
C
Yeah
I
was
wondering
because
now
this
is
easily
fixable,
but
it's
not
a
given
that
it
will
always
be
the
case.
So
I
was
wondering
whether
we
should
use
the
test
suit
default,
which
we
would
be
setting
up
the
cluster
with
the
test
and
tearing
it
down.
C
D
I
would
say,
the
the,
including
the
setup
of
the
cluster,
is
a
good
idea
as
long
as
it
stays
optional,
because
sometimes
it's
also
preferable
to
yeah
run
the
tests
on
some
state
of
the
cluster.
You
currently
have
when
working
on
a
new
feature,
and
then
it
might
be
a
little
bit
too
much
overhead
to
to
recreate
the
cluster
on
each
run.
D
C
B
I,
don't
know
doesn't
mean
that
we
also
need
to
build
and
deploy
QT
every
time
right.