►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
First
off,
let's
start
with
the
real
app
deployment,
a
success
rate
and
good
lab
for
to
get
back
projects
I'm
happy
to
say
that
we
have
attained
90%
success
rate
for
the
month
of
April,
and
this
is
due
to
us
being
improving
defensive
measures
and
deployments.
We're
not
only
deploying
relapse,
forefront
and
related
changes.
We're
relapse
are
useful.
We
have
improved
clean
up
policies
in
GCP
as
well.
A
A
The
the
challenges
here
is:
the
team
has
been.
The
team
has
shifted,
focus
made
by
Ekta
focus
on
costs
in
their
situation,
so
we
have
a
lot
of
improvements
on
costs
of
inactivation.
We
will
continue
to
take
on
a
kr
into
two
to
lower
this
further.
We
have
identified
four
main
pipeline
top
types
that
we
will
have
more
detailed
metrics
for
each
type
to
track
and
also
working
on
really
reducing
the
test
environment
set
up
in
in
each
in
the
pipeline's.
A
A
It's
down
to
two
point:
88
to
point
$88,
and
the
improvement
here
is
attributed
to
using
interruptible
seen
on
pipelines
is
where
we
cancel
pipelines
where
a
new
push
has
been
made,
so
those
pipelines
to
consider
sale
and
we
are
taking
on
a
kr
in
q2
as
well
to
take
this
even
lower
tu-tu-tu-tu-tu
dollars.
The
current
target
long-term
target
has
been
cursed,
as
we
said
at
one
point:
$25,
let's
back
up
a
little
bit,
so
we
have
a
KPI
for
our
handbook,
update
frequency.
We
need
to
improve
here.
A
A
We
aim
to
finish
this
at
100
percent,
but
beyond
this
quarter,
as
I
said
before,
we
were
not
able
to
complete
our
our
target
of
our
goal
of
45
minutes
or
the
average
motionless
pipeline
duration.
This
quarter
and
curlies
at
62
minutes
anticipated.
We
will
be
facing
a
quarter
with
with
this.
This
number
will
take
on
a
kr
in
future
for
this,
the
engineering
productivity,
okay,
our
team,
their
tracking
progress
at
70%
for
their
team
oak.
A
We
are,
and
they've
been
working
on
both
the
duration
and
also
decreasing
decreasing
duration
and
improving
the
stability
of
our
pipelines.
Moving
back
to
ok,
ours.
The
second
one
is
our,
is
Ethiopia
we're
tracking
at
75%,
and
we
have
rolled
out
an
internal
on-call
rotation
process
to
ensure
that
pipelines
are
charged
in
a
timely
manner.
It's
an
on-call
rotation
to
ensure
that
our
internal
infrastructure,
all
test
pipelines
and
test
infrastructure
is
stable.
A
D
Nayland
QA
team
has
completed
their
Oakley
arm
for
this
quarter.
Congratulations.
The
team
has
delivered
our
first
iteration
our
cloud
native
reference
architecture
using
kubernetes.
This
is
based
off
the
50k
reference
architecture.
They've
also
produce
a
dubious
equivalence
of
all
our
reference,
architectures
and
also
close.
The
opponent's
escape
the
Deaf
Curie
team.
A
Are
there
tracking
at
89%
we
have
made
progress
on
having
a
reliable
test
suite
to
God
every
deploys,
we're
still
working
on
the
historical
reliability
of
our
tests,
I'm,
hoping
that
we
can
make
some
progress
here
before
we
close
out
the
border
going
back
to
okay,
ours.
The
last
care
is
our
team.
Okay.
Are
we
have
hard
to
plan,
however,
we're
not
able
to
complete
the
career
metrics
or
for
the
department
we'll
be
taking
on
a
q2?
A
We
are
to
complete
this
and
ensure
that
our
team
members
have
appropriate
career
growth
conversations
and
then
tracking
all
the
facets
of
their
other
work
streams
and
work
responsibilities,
and
that
concludes
our
highlight
for
the
engineering
key
review.
I
hope
that
everybody
have
a
good
day
or
good
night
wherever
you
are.
Thank
you.