►
From YouTube: Pipeline Execution 15.3 Refinement/Planning Kickoff
Description
This video walks through the theme and goals for the 15.3 milestone that the Pipeline Execution team will be working towards.
The 15.3 planning issue can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/104
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
This
is
the
15.3
refinement,
kickoff
or
planning
kickoff,
I'm
already
sharing
my
screen
and
have
the
15-3
planning
issue
open.
It's
pretty
full,
it's
overly
full
right
now,
so
we're
going
to
be
doing
some
work
to
reduce
that.
But
I
wanted
to
call
out
what
we
have
so
far.
So
our
theme
for
the
milestone
is
to
improve
the
pipeline
experience
or
the
experience
of
running
pipelines
for
open
source
program
project
contributors,
it's
kind
of
a
mouthful,
so
our
goals
for
the
milestone
that
lead
up
to
that
theme
are
built.
A
In
that
theme,
our
number
one
goal,
as
it
always
has
been
the
last
couple
of
quarters
or
has
it
has
been,
and
as
it's
going
to
continue
to
be-
is
to
meet
our
reliability
issues
and
those
are
all
verified.
P1,
synthetic
security,
infradev
and
application
limits
as
we're
working
on
stability
and
reliability
for
the
platform.
A
So
the
second
part
of
that
is
really
what
leads
up
to
the
theme
itself
of
making
that
pipeline
or
the
experience
of
wedding
pipelines
if
you're
a
gitland,
open
source
program,
project
maintainer
or
someone
who's
contributing
to
one
of
those
making
that
experience
better
and
not
costly
for
you.
So
part
of
that
is
a
reduced
cost
factor
for
those
oss
plans
just
so
they
can
get
a
few
more
minutes
as
we're
working
through
some
of
the
kinks
of
counting
all
of
the
public.
A
All
the
minutes
on
public
projects,
another
one
of
those
is
to
reduce
use
a
reduced
cost
factor
for
public
forks
of
public
projects
so
for
contributors
to
public
projects,
especially
those
open
source
projects,
they're
not
burning
through
all
of
their
minutes
in
a
single
pipeline.
It's
especially
important
for
the
gitlab
project,
which
is
another
issue
that
we're
working
on
in
15-2.
A
Some
other
usability
things
that
I
wanted
to
call
out.
One
is
the
back-end
work
that
makes
it
easier
to
understand
and
differentiate,
merge,
request
pipelines.
This
is
a
precursor
to
front-end
work.
That'll
come
maybe
in
15-3,
probably
in
15
4
of
fixing.
Some
of
those
labels
of
what
the
heck
is
a
detached
pipeline,
some
things
like
that,
you
can
read
more
about
it
in
the
issues
and
our
ui
for
the
merge
request,
widget
to
rebase
without
running
ci.
A
This
is
really
helpful
if
you
don't
want
to
run
a
pipeline
as
you
rebase,
if
you're
way
behind
on
your
branch
as
you're
contributing
to
an
open
source
project,
for
instance,
so
this
will
help
folks
make
sure
that
their
branches
are
up
to
date
without
having
to
run
the
ci
or
the
pipeline
every
single
time.
They
do
that.
You
can
do
it
through
the
api
today,
but
this
just
makes
it
a
really
nice
experience
to
do
it
through
the
ui
and
the
other
thing
I'm
going
to
call
out
the
stretch.
A
Goal
are
a
couple
of
spikes
that
we
have
in
the
milestones,
so
these
are
smaller
than
what
would
be
a
normal
issue,
we're
going
to
time
box
those
to
about
a
day
hopefully.
But
we'll
talk
about
that
with
the
ems.
The
first
one
is
investigation
into
enabling
the
ci
token
permission
flow.
So
it's
unblocking
an
issue
that
is
a
big
one
for
us
around
the
security
theme
that
we
have
for
the
year
and
that
opens
up
a
lot
of
use.
A
Cases
for
us
like
enabling
things
like
depend
about
to
run
pipelines
in
your
project
and
trust
that
only
dependable
is
going
to
be
able
to
do
that.
They're,
the
only
one
who
is
going
to
have
access
to
those
secrets
and
really
just
within
the
scope
of
that
ephemeral
token,
so
those
things
will
rotate
automatically
and
so
there's
it
just
makes
that
process
a
whole
lot
more
secure.
The
other
is
trying
to
figure
out
what
the
what
the
blockers
are
rather
and
get
unblocked.
A
This
review
after
script,
we'd
love
to
get
a
poc
done
right
now
that
is
scheduled
for
15.5.
So
if
we
work
on
this
in
15-3,
that
gives
us
some
time
also
in
15
4,
to
work
on
the
proof
of
concept
and
then
hopefully
roll
that
out
it's
one
of
our
most
popular
issues.
It's
something
that
the
community,
the
wider
community,
has
really
wanted
for
a
long
time.
So
I
think
we
really
benefit
our
user
base
by
solving
this
problem
once
and
for
all
and
getting
this
ruled
out.
A
So
as
we
look
at
our
breakdown
of
the
verified,
p1s
p2s
p3s,
you
can
see
a
lot
is
in
here
we're
targeting
somewhere
between
30
and
40
issues
in
the
milestone
and
then
something
new
as
part
of
our
workflow.
I
wanted
to
call
out.
Is
that
issue
breakdown
so
for
mark
and
sam
vitica
and
richard
what
I've
targeted
percentage-wise-
and
this
is
open
for
discussion
of
course,
is
25
feature
25
above
50
maintenance.
So
you
can
see
that
we're
getting
pretty
close
to
that
in
our
breakdown.
A
A
So
I
will
update
this
table
as
the
milestone
goes
on
and
as
we
get
closer
to
it,
so
that
we
can
be
confident
that
we're
going
to
hit
our
goals
for
how
much
we're
going
to
deliver
and
the
wider
community
is
confidence
that
we're
going
to
deliver
issues
when
we
say
we
do
so
that
is
our
kickoff,
just
a
quick
walkthrough
of
our
planning
issue.
This
is
always
going
to
be
evolving.
It's
probably
going
to
change
before
the
video
is
done
uploading.
A
So
if
you
have
questions,
please
ping
me
in
the
channel
or
leave
a
comment
on
the
issue.
Thanks
dean.