►
From YouTube: Verify Stage Direction
Description
Welcome to the Verify Stage Direction Overview!
https://about.gitlab.com/direction/verify/verify/#overview
A
Earlier
this
year,
one
of
the
teams
in
the
op
section
established
a
product
direction
for
the
combined
vision
of
release
and
configure
to
satisfy
the
market
use
case
for
users
and
customers
deploying
their
application
with
gitlab.
This
page
provides
a
consolidated
view
into
the
strategy,
one
year
direction
and
jobs
to
be
done
for
this
product
vision.
This
page
is
a
great
forward-looking
asset
that
really
helps
to
transparently
convey
the
themes
and
purposes
of
these
individual
stages
in
context
to
what
the
market
landscape
needs.
A
This
layout
and
overall
page
has
created
an
inspiration
for
the
verify
stage,
thus
was
born
the
verify
stage
direction,
as
mentioned
earlier.
Our
purpose
is
to
satisfy
and
drive
innovation
in
the
market
in
regards
to
building
and
testing
code.
Some
of
the
core
aspects
of
this
direction
page
include
a
stated
mission
and
vision,
as
well
as
the
one-year
direction,
with
some
details
around
swat
and
competitive
landscape
analysis.
A
A
We
need
to
be
sure
that
we
also
manage
our
bugs
and
technical
debt
along
the
way
to
use
data
that
informs
our
areas
of
growth.
So
these
experiences
are
not
only
fruitful
for
developers
but
enterprise
organizations
without
focusing
too
much
on
enterprise
development
exclusively
as
we
look
forward
beyond
the
swot
analysis.
A
Some
of
the
core
competencies
in
our
ci
capabilities
needs
to
be
us,
making
it
as
easy
as
possible
to
automate
the
building
testing
pipeline
configuration
with
compliance
and
security
at
the
forefront.
We
also
need
to
empower
users
with
our
data,
so
they
can
make
informed
decisions
about
ci
performance
and
cicd
minute
consumption.
A
We're
also
looking
to
empower
an
ops
for
all
by
leveraging
that
data
asset
for
ci
performance
and
secure
supply
chain
workflows.
We
want
to
also
drive
speedy
and
reliable
pipelines.
So
that
people
are
as
efficient
as
possible
while
using
gitlab
and
lastly,
we
want
to
support
the
getlab.com
increasing
base
by
prioritizing
our
get
lab,
hosted
first
scaling
experience
as
we
start
to
apply
this
mission
and
vision.
We've
created
one
direction
across
all
the
product
groups
in
verify
that
will
help
us
accomplish
some
of
the
most
critical
jobs
to
be
done.
A
This
includes
the
pipeline
authoring
experience
which
will
help
our
users
increase
efficiency
in
their
organizations
and
authoring
pipelines.
Merge
trains,
build
artifacts,
review,
apps
and
code
testing.
Are
categories
we'll
invest
in
in
the
coming
year
to
help
you
implement
cicd
practices
across
your
organization,
as
well
as
reviewing
test
data.
A
Continuous
integration
and
runner
enterprise
management
categories
will
help
our
users
unlock
data
to
identify
trends
and
perform
administrative
tasks
efficiently,
and
we
have
a
handful
of
teams
that
are
thinking
about
scale
which
are
runner
cloud
and
ci
scaling.
These
are
going
to
empower
our
git
lab
tomcom
users
to
accomplish
cicd
adoption
within
their
organizations
easy
and
effortlessly.
A
We
also
have
a
few
things
that
we're
not
working
on
in
the
coming
year.
One
of
those
is
the
jenkins
importer
experience.
Well,
jenkins
is
a
part
of
our
competitive
landscape.
In
this
coming
year,
we
really
need
to
prioritize
other
features
like
scaling
and
combat
against
github
actions
as
our
major
competitive
threat.