►
From YouTube: Verify:Pipeline Insights FY24 Direction
Description
This quick video highlights the Pipeline Insights plans for FY24.
A
A
For
those
of
you
who
don't
know
me,
I
am
the
product
manager
for
the
pipeline
insights
group
here
at
gitlab,
with
fiscal
year
24
quickly
coming
here
in
the
next
day,
I
wanted
to
share
out
what
what
the
team
here
in
pipeline
insights
is
going
to
be.
Focusing
on
a
couple
of
big
things.
I
wanted
to
start
with
is
areas
that
we're
not
going
to
be
actively
continuing
support
in
a
couple
of
items
that
we
are
going
to
be
deprecating.
A
The
first
one,
which
was
announced
as
part
of
the
15-8
release,
is
the
visual
reviews
tool
now
I
want
to
clarify
this.
Is
the
visual
reviews
function?
Not
the
review
apps
function,
so
we
will
continue
to
Support
Review
apps
and,
however,
just
given
the
limited
usage
as
well
as
our
existing
feature
set,
we
are
going
to
deprecate
visual
reviews.
A
A
If
you
go
back
and
look
and
listen
to
our
Milestone
recordings
for
the
last
year,
there
is
a
lot
for
build
artifacts
moving
into
fiscal
year
24
we
are
going
to
Pivot
a
bit
of
our
focus
and
we're
going
to
start
looking
at
test
intelligence
as
as
a
category
that
we're
going
to
support
some
examples
of
this
are
fail
fast,
testing,
optimize
pipeline.
It's
not
just
about
using
machine
learning
to
make
tests
smarter.
This
is
also
about.
A
How
can
we
do
things
operationally
to
be
better
testers
and
to
use
our
time
more
efficiently
through
tests?
So
a
few
things
that
I
want
to
highlight
real
quick
is
fail,
fast
testing.
This
is
something
that
we
have
a
I'll
say
a
more
beta
version,
experimental
version
right
now
here
at
gitlab,
we
do
have
input
from
our
engineering
productivity
team,
so
one
of
our
plans
is
to
put
out
a
great
MVC
for
for
feedback,
as
I
mentioned.
A
It's
part
of
test
intelligence
is
also
about
being
smarter
about
how
we
test
so
we're
going
to
look
at
some
of
the
different
kinds
of
tests.
Think
about
some
of
the
options
in
terms
of
what
are
maybe
configurations
that
may
allow
our
developers
to
be
able
to
move
forward
faster.
One
of
the
big
things
that
we're
working
on
for
1510
is
actually
detecting
a
report
on
flaky
tests.
A
A
A
Essentially
so
you
know,
one
of
the
themes
that
we
have
heard
over
and
over
is
that
it
takes
a
bit
of
effort
to
set
up
testing
features
in
a
new
Pro
in
a
new
project,
and
so
one
of
the
things
that
we
are
going
to
focus
on
is
how
do
we
make
this
more
user
friendly
and
quick
quick
to
test?
So
that's
all
I
had
to
share
today
looking
forward
to
an
exciting
fy24
thanks.