►
From YouTube: Pipeline Execution 15.7 Refinement/Planning kickoff
Description
This video walks through the theme and goals for the MM.m milestone that the Pipeline Execution team will be working towards.
The 15.y planning issue can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/117
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
A
So
the
big
theme
for
the
Milestone
is
the
secure
CI
job
token
by
default
and
there's
two
big
issues
that
roll
into
that
in
our
goals.
The
front
end
for
the
new
interface
for
inbound
the
back
end
work
is
just
moved
into
15-6,
but
is
in
Flight
already.
This
is,
hopefully
it
could
pull
forward
even
and
then
making
that
the
default
for
any
projects.
So
today
you
have
the
option
to
make
use
the
limited,
CI
job
token
your
default
option,
but
it's
not
on
by
default.
A
We're
going
to
flip
that
in
anticipation
of
n160
getting
rid
of
that
feature
altogether.
So
it's
just
the
limited
token
and
you
have
to
set
an
inbound
scope
for
it
of
which
projects
can
use
their
token
on
yours.
So
then,
the
second
goal
here
is
back
in
work
for
cost
factors
get
in
the
cost
factors
out
of
the
code
and
we
have
a
new
column
for
the
standard
in
the
OSS
cost,
Factor
admin
and
then
not
applying
those
cost.
A
Factor
discounts
to
the
back
and
the
windows
Runners,
which
we're
doing
in
a
horrible
way
today,
I
think
so.
I've
got
almost
everything
into
a
verified
label
that
is
in
the
Milestone
of
the
CI
job
token
work
is
in
a
verify,
P
ones.
After
getting
our
slos
for
any
sort
of
reliability,
security
type
things
done,
that's
the
first
thing
we
should
be
looking
at
and
then
pulling
from
the
right
or
working
from
the
right.
Rather,
we
have
an
infra
Dev
issue.
A
We
have
a
potential
data
Integrity
issue,
although
we
haven't
seen
any
data
loss,
something
to
look
at,
that's
a
verified
P1
as
well,
then
we
get
into
the
secondary
goals,
creating
those
columns,
cost
factor
and
some
bugs
that
they
have.
So
those
are
the
issues
and
then
into
verify
P3.
These
are
going
to
be
stretch.
If
anything,
if
we
get
to
them
a
git
push
option
bug.
A
That's
one
of
our
more
popular
bugs
in
the
backlog
that
isn't
scheduled
and
working
with
the
runner
team
on
ensuring
that
after
script
is
called
for,
ensuring
that
after
ship
is
after
script,
is
actually
canceling
or
being
called
on
a
canceled
in
a
timed
out
pipeline.
Whoa,
that's
a
mouthful,
so
those
are
some
highlights
in
215.
7.
I
also
wanted
to
just
click
into
and
look
at
this
CI
minutes
cost
Factor
follow-ups.
A
We've
moved
all
of
the
tech
debt
and
the
pending
work
around
the
ca
minutes
work
now
that
we're
down
to
a
cost
factor
of
one
on
the
public
projects
into
a
single
epic.
So
we
can
close
out
that
other
epic.
So
all
of
that
work
is
here:
15,
7,
15,
8
and
into
15
9.
It
looks
like
that
we'll
be
doing
the
cleanups.
A
It's
really
getting
that
cost
factor
into
the
database
so
that
we
can
change
it
more
easily,
not
having
it
hard
coded
in
the
code,
so
that
we're
not
having
to
push
code
changes
to
make
those
changes
and
then
wanted
to
look
a
little
bit
ahead
into
15
8.
This
will
be
the
January
release.
So
again,
it's
going
to
be
a
lighter
one.
I'll
be
filling
in
issues
here,
there's
stuff
already
in
the
Milestone
and
with
verify
P1
and
P2
that
just
isn't
into
this
planning
issue.
A
That's
the
big
theme
goals
as
always
meeting
our
reliability,
slos,
reliability,
issue,
slos
and
then
completing
that
CNN
work
using
that
new
cost
Factor
columns
behind
the
feature
flag,
so
the
feature
flag
may
still
be
there,
we'll
remove
it
in
15
9
in
case
anything
goes
wonky.
Those
are
kind
of
some
headlights
into
what's
coming
in
what
will
be
the
15-8
Milestone,
so
I'll
post
this
to
unfiltered
I'll
drop
a
link
into
the
Channel
with
links
to
these
two
planning
issues
as
well.