►
From YouTube: GitLab 14.1 Kickoff - Verify:Testing
Description
Kickoff Page: https://about.gitlab.com/direction/kickoff/#verify
Ops Direction: https://about.gitlab.com/direction/ops/#verify
Issues discussed:
* https://gitlab.com/gitlab-org/gitlab/-/issues/329547
* https://gitlab.com/gitlab-org/gitlab/-/issues/331163
* https://gitlab.com/gitlab-org/gitlab/-/issues/238535
We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl
A
Hi,
I'm
jake
timbak
the
product
manager
for
the
testing
group
and
the
verify
stage
of
github.
Today,
I'm
going
to
be
previewing
the
work
the
team
is
going
to
be
doing.
The
upcoming
14-1
milestone
you'll,
find
a
link
to
the
14.1
kickoff
page
and
links
to
these
items
in
the
verify
stage
direction
page
with
discussion
of
our
future
work
in
the
comments
below
the
video.
You
can
always
reach
me
at
jhinebucketgitlab.com
or
through
comments
on
these
issues
or
anything
with
the
group
testing
label
in
the
gitlab
project.
A
So
today,
I'm
already
sharing
our
14-1
planning
issue
and
our
theme
in
the
14-1
milestone.
We're
really
focused
in
on
a
couple
of
issues
around
reliability
and
usability,
and
I'm
going
to
speak
to
kind
of
our
top
three
issues
here.
The
first
one
is
an
nbc
is
really
a
proof
of
concept
around
getting
a
code,
quality
scan
and
results
into
all
of
the
code
quality
feature
set
without
utilizing
the
code,
climate
scanner,
which
requires
docker
and
docker.
A
This
is
going
to
let
a
lot
more
users
or
show
users
how
to
make
use
of
all
of
those
code.
Quality
features
without
relying
on
the
code
climate
engine
that
runs
under
the
covers
and
is
great
to
use
out
of
the
box
and
as
part
of
auto
devops,
but
some
folks
just
can't
use
that
docker
and
docker
capability
for
themselves.
So
this
is
a
perfect
concept
that
we're
going
to
do
with
the
gitlab
project,
looking
at
ruby
and
javascript
linters
and
scanners,
and
translating
that
data
into
a
report
that
our
feature
set
can
use.
A
So
that's
kind
of
a
proof
of
concept
for
other
folks,
so
they
can
take
it
and
run
with
it
and
make
use
of
those
features.
The
second
issue
that
we're
going
to
be
focused
on
is
reviewing
our
existing
dashboard
or
around
our
error
budget.
It's
been
looking
really
good
lately,
but
the
team
has
not
really
done
a
deep
dive
into
this
to
ensure
that
all
of
the
services
that
we
manage
are
included.
A
So
this
is
going
to
help
us
ensure
that
we're
keeping
the
right
level
of
focus
on
reliability
and
usability,
balancing
that
with
feature
work,
going
forward
to
ensure
that
we
have
a
great
service
that
everyone
is
able
to
use,
and
the
last
feature
here
is
enabling
a
feature
flag.
This
is
a
step
towards
resolving
some
of
the
issues
that
you
see
in
the
way
that
build
artifacts
pipeline
and
job
artifacts
both
are
being
incorrectly
calculated.