►
From YouTube: GitLab 16.0 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.0
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
categories
for
making
sea
ice.
Lovable
Within
gitlab
in
16.0.
The
team
will
be
focusing
mostly
on
removals,
breaking
changes
and
seven
one
bucks.
First
up
for
this
major
Milestone.
We
have
the
breaking
changes
and
removals
that
we're
hoping
to
knock
out
first,
one
being
disabling
the
outbound
scope
for
the
secure
CI
job
token
workflow.
So
a
year
ago
we
added
this
functionality
to
I.
A
Don't
know,
allow
list
for
CI
job
token,
to
lock
down
the
functionality
to
prevent
people
from
abusing
that
CI
job
token,
and
we've
noticed
that
the
outbound
and
inbound
flows
are
confusing
for
users,
so
we
are
going
to
start
with
disabling
the
outbound
scope,
which
will
impact
projects
that
were
created
as
of
February
2023,
and
any
other
project
will
not
be
able
to
enable
the
outbound
scope
in
order
to
enforce
the
CI
job
token.
Workflow
you'll
only
use
the
inbound
scope.
A
So
the
only
thing
that's
really
changing
for
end
users
is,
if
you're
and
if
your
project
uses
the
CI
job
token
and
it's
a
brand
new
project,
you'll
need
to
enable
the
inbound
scoping
for
it.
Another
removal
or
breaking
change
that
we're
implementing
is
removing
this
required
pipeline
configuration.
So
previously
there
was
no
real
way
to
enforce
or
inherit
includes
throughout
projects.
This
is
before
the
compliance
solution
was
offered.
A
So
now
we're
going
to
be
deferring
to
this
compliance
pipelines
offering,
instead
of
using
a
required
pipeline
configuration
and
16
Auto,
that
means
required
pipeline
configuration
will
be
removed.
This
only
impacts
ultimate
self-managed
customers.
Now.
Another
piece
of
this
Milestone
that
we'll
be
working
on
are
Sev
one
and
cess
impacting
bugs
so.
First
up
we
have
a
Cess
impacting
bug
related
to
the
merge
request,
widget
and
how
a
review
app
is
presented
in
there.
So
today,
sometimes
a
review
app
will
go
missing
or
it
will
disappear
from
the
merger.
A
Quest
widget
it
can
be
really
confusing
for
users
and
especially
if
they
want
to
get
that
review
at
back.
So
we're
going
to
be
adding
some
different
experiences
to
the
merge
request,
widget
to
enable
users
to
understand
what
to
do
next.
For
that
review
app
another
high
priority
bug
that
we're
going
to
be
thinking
about
delivering
is
successful
pipelines
and
merge
trains
not
being
merged
or
executing
when
the
pipeline
before
that
fails.
A
So
today,
merge
trains
can
can
be
disrupted
whenever
there's
a
failure
before
a
successful
Pipeline,
and
that
means
that
there's
technically
a
merge
train,
that's
that's
kind
of
stuck
and
then
someone
needs
to
re-trigger
it
to
merge
successfully.
This
is
not
how
it's
designed,
so
we
want
to
make
sure
that
we
enable
automatic
merging
of
those
pipelines.