►
From YouTube: GitLab 16.5 Kickoff - Verify:Pipeline Execution
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
Welcome
to
the
16.5
kickoff,
my
name
is
Jackie
Porter
and
I'm
the
product
manager
over
pipeline
execution
Group,
which
covers
merge
trains,
continuous
integration
and
several
other
key
areas
for
making
CI
lovable
within
gitlab
in
16.5.
The
team
will
be
focusing
mostly
on
our
usability
Benchmark
issues
with
a
Keen
Eye
toward
merge
trains
as
well
as
enhancing
when
pipelines
can
be
canceled.
A
So
first
up
the
feature
that
we're
going
to
be
tackling
addresses
a
functionality
Gap
where,
if
an
MR
does
not
contain
a
pipeline,
it
cannot
be
merged.
When
Auto
merge
is
enabled
in
the
project
settings
we're
looking
to
adjust
the
default
Behavior
to
make
the
experience
more
consistent
with
how
users
expect
emerge
to
happen
when
no
pipeline
is
present,
Next
Step
we're
going
to
be
addressing
some
unexpected
Edge
Paces
or
bugs
that
that
also
happen
with
Birch
trains.
A
So
in
this
particular
issue,
merge
trains
can
be
merged,
even
if
they're
blocked
by
a
particular
pipeline
status,
which
really
defeats
the
whole
purpose
of
setting
Auto
merge
based
on
successful
pipelines.
So
addressing
this
will
help
again
Drive
consistency
in
using
merge
trains
or
merge
request
pipelines
with
gitlab
and
in
this
other
issue,
when
a
merge
request
is,
is
enabled
or
fails
with
a
merge
train.
It
is.
It
has
a
non-regible
status,
even
though
a
pipeline
might
be
succeeding
on
retry.
A
This
is
an
intermittent
issue
and
we
do
suspect
that
there
may
be
some
tuning
in
the
merge
ability
checks
to
address
it.
So
we're
excited
to
fix
this
issue
because
it's
definitely
a
pain
point
for
some
of
our
our
customers
and
users
of
merge
trains
and
then,
finally,
in
this
particular
issue,
we
want
to
make
sure
when
a
manual
action
needs
to
be
taken
on
a
merge
train,
that
it
is
clear
from
the
merge
button
and
the
merge
request
widget
that
a
particular
action
needs
to
happen.
A
So
in
this
proposal
we'll
be
updating
the
button
text
so
that
you
know
a
merge,
train
needs
to
be
started
or
added
dependent
on
that
change
and
then,
lastly,
for
our
Advanced
security
and
compliance
use
cases
there's
some
instances
that
would
like
to
prevent
all
levels
of
access
from
being
able
to
cancel
pipelines.
So
we'll
be
adding
a
setting
that
supports
this
functionality
by
disallowing
pipeline
cancellations
in
gitlab
super
excited
for
16.5.