►
From YouTube: Pipeline Execution 15.10 Refinement/Planning Kickoff
Description
This video walks through the theme and goals for the 15.10 milestone that the Pipeline Execution team will be working towards.
The 15.10 planning issue can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/126
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
18
wanted
to
walk
through
the
15-10
planning
issue,
as
we
kick
off
refinement
and
waiting
of
those
issues.
A
So
1510
our
theme
is
going
to
be
making
it
obvious,
the
command
Markham
emerged
and
what
pipeline
will
run
or
what
pipeline
type
so
some
of
the
gold
toward
that
theme
actually
the
first
goal
of
the
map
real
well,
but
at
that
in
the
DI
job
token
event
to
the
audit
log,
so
that
the
next
step
in
our
bigger
CI
job
token
workflows,
epic,
and
that
should
get
us
close
to
wrapping
up
phase
one
one
of
that
and
it
Maps
really
nicely
to
our
fiscal
24
investment
team
of
advanced
security
and
compliance.
A
By
putting
this
into
audit
logs,
it
enabled
it
for
those
authors
to
see
which
project
are
we
allowing
to
act,
the
different
projects
as
an
org
and
how
to
compliance
or
has
an
audit
function?
And
then
the
two
issues
that
map
up
really
nicely
to
that
Milestone
theme,
making
it
easy
to
understand
and
differentiate
the
different,
merge
request
pipelines
the
back
end
work
for
it
the
front
end.
Work
is
in
a
later
Milestone.
A
If
this
gets
done
early
in
the
Milestone
I
see
no
reason
why
we
can't
pull
that
forward,
though,
and
deliver
on
that
in
the
front
end
and
then
replacing
the
merge
strategy.
Labels
with
the
auto
merge
and
changing
the
help
effects
to
make
it
a
lot
easier
to
understand.
What's
going
to
happen
when
I
click
this
button,
when
can
my
Mr
merge?
What
needs
to
happen
before
that?
A
So
then,
breaking
down
the
some
of
the
issues
in
note
in
the
Milestone
we
have
one
verified
P1
right
now
around
recalculating
remaining
minutes
on
additional
packs.
That's
going
to
make
it
easier
for
us
to
understand
which
projects
are
buying
more
CI
CD
minutes,
as
we
think
about.
Does
that
make
it
stickier
or
make
it
a
stickier
experience
for
them,
and
then
we
can
use
that
data
to
encourage
more
usage,
more
purchase.
Make
that
purchase
look
easier.
A
If
it
doesn't,
then
we
can
shift
our
priorities
built
where
infra
Dev
issues
there's
none
listed,
no
corrective
actions
right
now,
hopefully
stays
that
way,
and
then
the
verified
p2s,
the
things
that
we've
already
discussed
and
then
the
back
end
research
for
the
very
scheduling
algorithm.
That's
probably
the
ones
that
risk
to
move
out
of
the
Milestone
verify
p3s.
Then
all
of
these
would
be
potentially
at
risk
for
moving
out
of
the
Milestone
and
then
some
bugs
of
note
that
aren't
a
verified,
P2
or
P3.
A
Some
of
these
have
been
in
here
for
a
while
and
have
missed
envelope
on
them,
but
definitely
interesting
bugs
that
you
know
are
going
to
improve
customer
experience.
User
experience
when
we
get
them
resolved.
I,
don't
see
any
feature.
A
Flags
that
are
rolling
out
yet
within
the
Milestone
I
would
expect
that
if
we
have
CI
job
token,
work
still
happening
that
that
would
have
a
feature
flag
will
be
rolling
out
during
1510,
and
then
we
know
that
we're
gonna
have
a
number
of
issues
that
probably
get
a
feature
flag
rollout
associated
with
them.
Let's
try
to
get
those
created
through
them
later
Richard.
A
If
you
can
take
a
look
at
any
open,
flicky
test
or
quality
test
that
you
want
to
get
resolved
and
test,
especially
around
that
CA
job
token
flow
that
we
want
to
work
on
during
the
Milestone,
be
great
to
list
them
out
and
understand
what
developer
help
we
need
and
then
docs
improvements,
Catherine
and
Marcel.
Is
there
anything
that
we
want
to
focus
on
again
around
that
CI
job
token
work?
A
25
maintenance
and
Bug
maintenance
will
probably
skew
a
bit
higher
as
we
continue
to
work
on
the
CI
scaling
work
and
have
some
dedicated
folks
there,
so
that
ratio
might
shift
a
little
bit
and
then
we
do
know
that
there
is
a
bit
of
a
dip
into
the
error
budget
over
the
last
week.
I
think
that
it
will
have
rolled
out
by
the
time
we
get
to
1510,
but
that
might
cause
that
ratio
to
change
a
little
bit
as
we
get
into
the
Milestone.
A
So
those
are
the
big
golden
themes
around
1510,
so
you
should
start
to
see,
needs
weight,
issues
show
up
underneath
wakeboard
and
you
can
take
a
look
if
you
have
questions
by
all
means
ping
me
on
the
video
in
black
or
on
the
issue
and
I'll
get
back
to
you.
Thanks.