►
From YouTube: Pipeline Execution 15.9 Refinement/Planning Kickoff
Description
This video walks through the theme and goals for the 15.9 milestone that the Pipeline Execution team will be working towards.
The 15.9 planning issue can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/124
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
So
our
theme
around
15
9,
which
will
deliver
in
February
of
2023,
is
more
CI
minute
and
CI
job
token
visibility,
so
really
adding
capability
to
show
users
what
they're
doing
so.
Our
goals
are
meeting
reliability,
slos
our
reliability
issue
slrs
as
always,
and
then
digging
deeper
into
that.
We
have
an
issue
to
add
the
CI
job.
A
Token
events
to
the
audit
logs,
specifically
that's
enabling
that
CA
that
new
inbound
workflow
for
CI
job
token,
so
that
our
friends
and
security
and
compliance
or
folks
in
security
and
compliance
can
see
that
in
the
audit
log,
if
they're,
an
ultimate
user
which
is
really
exciting.
So
I
can
see
when
projects
started
to
allow
things
inbound
and
then
improving
visibility
of
the
CI
minute
usage.
A
So
just
a
couple
of
verify,
P1
p2p3's
been
here
so
far.
It's
pretty
slim
Milestone
right
now,
we've
been
trying
to
actively
take
things
out
of
or
not
push
things
forward
through
milestones
and
really
just
put
them
into
the
backlog,
and
then
every
Milestone
we
evaluate
once
the
top
impactful
things
our
most
impactful
things,
and
what
can
we
put
into
the
Milestone?
So
you're
going
to
see
more
of
that
and
then
I've
started.
A
The
comment
thread
already
about
the
cross-functional
cross-functional
issue,
prioritization
or
issue
breakdown,
so
normal
thread
here
is
talking
about
what
we
have
open
for
security.
Our
discipline
availability
we're
back
into
the
green
yay.
So
what
I'm
proposing
is
roughly
the
same?
Seven,
seven
six.
A
As
far
as
the
number
of
issues
which
works
out
roughly
to
30
through
30
through
33,
depending
on
how
you
do
the
math
for
bug
maintenance
feature,
that's
going
to
really
allow
us
to
focus
in
on
this
up
a
couple
of
verify,
verify
P1
and
P2
issues
and
then
a
call
out
to
Mary,
Scott
and
Gregor.
If
you
can
help
time
in
on
what
are
the
top
themes
and
goals
for
59
for
continuous
integration
and
scaling,
we
can
do
that
anything
here
within
the
issue.
A
I
just
want
to
start
to
better
land
for
those,
especially
in
the
functional
prioritization,
as
we
think
about
pulling
those
out
and
really
making
sure
that
the
the
split
is
indicative
of
CI
and
merge
trained
categories
and
what
the
main
pipeline
execution
team
is
working
on
and
then
thinking
about
how
maintenance
really
is
driving
the
data
scaling,
category
and
network.
So
if
you
can
comment
here
would
be
great
thanks.