►
From YouTube: GitLab 14.6 Kickoff - Verify:Pipeline Execution
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/337245
https://gitlab.com/gitlab-org/gitlab/-/issues/340504
https://gitlab.com/gitlab-org/gitlab/-/issues/329920
https://gitlab.com/gitlab-org/gitlab/-/issues/337087
https://gitlab.com/gitlab-org/gitlab/-/issues/340594
https://gitlab.com/gitlab-org/gitlab/-/issues/340593
https://gitlab.com/gitlab-org/gitlab/-/issues/300663
https://gitlab.com/groups/gitlab-org/-/epics/6687
A
Hi
welcome
to
the
pipeline
execution
14
6
kickoff.
My
name
is
james
heimbuck,
product
manager
for
the
pipeline
execution
group
here
at
git
lab.
As
a
reminder,
this
group
is
responsible
for
gitlab
ci,
such
as
pipelines,
pipeline
processing,
as
well
as
the
category
of
merge
trains.
I'm
joined
today
by
our
product
designer
vitica
and
in
14
6.
We're
focused
on
ci
minute
visibility
and
implementing
various
control
mechanisms
for
the
pipeline.
Permissions.
We'll
talk
about
those
issues
in
just
a
minute.
A
You'll
find
a
link
to
the
14
6
kickoff
page
with
links
to
these
items
and
our
verify
stage
direction
page
with
discussion
of
future
work.
In
the
comments
below
the
video.
You
can
always
reach
me
at
jheimbucketgitlab.com
or
through
comments
on
items
with
the
group
pipeline
execution
label
in
the
gitlab
project.
A
So
I'm
sharing
our
14-6
planning
issue
and
we
have
a
couple
of
top
investments
related
to
ci
improvements
which
include
hardening
our
ci
limit
for
public
projects,
so
just
ensuring
that
our
public
projects
are
respecting
the
limits
that
we've
put
out
there
for
them.
The
other
is
delivering
the
ci
usage
chart
which,
by
adding
the
monthly
pipeline
duration,
we're
going
to
add
the
monthly
pipeline
duration
for
projects
and
namespaces
to
this
chart,
just
give
better
visibility
to
the
minutes
being
used
by
those
public
projects.
A
A
This
unlocks
unblocks
our
jobs,
page
refactor
of
our
front-end
engineers
that
they've
been
working
on
to
improve
the
overall
page
experience
and
additionally,
following
the
14-4
release
of
the
ci
job
token,
secure
workflows,
we're
making
an
enhancement
to
enable
users,
better
visibility
into
the
scopes
of
the
ci
job
token
and
the
exposed
job
scope,
data
and
the
ci
job
token
api
for
introspection.
This
really
just
means
you'll
be
able
to
see
hey.
What
are
the
is
this
enabled
or
disabled?
What
are
the
projects
that
are
related
to
it?
A
B
Thank
you
so
much
james,
so
we
recently
did
a
cux
scorecard
research
and
based
on
our
findings
from
that
we
created
issues
to
make
it
easier
for
our
users
to
locate
and
track
the
usage
quota.
So,
for
example,
this
is
the
first
issue
that
we're
working
on,
which
says
list
all
projects
in
pipe
and
quota
section
with
a
pipeline
configured.
So
what
has
been
happening
until
now
is
until
no
pipeline
has
been
run
in
a
project.
Its
name
doesn't
show
up
in
the
pipeline
quota
section
of
the
usage
quota
page.
B
However,
for
the
storage
section
all
the
projects
are
listed,
so
we
just
want
to
make
sure
that
at
all
times,
even
when
there
are
no
pipelines
run
for
a
project,
if
there's
a
pipeline
configured
for
it,
it
should
show
on
the
usage
code
up
project
list,
then
moving
to
the
next
one.
B
This
one
says:
make
usage
quota
page
discoverable,
so,
as
you
would
be
experiencing,
the
usage
quota
page
is
not
very
discoverable
today
and
there
isn't
a
good
explanation
for
placing
it
under
settings
since
the
data
in
it
is
non
configurable.
B
So
considering
all
these
points
and
the
usability
associated
with
it,
we
are
planning
to
move
the
page
out
of
the
settings
and
to
place
it
in
a
more
discoverable
location,
and
this
issue
is
related
to
more
streams,
so
regular,
merge
button
shows
up
when
merge
string
is
enabled,
and
the
pipeline
for
mr
is
waiting
on
a
manual
action.
The
title
itself,
it's
pretty
explanatory
and
it's
a
bug.
So
when
you
switch
on
pipeline
must
succeed
option,
then
the
right
kind
of
text
appears
in
the
mr
widget.
B
B
Another
issue
that
I'm
very
excited
to
go
and
update
about
is
simplifying
word
strategies
with
auto
merge,
so
we'll
be
making
a
considerable
progress
on
this
work
on
providing
an
auto
merge
option
to
our
users.
This
milestone,
which
means
we'll
be
creating
some
designs
and
taking
it
to
a
few
users
for
just
to
get
an
idea
about
just
to
get
more
confidence
about
our
design
direction,
and
that
is
all
from
the
ux
side.
Back
to
you.
James.
A
Awesome,
thank
you.
Vitica!
I'm
really
excited
about
those
improvements
around
merch
trains.
That's
such
a
cool
feature
of
being
able
to
set
your
mr
to
merge,
know
that
all
of
the
things
in
front
of
it
on
the
train
is
going
to
get
merged
into
and
tested
so
that
you
can
really
quickly
find
those
conflicts
and
get
them
resolved
if
need
be,
but
really
have
that
confidence
that
my
pipeline
is
going
to
stay
green
as
we're
really
delivering
value
constantly
to
customers.
A
So
super
exciting
stuff.
Thank
you
so
much
so
we're
really
excited
for
14.6.
If
any
of
these
issues
are
interesting
to,
you
feel
free
to
give
us
a
tag
in
any
of
those
issues.
Thanks
so
much.