►
From YouTube: Pipeline Execution 15.4 Refinement/Planning Kickoff
Description
This video walks through the theme and goals for the 15.4 milestone that the Pipeline Execution team will be working towards.
The 15.4 planning issue can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/107
The needs weight board can be found here: https://gitlab.com/groups/gitlab-org/-/boards/4178322?not%5Bmilestone_title%5D=Started&label_name%5B%5D=group%3A%3Apipeline+execution&label_name%5B%5D=needs+weight
A
Hey
team:
this
is
the
refinement
kickoff
for
15.4.
It
is
already
that
time,
so
it
just
got
the
issue
into
a
little
bit
of
better
shape
and
our
board
is
in
pretty
good
shape.
A
So,
looking
through
our
theme
for
the
milestone
is
we
want
to
improve
the
developer
experience
when
troubleshooting
pipelines
always
our
reliability
goal
as
well,
and
so
some
of
the
goals
that
lead
up
to
that
theme,
our
reliability
goal
that
I
just
mentioned,
and
improving
the
developer
experience.
Troubleshooting
pipelines
we're
the
last
step
in
making
it
easier
to
understand
and
differentiate
the
merge
request,
pipelines,
the
different
labels,
getting
rid
of
detached,
merge,
request,
emerge,
result,
pipelines
and
then
fixing
a
bug
around
scheduled
pipelines
that
are
triggering
multiple
times.
A
That's
causing
some
confusion.
It
is
an
internal
customer
confusion
as
well
and
there's
a
problem,
so
I
know
our
engineering
productivity
friends
are
going
to
be
looking
for
that
and
then
I
have
another
goal
here.
One
of
the
steps
in
getting
us
wrapped
up
with
the
ci
minutes
work
is
closing
the
visibility
epic.
A
These
are
the
last
two
issues
in
that
epic
of
removing
the
shared
render
usage
tab
from
the
group
analytics
page,
where
we
initially
put
it
that
ux
cleanup
and
then
displaying
the
one
date
selector
for
the
user's
quotas,
on
both
the
namespace
and
on
the
group.
So
both
of
those
are
combined
into
the
single
issue.
If
we
want
to,
we
can
break
that
out
into
multiple
issues
or
just
multiple,
mrs
as
we
progress,
so
the
milestone
itself
is
in
pretty
good
shape.
A
So
far
as
I'm
looking
at
it
today-
and
today
is
july.
18Th,
for
you
know,
features
that
we're
going
to
release
with
the
september
22nd
release.
Looking
pretty
good,
we
do
already
have
quite
a
few
issues
that
are
ready
for
development.
That's
a
testament,
tl's
persistence
in
getting
things
refined
and
looking
at
that
knees,
weight
board,
making
sure
that
everything
is
in
ship
shape.
So
we
have
a
lot
there
already
and
we
only
have
a
few
things
that
are
in
planning
breakdown.
A
A
But
right
now
it's
looking
pretty
good,
so
we
have
a
couple
of
spikes
in
here:
getting
ready
to
deliver
some
popular
issues
like
making
the
afterscript
work
properly
and
investigation
around,
enabling
the
ci
token
permission
flow
for
bots,
like
the
pentabot
in
ensuring
that
those
kinds
of
projects
can
run
pipelines
on
an
mr
in
another
project
and
that
the
project
admins
of
that
target
project
have
the
right
permissions
to
allow
that
bot
to
do
that
and
not
have
the
token
leak.
A
So
those
are
some
of
the
big
spikes
that
I'm
looking
for
forward
to
being
delivered
as
we
continue
to
progress
in
delivering
on
those
solutions
for
customers
to
solve
their
problems.
So
that
is
a
quick
overview
of
the
milestone.
Take
a
look
post,
a
comment
to
the
video
once
it's
up
on
unfiltered
or
in
the
planning
issue
itself,
and
look
forward
to
your
feedback.
Thanks.