►
From YouTube: GitLab 15.10 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:
Replace Merge strategy labels with `Auto-merge` and change help text - https://gitlab.com/gitlab-org/gitlab/-/issues/359057
Make it easier to understand and differentiate merge request pipelines - https://gitlab.com/gitlab-org/gitlab/-/issues/217718
Display the total shared runner execution time / CI Minutes consumed on the pipeline details page - https://gitlab.com/gitlab-org/gitlab/-/issues/376270/designs/ci-cd-minutes-on-pipeline-page.png
Add Audit Logging for secure CI_JOB_TOKEN setting - https://gitlab.com/gitlab-org/gitlab/-/issues/338255
Display one date selector for usage quotas - https://gitlab.com/gitlab-org/gitlab/-/issues/363046
Add additional permission to allow retrying of jobs on protected tags - https://gitlab.com/gitlab-org/gitlab/-/issues/21868
We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl
A
Hi
welcome
to
the
verified
pipeline
execution,
1510
kickoff.
My
name
is
James
heimbuck,
the
product
manager
for
the
python
execution
group
here
at
gitlab.
As
a
reminder,
this
group
is
responsible
for
keeplab
CI
pipelines,
pipeline
product
scheduled
and
the
category
of
merge
trades
I'm
joined
by
the
pipeline
execution
product
designer
vegica
you'll
find
a
link
to
the
1510
kickoff
page
with
links
to
the
items
we're
discussing
today
and
the
verify
stage,
Direction
page
with
discussion
of
our
future
work
in
the
comments
below
the
video.
A
A
A
We've
done
some
work
already
to
date,
but
we're
introducing
some
new
labels
instead
of
attached
as
the
label
for
a
branch
pipeline
that
just
make
it
a
little
bit
easier
to
understand.
What
is
this
pipeline
that
just
ran?
What
kind
of
pipeline
is
it?
What
did
it
run
against
as
far
as
the
code
in
the
branch?
A
So
it's
easier
to
understand
for
users
to
see
where
they're
at
in
their
Mr
and
then
moving
on
with
the
start
of
this
1510
Milestone
we're
starting
to
turn
our
attention
to
the
larger
investment
themes
for
the
new
fiscal
year,
and
we
have
two
features
in
the
Milestone
that
really
contribute
towards
two
of
those
investment
themes.
The
first
is
observability
analytics
and
feedback,
and
that
is
an
issue.
That's
showing
a
little
bit
more
data
about
how
much
time
the
pipeline
took.
It's
really
easy
to
feed.
A
Today,
the
total
pipeline
duration,
time
or
I
often
call
that
wall
clock
time
between
when
the
pipeline
started
and
when
it
ended,
and
it's
easy
to
see
an
individual
job.
How
long
maybe
it
took,
but
what's
not
so
simple,
is
to
figure
out
how
long
it
took
for
all
of
the
jobs
to
run
and
thinking
about
your
compute
or
your
CI
compute
credit
through
cipd
minutes
how
many
of
those
were
consumed
by
that
pipeline.
So
this
issue
brings
the
detail
of
the
total
pipeline
time
that
you
credits,
consumed
and
the
time
spent
queued.
A
Do
the
pipeline
detail
page
for
easier
access
without
having
to
add
up
a
bunch
of
jobs
through
the
jobs
page
even
filtering
there
make
that
really?
Not
the
easiest
thing
to
do,
especially
if
you
have
you
know,
potentially
hundreds
of
jobs
that
run
in
a
pipeline.
Now,
it's
all
nice
and
easy
in
one
spot
for
you,
so
you
can
see
how
many
minutes
were
consumed
by
the
jobs
within
the
pipeline.
A
We're
going
to
add
an
audit
event
when
this
setting
is
changed
so
when
the
setting
is
turned
off
for
now,
while
it's
not
a
default
setting
and,
more
importantly,
when
projects
are
added
so
that
customers
who
need
that
level
of
compliance
or
audit
can
be
within
their
audit
logs
who
added
this
project?
What
what
would
the
project
that
was
added?
When
was
it
added
or
removed
to
try
to
understand
if
they
need
to
within
those
Auto
events,
both
activating
their
project
and
so
now?
B
B
So
one
of
the
issues
that
we'll
be
working
in
this
Milestone
like
that,
will
be
working
on
the
proposal
for
in
this
Milestone.
Is
this
just
play
one
date:
selector
for
usage
quota
graphs
on
the
usage
quota
graphs.
We
show
a
bunch
of
crafts
today,
I
mean
on
the
usage
quota
page.
We
show
many
crafts
today
and
that's
primarily
to
give
users
an
insight
into
their
CI
CD
minutes
consumption
and
how
their
Runner
use
it
has
been
like.
B
But
at
the
same
time
as
you
can
see,
there's
a
lot
many
date
selectors
and
I
mean
from
observing
the
usage
so
far.
You've
also
realized
that
when
users
are
searching
for
some
information,
it
is
usually
in
the
same
context
right
like
they
are
trying
to
look
at
the
data
from
the
same
time
frame.
So
why
don't
we
give
them
an
option
to
only
select
the
date
once
and
see
all
the
related
information
to
that
date?
B
All
in
the
all
in
one
go,
that's
what
we'll
be
trying
to
do
through
this
issue,
and,
secondly,
is
another
one
that
says
add
additional
permission
to
allow
retrying
off
shops
on
protected
tags.
Now,
there's
a
bug
that
has
been
identified,
that
when
users
users
expect
to
be
able
to
retry
a
job
on
a
protected
branch
that
they
have
permission
to
access,
but
somehow,
in
certain
circumstances
they
are
not
able
to
do
that.
A
Really
excited
for
the
new
date
selector
on
that
page
and
also
fixing
the
bug.
That's
there
around
selecting
and
showing
the
right
dates.
We
show
the
right
dates
rather,
but
having
the
selector
match
up
so
that
you
can
more
easily
navigate
to
the
month
that
you
care
about.
Looking
at
that
shared
Runner
duration
and
cicd
minute
consumption,
that's
exciting!