►
From YouTube: Pipeline Execution 14.9 Refinement/Planning Kickoff
Description
This video walks through the theme and goals for the 14.9 milestone that the Pipeline Execution team will be working towards.
The issue itself can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/86
A
Hey
team
recording
a
kickoff
to
we're,
recording
a
video
to
kick
off
our
14-9
refinement
and
planning
around
the
14-9
milestone
so
for
pipeline
execution.
The
big
theme
of
this
milestone
for
me
or
the
big
themes
are
two
one:
getting
our
cn
minutes.
Work
unblocked
and
second
theme,
improving
customer
experience
with
pipelines
and
mr
widgets
so
goals
for
the
milestone
that
lead
up
to
those
themes.
The
first
one
is
delivering
two
of
the
group
utilization
issues
that
are
blocking
the
remaining
ci
minutes.
A
Those
are
both
verified
p1's,
both
listed
here
we've
synced
with
the
pm
in
utilization
and
they're.
Happy
to
have
us
pick
those
up
they're
not
going
to
get
to
them
until
later,
but
those
are
blockers
for
us
to
apply
new
cost
factors
to
public
projects,
oss
projects,
making
sure
that
those
folks
are
still
being
able
to
contribute
and
really
just
help
unblock
some
of
that
work.
So
those
are
the
two
issues
there.
We
should
jump
in
start
refining
those
they
have
proposals
already,
but
from
utilization,
who
has
a
lot
more
familiarity
with
that
code.
A
Obviously
so
we
should
dig
in
and
make
sure
that
we're
not
getting
in
over
our
heads.
Hopefully
we
can
get
these
done
within
fourteen
nine,
but
we
could
have
these
trail
over
into
fourteen
ten.
The
two
that
are
here
unblock
a
third
utilization
issue,
which
is
really
in
turn
the
blocker
for
us
continuing
on
the
work
to
harden
ci
limits.
So
these
are
kind
of
foundational
pieces
and
utilization
is
going
to
be
available
to
help
answer
any
questions.
A
Do
the
reviews
on
these
so
to
make
sure
that
we're
getting
everything
done
that
we
need
to
get
done
next
step
is
delivering
four
of
the
sus
okay,
our
issues,
we're
kicking
off
a
new
quarter
on
monday
february,
1st
for
the
new
fiscal
year,
23
q1.
As
part
of
that
we
have
12
sus
issues
between
step,
one
and
step
two
that
we
want
to
deliver.
So
we're
already
delivering
a
couple
of
those
within
14
8,
which
is
great
within
14
9.
A
I
have
four
of
them
called
out
one
step,
one
and
three
sub
twos.
I
believe
that
all
of
these
are
in
a
good
state
ready
to
go,
have
design.
So
we
should
be
able
to
jump
right
into
those
and
get
working
on
those
and
then
so
those
will
help
overall
they're,
just
better
experience.
Making
the
group
level
usage
quote
quote
a
page
discoverable
improving
mr
budget
warnings.
Things
like
that,
so
overall,
really
really
great
and
our
last
goal
for
the
milestone,
which
doesn't
lead
up
to
one
of
the
themes.
A
But
it's
something
that
we
need
to
get
moving
on.
Mr
gregorish
and
marius
is
defining
the
work
needed
for
the
cicd
time.
Decay,
epic
and
the
ci
builds
metadata
work,
so
I'm
going
to
double
click
into
those
real
quick
as
we
look
at
those.
So
we
have
two
efforts
here.
These
were
promoted
to
epics
from
issues,
and
these
follow
on
from
the
engineering
allocation
is
my
understanding.
Partitioning
builds
queueing
tables
using
list-based
partitioning,
that
is
work
that
came
out
of
the
time
decay
blueprint
and
then
a
new
ci
builds
metadata
table
growth.
A
We
need
to
address
some
of
the
issues
that
are
here
and
understand
why
this
is
growing
linearly
again.
Gregorish
and
marius
are
looking
into
that.
So
defining
the
work
for
those
within
this
within
this
milestone,
so
that
we
can
start
to
work
on
those
and
understand
if
we
do
need
to
get
an
engineering
allocation
going
or
allocate
more
of
our
engineers
towards
that
effort
or
get
help
externally
outside
of
the
group.
So
those
are
the
the
big
things
that
I'm
thinking
about.