►
From YouTube: GitLab 15.5 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:
Next iteration of CI_JOB_TOKEN - https://gitlab.com/gitlab-org/gitlab/-/issues/346298
Configure CI/CD Quotas for Projects - https://gitlab.com/gitlab-org/gitlab/-/issues/357760
Configure CI/CD Quotas for Projects under Groups - https://gitlab.com/gitlab-org/gitlab/-/issues/362287
No Notifications for Failed scheduled pipelines - https://gitlab.com/gitlab-org/gitlab/-/issues/36806
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,
15.5
kickoff.
My
name
is
james
heimbuck
product
manager
for
the
pipeline
execution
group
here
at
gitlab,
a
reminder
that
this
group
is
responsible
for
gitlab,
ci
pipelines,
pipeline
processing,
as
well
as
the
category
and
features
in
merge
trains
and
I'm
joined
by
our
product.
Designer
vitica
today
you'll
find
a
link
to
the
kickoff
page
415.5
with
links
to
these
items
and
the
verify
stage
direction
page
with
discussion
of
our
future
work.
In
the
comments
below
the
video.
A
A
I'm
sharing
my
screen
with
our
planning
issue
for
15.5,
and
our
theme
for
this
milestone
is
the
next
step
in
secure
pipelines,
and
so
some
of
the
goals
that
we're
working
on
within
the
15-5
milestone
are
first
meeting
our
service
level
objectives
for
any
critical
reliability
or
performance
issues
bugs
that
might
pop
up
again.
We've
made
great
progress
the
last
couple
of
quarters,
so
I
really
have
no
doubt
that
the
team
will
be
able
to
deliver
on
this
goal
in
the
milestone.
A
A
We've
been
working
on
this
project
for
quite
some
time.
I
feel,
like
we've,
been
talking
about
ci
minutes
and
our
kickoffs
almost
all
year,
if
not
longer,
but
really
really
close
to
wrapping
up
that
work
and
having
already
met
our
goal,
that
users
of
gitlab
sas
shared
writers
can
see
their
cicd
minute
consumption
with
a
good
understanding
of
which
projects
or
groups
are
consuming
the
most
minutes
out
of
their
quota
and
so
I'll
hand
it
over
to
vitica
now
to
discuss
some
upcoming
usability
improvements
that
the
team
is
exploring
for
later
this
year.
B
Thank
you
james.
As
you
open
the
issue,
I
would
just
talk
a
little
about
what
we
are
looking
forward
to
doing
this
milestone
on
the
ux
side.
So
previously
I
spoke
about
and
also
like.
We
shared
our
progress
around
the
work
that
we
did
for
making
for
adding
configuration
to
the
user
name
space
level
for
users
to
be
able
to
control
their
project,
cicd
consumption,
so
being
able
to
control
their
quota
or
add
a
quota
to
projects
for
ci
cd
minutes.
B
We
took
our
solution
for
our
validation.
Research
spoke
to
many
users,
and
we
also
received
many
good
insights
that
will
that
helped
us
like
make
meaningful
changes
to
the
proposal
that
we
had
in
the
first
place
now.
Moving
on
to
the
next
step
of
that
work
is
the
issue
which
is:
where
did
it
go?
I
think
it's
a
it's
in
another
tab,
james.
A
B
Now
we
are
going
to
take
that
work
forward,
implement
the
design
for
groups
and
it's
definitely
going
to
be
much
more
complex,
because
when
we
talk
about
groups
we
also
talk
about
the
subgroups
which
are
nested
inside
it
yeah
and
then
once
we
are
confident
with
our
proposal
we'll
again
take
it.
Our
validation,
then
moving
on
to
the
no
notification
for
failed
pipeline
schedule
pipelines
now
when
a
person
creates
a
schedule
pipeline,
they
own
it
by
default
and
if
they
decide
to
lead
the
organization
or
the
project
or
the
group.
B
The
ownership
is
not
shifted
by
default,
and
this
is
a
problem
because
then,
if
anything
happens
to
the
pipeline,
if
it
fails,
nobody
gets
the
notification
for
that.
So
we
will
be
fixing
that
behavior
we'll
be
abandoning
the
rules
there
and
also
look
for
any
other
scope
for
any
other
change
in
this,
and
that's
the
two
works
that
I
would
mostly
be
focusing
on
this
milestone.
A
Fantastic
that
validation
step
is
so
important,
and
I'm
really
glad
that
we
do
that,
so
that
we
get
solutions
in
front
of
users
early
in
the
process.
I'm
really
excited
to
see
the
exploration
around
the
notification
for
failed,
scheduled
pipelines.
That's
a
great
step
for
us
as
users.
Talk
about
things
fail
all
the
time
I
don't
know,
especially
when
changing
owners
of
the
scheduled
pipelines,
which
is
a
really
common
use
case,
so
super
exciting
stuff
that
we're
working
on.
So
we're
really
excited
for
fifteen
five.