►
From YouTube: GitLab 15.8 Kickoff - Verify:Pipeline Execution
Description
Links for the YouTube post
Kickoff Page: https://about.gitlab.com/direction/kickoff/#verify
Ops Direction: https://about.gitlab.com/direction/ops/#verify
Issues Discussed:
UI for Inbound CI_JOB_TOKEN - https://gitlab.com/gitlab-org/gitlab/-/issues/375782
Custom Pipeline Name - https://gitlab.com/gitlab-org/gitlab/-/issues/372538
Job Filter Solution validation - https://gitlab.com/gitlab-org/ux-research/-/issues/1815
Design: Set CI/CD Minute Limit for a project - https://gitlab.com/gitlab-org/gitlab/-/issues/384874
Improve workflow for finding a project to set limit for - https://gitlab.com/gitlab-org/gitlab/-/issues/366929
We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl
A
As
a
reminder,
this
group
is
responsible
for
gitlab
CI
pipeline
pipeline
processing,
as
well
as
the
category
merge
trains
you'll
find
a
link
to
the
15
8
kickoff
page
with
the
links
to
these
items
and
the
verify
stage,
Direction
page
with
a
discussion
of
our
future
work
in
the
comments
below
the
video,
and
you
can
always
reach
me
at
jheimbuck,
getlive.com
or
through
comments
on
items
with
the
group
pipeline
execution
label
and
the
gate
lab
project.
So
I'm
already
sharing
this
my
screen,
showing
our
158
planning
issue
and
we'll
start
with
our
theme.
A
So
our
theme
for
15
8
is
security
and
reliability.
A
couple
of
the
goals
that
we
want
to
accomplish
towards
that
theme
and
the
Milestone
are
first
meeting
our
reliability
issue.
Slo
we've
again
been
making
great
progress
here
over
the
last
couple
of
quarters
and
Milestones
really
increasing
availability
for
our
endpoints,
reducing
our
backlog
of
these
kind
of
issues
and
we're
really
burning
it
down.
But
it
continues
to
be
a
top
investment
theme
and
a
top
priority
for
us
as
a
group.
A
Our
second
goal
towards
that
security
and
reliability
theme
is
shipping
that
next
iteration
of
the
ti
job
token
in
issue
three:
seven:
five,
seven
or
three,
seven,
five,
seven,
eight
two-
and
this
is
the
UI
to
implement
that
new
inbound
scope
for
The
Limited,
CI
job
token
we're
doing
this.
A
head
up
and
I've
talked
about
this
on
a
couple
of
the
kickoff
videos
now
with
16
over
lease,
where
we
will
be
removing
the
non-limited,
CI
job
token
capability
and
removing
the
outbound
flow
as
well
and
just
settling
on
the
inbound
flow.
A
So
you
as
a
project
owner
or
a
project
maintainer
can
set
which
projects
are
allowed
to
trigger
a
pipeline
using
a
TI
job
token
in
yours,
then
future
iterations
of
this
we're
going
to
get
being
able
to
set
by
what
CI
job
token
would
have
access
to
different
permissions.
There.
We
have
an
epic
for
that
and
I'll
link
to
that
in
the
comments
below
for
future
work
and
then
the
last
item
I
want
to
mention
that
doesn't
necessarily
match
up
with
a
theme
tune.
Something
we're
really
excited
about.
A
Around
usability
of
the
product
is
this
issue
of
adding
custom
name
to
pipelines,
so
this
was
broken
out
of
a
larger
discussion
and
a
couple
of
use
cases
that
we
identified
from
use
users
where
they
want
to
specify
the
name
of
a
pipeline
either
dynamically
or
statically
beforehand.
And
so
this
is
the
static
use
case
and
I'm
especially
excited
about
this,
because
it's
contributed
from
an
internal
team.
A
and
if
you
decide
not
to
use
it,
you'll
continue
to
see
what
you
see
today,
which
is
the
commit
name
for
the
pipeline
that
shows
up
in
the
pipeline
list
or
if
you
set
it
guilty.
The
pipeline
name
there.
So
now,
I
want
to
walk
through
a
couple
of
things
from
vitica
our
product
designer
that
she'll
be
focusing
on
in
15-8
Milestone
and
the
first
is
solution,
validation
around
job
filters.
A
So
we've
introduced
job
filters
a
couple
of
Milestones
ago
and
want
to
get
some
feedback
from
users
about
how
they're,
using
it
and
other
feature
iterations,
do
those
meet
the
needs
and
solve
for
the
problems
that
the
customers
have.
So
it
should
be
working
through
that
the
next
is
working
on
design
for
setting
that
CI
CD
minute
limit
for
a
project.