►
From YouTube: GitLab 15.1 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:
* Enforce CI Limit - https://gitlab.com/gitlab-org/gitlab/-/issues/243722
* Shared Runner usage by project in namespaces - https://gitlab.com/gitlab-org/gitlab/-/issues/356722
* Shared Runner usage by project in groups - https://gitlab.com/gitlab-org/gitlab/-/issues/355666
* Display the duration of each stage on the pipeline page - https://gitlab.com/gitlab-org/gitlab/-/issues/29439
* MVC: Configure CI/CD Quotas by project - https://gitlab.com/gitlab-org/gitlab/-/issues/357760
* Make the workflow to avoid duplicate pipelines in merge requests easy to use - https://gitlab.com/gitlab-org/gitlab/-/issues/299409
We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl
A
Hello
welcome
to
the
verify
pipeline
execution,
15.1
kickoff.
My
name
is
james
heimbuck,
product
manager,
for
the
pipeline
execution
group
here
at
kit
lab
and
as
a
reminder,
this
group
is
responsible
for
gitlab
ci
pipelines,
pipeline
processing,
as
well
as
the
category
of
merge
trains
and
I'm
joined
today
by
our
product
designer
vitica.
A
So
during
the
15.1
milestone
we're
going
to
enable
the
counting
for
ci
minutes
for
all
public
projects
using
the
shared
sas
runners,
the
team
has
been
working
hard
to
provide
visibility
to
the
shared
runner
usage
for
users
as
they
prepare
for
this
change.
Coming
on
june,
1st,
so
you'll
find
a
link
to
the
kickoff,
the
15.1
kickoff
page,
with
links
to
all
of
the
items
that
we're
going
to
talk
about
today
and
the
verify
stage
direction
page
with
discussion
of
our
future
work
and
direction.
A
In
the
comments
below
the
video,
you
can
always
reach
me
at
jheimbuk,
gitlab.com
or
through
comments
on
these
items
or
any
item
with
the
group
pipeline
execution
label
in
the
gitlab
project.
So
I'm
going
to
dig
in
a
little
bit
more
on
those
goals
that
the
team
has.
So
you
can
see
in
our
planning
issue.
We
have
three
big
goals
for
the
milestone
and
our
theme
is
puzzle.
A
Our
second
goal
is
rolling
out
the
enforcement
of
our
ci
limit,
so
the
actual
feature
itself
to
count
those
minutes
and
accumulate
the
ci
cd
minutes
for
all
public
projects
was
done
in
1410.
We're
launching
that
on
june,
1st
so
outside
of
the
milestone
and
happening
only
on
gitlab.com
we're
going
to
start
to
count.
All
minutes
should
runner
duration
minutes
for
public
projects,
and
I
wanted
to
share
then
with
our
last
goal.
A
We
want
to
bring
additional
visibility
to
the
shared
runner
usage,
so
today
is
really
easy
to
see
how
or
today
it's
really
hard
to
see
all
projects
are
using
those
shared
sas
runners,
you
can
see,
and
you
can
see
in
the
design
you
have
this
graph
today,
that's
showing
you
your
total
usage,
either
in
your
name
space
or
in
your
group,
but
it's
hard
to
tell
which
of
the
projects
that
you
have
in
that
namespace
or
group
are
using
all
of
those
minutes
and
so
to
provide
additional
visibility.
We
have
a
couple
of
issues.
A
So
that
is
what
the
team
is
focused
on.
Those
are
our
three
big
goals:
meeting
our
reliability,
slos
rolling
out
the
ci
minutes
and
adding
the
additional
visibility,
and
I
want
to
hand
it
over
to
vitica
who's
going
to
discuss
some
of
the
upcoming
usability
improvements.
The
team
is
exploring
for
later
in
the
year
and
vitica
I'll
stop
my
share.
So
you
can
hopefully
share
some
cool
stuff.
B
The
first
one
is
display
the
duration
of
each
stage
in
the
pipeline
page
now,
we've
had
this
long-standing
request
from
our
users
to
surface
the
duration
for
each
stage
in
the
pipeline
to
be
able
to
make
quick
assessments
about
the
bottlenecks
that
are
in
picture
now.
The
work
on
this
one
has
already
kind
of
kicked
off
because
we
were
in
the
middle
of
a
conversation
and
things
just
like
proceeded
and
we
have.
B
B
Now
we
do
have
this
option
today
to
set
a
limit
for
ci
minutes
consumption
at
the
name,
space
or
group
level,
and
that
gets
trickled
down
to
all
the
projects
that
are
kind
of
a
part
of
that
name.
Space.
But
not
all
projects
are
as
important
to
our
users,
so
we
want
to
provide
this
ability
to
them.
This
flexibility
to
set
consumption
limit
for
each
project
for
better
utilization
of
minutes.
B
The
last
one
that
I
want
to
speak
about
is
this
issue
that
says,
make
the
workflow
to
avoid
duplicate
pipelines
and
merge
requests
easy
to
use.
Now
about
a
year
ago,
when
many
of
our
users
were
facing
the
problem
of
ending
up
with
duplicate
pipelines
for
the
branches,
we
came
up
with
this
workflow
that
helped
them
fix
the
problem.
B
So
the
workflow
used
these
two,
the
workflow
involved,
defining
rules
with
the
help
of
ci,
open,
merge,
request
and
say,
merge,
request,
iid
now
the
problem
that
still
stands
is
this
solution.
This
needs
to
be
kind
of
taken
care
of
by
manually.
So
this
this
is
still
not
the
default
behavior.
So
this
issue
is
to
make
sure
that
the
proposal
that
we
had
put
across
then,
is
something
that
we
consider
for
our
default
behavior.
B
A
Oh,
those
are
really
exciting
features.
I'm
really
excited
that
we'll
be
able
to
show
duration
within
a
pipeline
of
where
the
stages
are
taking
the
most
time,
that'll
be
a
lot
easier
to
use,
at
least
within
a
single
pipeline.
I
think
that's
a
great
mvc
for
us
and
we
can
iterate
on
that
with
users,
so
we'll
definitely
be
opening
a
feedback
issue.
Once
that
feature
is
launched,
configuring
the
ci
cd
minutes
quotas.
I
know,
as
we've
been
working
forward
with
the
cia
minutes
proposal
that
that's
been
one
of
the
top
requests
of.
A
Let
me
configure
a
project,
so
it
doesn't
use
all
of
my
minutes,
so
that'll
be
really
exciting.
To
see-
and
I
know
those
duplicate
pipelines
are
things
that
something
that
pops
up
in
the
forum,
it
seems
like
every
other
week.
Why
do
I
have
two
pipelines
for
this?
Mr,
so
getting
that
workflow
to
be
default,
I
think,
is
gonna
solve
a
huge
pain
point
for
our
customers.
A
So
it's
three
really
exciting
pieces
of
functionality
that
I'm
looking
forward
to
happening
later
in
this
quarter,
thanks
for
showing
those
off
those
are
great,
so
we're
so
excited
for
the
work
that's
actually
happening
in
fifteen
one.
If
any
of
these
issues
are
interesting
to,
you
feel
free
to
give
us
a
tag
or
follow
in
any
of
the
issues.
Thanks.