►
From YouTube: GitLab 15.9 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/groups/gitlab-org/-/epics/7290
* https://gitlab.com/gitlab-org/gitlab/-/issues/372538
* https://gitlab.com/gitlab-org/gitlab/-/issues/376270
We love feedback and you can reach me at jheimbuck@gitlab.com or mention me on GitLab.com using @jheimbuck_gl
A
Foreign
welcome
to
the
verified
pipeline
execution,
59
kickoff.
My
name
is
James
eibach
product
manager
for
the
pipeline
execution
group
here
at
gitlab.
As
a
reminder,
this
group
is
responsible
for
give
out
di
pipeline
pipeline
processing
envelope.
The
category
of
merge
trains
and
I'm
joined
today,
as
always
by
the
pipeline
execution
product
designer
vitica
you'll,
find
a
link
to
the
59
pickup
page
for
the
group
with
links
to
these
items
and
the
verify
stage,
Direction
page
with
discussion
of
our
future
work
within
the
stage
within
the
group.
A
A
So
we
kicked
off
the
quarter
with
a
goal
of
improving
the
time
it
takes
to
create
a
pipeline
on
average
by
50
one
of
the
next
things
that
we're
working
on
to
do.
That
is
to
make
some
of
the
debt
in
the
profit
of
pipeline
creation
asynchronous
and
one
example
that
the
team
is
working
on
within
right
now:
15
8,
but
we're
going
to
be
rolling
out
in
15
9
that
got
started
early
with
the
auto
cancellation
of
pipeline.
A
Our
movie
cancel
pending
pipeline
step
to
run
asynchronously,
so
we
think
that
that
will
reduce
the
duration.
It
takes
to
create
a
pipeline
happening
in
real
time
by
15
to
20
percent.
So
it's
a
big
Improvement.
It
does
been
applicable
to
every
pipeline,
but
it
is
a
step
that
we
can
take
towards
our
larger
goal
of
improving
that
pipeline
creation
time
and
then
one
of
the
other
big
things
that
the
team
is
going
to
be
working
on
as
we've
worked
through.
A
The
issues
that
we've
been
able
to
identify
is
adding
some
tracing
code
into
the
pipeline
creation
service.
That'll
enable
us
to
better
be
with
data
where
there
might
be
bottlenecks
in
the
process
that
we
can
tackle
later,
and
then
this
is
just
part
of
a
larger
goal
across
the
stage
within
verify
of
making
git
live.
A
This
is
one
of
the
larger
tables
within
the
database,
there's
a
lot
of
metadata
associated
with
jobs
that
they
run
and
we've
been
storing
it
for
a
long
time.
So
the
team
is
going
to
work
on
starting
to
write
and
read
data
from
the
news
di
built
metadata
partition
and
they
started
to
work
on
new
issues
within
15
8
partitioning
that
today
builds
table
and
attending
the
partition
ID
to
the
query.
So
they
can
start
to
use
the
new
partitions
and
expect
that
work
to
roll
out
in
the
T9.
A
So
the
big
step
for
the
team
is
they
get
away
from
one
giant
table
to
starting
to
use
smaller
versions
of
the
table
and
creating
new
partitions,
as
we
need
to
improve
performance
for
customers
and
see
less
downtime
at
the
release
to
these
really
large
Cable.
In
this
di
build
data
and
with
that
I'm
going
to
hand
it
over
to
vedica
to
talk
about
some
of
the
upcoming
usability
improvements
and
research
that
the
team
is
exploring
for
later
in
the
year.
B
Thank
you
James,
so
for
the
coming
Milestone
I
do
have
some
items
which
are
like
more
about
analyzing,
the
previous
researches,
but
as
for
the
new
ones
that
I'm
going
to
undertake.
This
is
the
first
solution:
validation
for
adding
custom
names
to
pipelines
in
1507.
We
delivered
a
feature
through
our
internal
contribution
that
allows
users
to
add
a
name
to
their
pipeline,
a
custom
name
using
the
keyword,
workflow
names
and
I
mean
we
had
a
lot
of
discussions
on
the
issues
we
are.
B
We
were
very
confident
of
the
use
cases
that
we
were
catering
to,
but
it's
time
that
we
also
talk
about
how
our
users
are
now,
finally
using
this
particular
feature
and
how
they
are
incorporating
this
and
their
workflows.
And
how
is
it
that
we
can
make
it
more
usable
learning
from
those
interviews
from
from
those
conversations
and
the
next
item
that
I'll
be
looking
at
this
Milestone
is
this
issue
that
talks
about
displaying
the
total
shared
Runner
execution
time
or
the
CI
CD
minutes
consumption
per
Pipeline
on
the
pipeline
Details
page.
B
This
is
a
really
good
like
issue
that
it's
the
suggestion
that
is
provided
through
this
issue,
that
we
should
be
providing
that
information
on
the
pipeline
detail
page,
which
is
a
very
visited
page
and
that's
where
one
gets
to
see
all
the
information
about
all
the
running
pipelines.
So
why
not
also
present
some
information
around
how
much
minutes
a
particular
pipeline
that
has
finished
as
consumed,
and
that
should
be
all
back
to
you.
James.