►
From YouTube: Pipeline Execution 15.5 Refinement/Planning Kickoff
Description
This video walks through the theme and goals for the 15.6 milestone that the Pipeline Execution team will be working towards.
The 15.6 planning issue can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/113
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
Thank
you.
I
wanted
to
walk
through
the
15-6
planning
issue,
as
we
start
refinement
on
the
issues
in
that
Milestone
talk
through
the
theme
and
the
goals
and
get
some
headlines
into
15
7
as
well,
so
15
6
is
all
the
way
out
into
November
when
we're
going
to
release
it.
So
it
seems
like
forever
away
after
having
just
kicked
off
15-5,
which
is
the
October
release,
but
wanted
to
get
going
talking
about
it.
A
So
our
theme
in
the
Milestone
is
improve
the
understanding
of
pipeline
types
and
what's
happening
in
them.
Our
goals
for
the
Milestone
always
meeting
our
reliability
issue
slos,
those
are
always
getting
verified
p1s.
Those
are
things
like
security
and
data
loss.
Anything
super
top
of
that
prioritization
table
following
that
is
goal,
a
goal
that
contributes
to
the
theme
so
delivering
issues
to
better
understand
the
pipeline
types
word
pipelines
but
fail
to
start
or
when
they
fail
to
start.
A
So,
if
the
back
end
and
the
front
end
issue
both
around
new
pipeline
labels
for
the
unlabeled
merged
results
pipelines,
so
both
of
those
issues
are
in
the
Milestone.
We've
done
plenty
of
refinement
on
those
that
should
be
ready
to
pick
up
and
go.
The
other
is
a
update
around
when
a
Max
job
limit
is
reached.
We
don't
do
a
great
job
today
of
showing
a
user.
What
has
happened,
their
pipelines
just
fail
or
canceled,
so
we
want
to
improve
the
usability
there.
A
So
if
you
hit
a
hit
a
limit,
you
know
why
you
hit
a
limit,
and
you
understand:
hey
I
need
to
just
wait
until
some
jobs
clear
out
and
then
I
can
start
this
pipeline
and
then
the
next
issues
in
the
phase
1.1
of
this
year,
job
token
work
so
exposing
the
job
scope,
token
API
for
introspection
and
as
I
was
looking
at
this
issue,
the
other
day
I
saw
it
was
actually
picked
up
and
I
think
that
this
might
be
merged.
A
So
we
may
be
able
to
close
this,
so
the
only
Next
Step
there
would
be
a
better
understanding
of
how
many
projects
have
that
on
by
default.
So
some
data
work
there.
So
some
issues
to
note,
as
you
dig
in
here,
we
have
already
some
confidential
issues
that
are
tagged
for
verify.
P1
we're
starting
to
burn
down
some
of
the
back
end
of
those
security
issues
and
that's
what
those
are.
A
So
you
can
dig
in
there
and
take
a
look,
but
it
won't
hover
over
and
then
some
of
the
issues
here,
making
it
easier
to
understand
the
pipelines,
one
of
our
goals,
I'll
get
the
rest
of
the
goals
issues
plugged
in
here
as
well.
It
looks
like
I
have
some
cleanup
to
do
cost
factors
out
into
15,
8
shouldn't
be
in
15
and
six
and
the
object
model
realizes
on
the
merge
train
as
we're
thinking
about
timing
for
the
Milestone.
A
What
we
may
do
is
shift
some
of
the
work
that
doesn't
align
to
the
goals
out.
That'll,
give
us
time
and
space
to
go
back
into
the
CI
minutes,
epic
and
clean
up
any
of
the
lingering
Tech
debt.
That's
there
and
really
close
that
out,
so
that
we
have
solid
code
base
that
we
can
iterate
on
in
the
future
and
really
have
met
all
of
our
goals
and
don't
have
that
lingering
Tech
debt,
especially
the
Milestones
around
the
holidays,
so
15
7,
15
8..
A
That's
probably
going
to
be
the
focus
which
looking
into
then
15
7
the
big
thing.
The
big
theme
is
making
that
CI
job
token
more
useful
and
standard
so
with
the
work
to
enable
the
new
workflow
for
the
CI
job
token,
for
inbound
projects
enabling
inbound
projects
to
use
the
CI
job
token
and
run
pipelines
on
Mrs.
In
your
project.
We
want
to
make
that
secure,
CI
job
token,
a
default
for
new
projects,
so
this
is
going
to
be
the
issue
to
deliver
in
the
Milestone
goals.
A
As
always,
though,
meeting
our
reliability
slos-
and
we
want
to
see
this
is
impaired
to
an
issue
but
have
some
projects
that
have
that
CI
job
token
set
based
on
the
data
issue
that
we
had
back
in
1506.,
so
15
7
is
December,
I,
believe
if
I'm
doing
my
Milestone
and
Calendar
Math
right
so
already,
looking
like
a
pretty
slim
Milestone,
anticipating
some
folks
being
out
and
like
I,
said
getting
that
CI
ad
minute
work
done,
15
8!
You
can
expect
the
same
thing
so
again.
A
A
pretty
slim
Milestone,
we'll
probably
have
some
okr
issues
that
come
up
in
Q4
because
that's
when
that
will
be
that
we'll
be
working
on,
but
all
leaving
plenty
of
time
and
space
for
that
CN
minute,
work
to
finish
up
or
the
CI
job
token
work.
So
those
are
some
headlights
into
15,
6
and
15
7..
If
you
have
any
questions,
let
me
know:
I'll
be
uploading
this
to
unfiltered
here
shortly
and
post
to
the
slack
Channel
cheers.