►
From YouTube: Pipeline Execution 14.7 Refinement/Planning Kickoff
Description
This video walks through the theme and goals for the 14.7 milestone that the Pipeline Execution team will be working towards.
The issue itself can be found here: https://gitlab.com/gitlab-org/ci-cd/pipeline-execution/-/issues/82
The needs weight issue for 14.7 can be found here: https://gitlab.com/gitlab-org/gitlab/-/issues/346718
A
Hey
team
wanted
to
record
our
refinement
kickoff
for
14.7
the
things
that
a
lot
of
these
are
already
ready
to
go,
but
just
to
get
headlights
on
what's
coming
down
the
pike
for
the
next
release
or
the
next
milestone.
Rather
so,
the
goals
are
on
fourteen
seven.
We
want
to
deliver
the
hard
cn
limits
for
public
projects,
there's
a
couple
of
things
that
lead
into
that
one
is
reducing
the
cost
factor
for
assessed
contributions.
A
That,
in
turn
has
dependency
on
some
issues
in
14
6.,
both
within
our
team
and
within
the
enablement
team.
But
that's
really
our
biggest
goal
for
the
our
biggest
theme
and
goal
for
14
7
is
around
adding
continuing
to
add
that
friction
for
crypto
miners.
So
they
can't
abuse
the
free
ci
minutes,
while
also
enabling
oss
projects
to
really
continue
to
thrive
on
gitlab.com
and
have
a
great
experience
once
we've
identified
them
and
unlocking
all
the
power
of
the
platform
for
them.
A
So
those
are
really
the
the
two
big
things
in
our
verified:
p
ones.
We
have
a
couple
other
verified,
p
ones
that
are
stacked
up
behind,
that
that
contribute
towards
our
quarterly
okrs
and
burning
down
some
tech
debt
there.
All
of
those
are
all
backend
issues,
so
those
are
all
gonna
fall
to
the
back
end.
A
Folks,
we
don't
have
any
verified,
p
ones
with
the
front
end
label
on
them
for
the
current
milestone,
but
a
couple
of
the
verified
p2s
are
front,
end,
enabled
issues
or
front
end
issues,
rather
rearranging
that
pipeline
index
page
layout
to
create
some
more
space.
We
do
want
to
deliver
on
that.
I
know
that
we've
gone
back
and
done
a
little
bit
of
additional
research
validated
some
use
cases.
A
I
think
that
we're
in
a
good
spot
to
move
forward
with
our
initial
goals
on
that
and
know
that
we
have
more
research
and
potentially
other
experience
to
address
some
of
those
other
jobs
to
be
done
where
users
were
using
the
pipeline
page.
That
may
be
ways
that
we
hadn't
anticipated
or
expected
that
we'll
need
to
solve
for
that
job
to
be
done
or
deliver
on
that
in
the
future.
A
The
other
one
I
wanted
to
call
out
is
assigning
some
custom
map
text
targets
around
the
ci
end
points.
This
is
going
to
require
a
little
bit
of
work
from
us
and
just
making
sure
that
we
understand
where's
the
right
threshold
for
those
either
one
second
or
five
seconds,
because
those
are
the
buckets
that
we
can
work
with
and
ensuring
that
we're
delivering
performant
experience
to
customers
really
that
they
are
getting
the
experience
that
they
expect
and
that
we're
not
causing.
A
You
know
business
critical
problems
downstream,
as
people
are
using
gitlab
for
their
ci.
So
that's
gonna
be
an
interesting
research
and
implementation
issue,
and
that
is
a
verified
p2
for
us.
Beyond
that
we
have
a
couple
of
things
here
that
you
can
link
into
nothing
for
infradev.
We
have
an
ongoing
engineering
allocation
that
drew
and
marius
are
part
of
and
are
going
to
be
working
on
those
issues,
I
didn't
say
anything
with
a
feature
flag,
that's
needed,
but
feel
free
to
go
and
edit.
This
issue
add
things
there.
A
Richard
didn't
see
anything
in
quality
as
far
as
new
tests
need
to
develop
again
feel
free
to
dump
those
in
here
same
around
docs
improvements,
and
if
you
want
to
check
out
what's
coming
from
ux
and
design,
you
can
feel
free
to
click
into
the
epic
that
we
use
to
track
that
as
vtk
is
continuing
to
work
on
some
new
excuse
me
new
experience
and
solution,
validation,
issues
within
fourteen
seven
and
looking
forward
into
fourteen
eight
fourteen
nine.
So
that's
the
just
on
fourteen
seven.
A
A
lot
of
these
already
have
weight.
I've
also
created
a
needs
weight
issue
to
work
on
during
fourteen
seven
so
that
we
can
start
picking
things
up
and
looking
at
them
validating
that
we
have
the
right,
solid
proposals
and
the
right
number
of
issues
created
for
things
and
I'll
link
to
that
in
the
in
the
video
description
here
as
well
shared
in
the
channel.