►
From YouTube: 12.3 Release Kickoff: Verify
Description
Kickoff Document: https://docs.google.com/document/d/1ElPkZ90A8ey_iOkTvUs_ByMlwKK6NAB2VOK5835wYK0/edit
Verify Strategy: https://about.gitlab.com/direction/verify
A
Hey
everyone:
my
name
is
Jason
money
and
I'm.
The
product
manager
for
CI
CD,
here
at
gitlab
and
today,
I'm
gonna,
take
us
through
the
verify
features
a
the
upcoming
12
day,
release
which
will
be
coming
out
on
the
22nd
of
this
month.
So
first
up
is
filters
for
pipelines
and
what
this
feature
introduces
is
on
the
pipeline's
page.
It'll
now
allow
you
to
filter
by
a
number
of
different
options.
So
you
can
see
what
that
is
going
to
look
like
here.
A
Well,
we
won't
be
using
Comic
Sans,
but
we
will
that's
a
promise,
but
we
will
allow
you
to
select
Branch
tag,
commit
out
there,
things
like
that
and
do
a
search
base
and
learn
to
what
you
do
with
issues
today
in
order
to
find
the
pipelines
that
you
are
interested
in.
We
know
this
page
can
be
very
busy
and
a
large
instance.
There
can
be
many
many
pipelines
that
are
available
here,
and
this
will
help
you
get
to
what
you're
looking
for
easier.
A
Next
up
is
making
it
easier
to
install
the
group
runner
on
kubernetes,
so
we're
not
really
adding
any
new
functionality
with
this
feature,
because
it's
already
possible
to
automatic
or
to
install
a
group
runner
in
communities,
but
we're
making
it
much
much
easier
by
having
a
single
button
here.
That
will
let
you
do
that
in
a
very,
very
easy
fashion.
So
we
hope
that
this
will
make
it
a
little
bit
easier
to
find
for
people
and
a
little
bit
easier
to
use
merging
stages
across
includes.
A
A
If
you're,
a
user
of
our
merge,
request,
pipelines
feature
you
know,
you
can
get
a
lot
of
value
out
of
being
able
to
turn
on
and
off
jobs
depending
on
whether
it's
in
the
context
of
a
merge
request
or,
more
importantly-
and
it's
actually
run
the
pipeline
in
the
context
of
rumored
requests
so
that
the
merge
result
is
available.
So
the
source
plus
the
target
branch,
is
built
together,
as
if
you'd
already
done
the
merge
and
then
it's
tested
in
the
pipeline.
A
But
one
thing
that
was
missing:
there
was
the
ability
to
request
a
new
one
of
those,
so
you
could
run
the
pipeline
when
you
made
it
commit,
but
you
couldn't
from
the
original
question
so
say:
I
want
to
run
another
pipeline
in
the
context
of
the
merge
request
with
this
MRR
we're
adding
that
feature,
so
that
will
now
be
a
lot
easier
to
use.
If
you
have
that
use
case
and
then
finally,
adding
merge
request
links
to
the
pipeline
view.
A
A
If
you
end
up
end
up
on
a
pipeline
page,
there's
something
I'm
personally,
really
looking
forward
to
like
some
o
from
bouncing
around
from
pipeline
page
to
merge,
request
and
so
on,
and
this
will
just
make
that
so
much
easier
and
that's
it
for
the
verified
release
in
our
upcoming
12
over
the
verify
stage
and
our
upcoming
12.3
release.
If
you
have
any
questions
or
thoughts
on
any
of
these
items,
we
would
love
for
you
to
jump
in
to
the
conversation
these
issues.
A
If
you
don't
feel
comfortable
doing
that,
you
can
also
reach
out
to
me
directly.
I'm
on
twitter,
my
handle
is
at
j
for
llen
or
my
email
address
is
Jason
at
kelabra
gitlab
comm
anyway,
love
to
hear
from
you
I
hope.
There
was
some
features
in
here
that
you're
excited
for
and
looking
forward
to
delivering
them
to.
You
thanks.