►
From YouTube: GitLab 15.2 Kickoff - Verify:Runner
Description
15.2 kickoff video for GitLab Runner.
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28888
A
B
Okay,
awesome
I'll
start
sharing
what
we
have
for
this
milestone,
so
here's
our
plan
for
the
runner
fleet
team
for
15.2
and
I'm
going
to
start
just
going
through
some
of
the
front-end
issues
and
a
lot
of
the
issues
that
we're
taking
on
this
milestone
are
related
to
our
okrs,
which
are
to
improve
the
sus
score
that
we
have
for
git
lab.
B
So
one
of
those
is
bulk,
deleting
runners
from
for
the
admin
view,
and
there
is
some
back
end
work
that
needs
to
be
done
for
this,
and
basically
it
will
just
allow
you
to
be
able
to
delete
many
runners
at
the
same
time,
this
really
goes
hand
in
hand
with
our
stale
status.
So
if
your
runner
hasn't
been
used
over
in
90
days,
then
we
would
recommend
you
delete
it.
B
So
today,
when
you
have
a
project
runner,
you
can
share
it
with
other
projects,
but
there's
not
really
any
way
of
determining
who
was
the
one
which
project
that
runner
originated
from.
So
this
would
allow
us
to
declare
like
an
owner
project
for
that
runner
so
that
you
have
a
point
of
contact
to
go
to.
B
If
you
wanted
to
change
the
change,
the
configuration
or
whatnot
on
the
ux
side,
we're
going
to
be
starting
prep
for
category
maturity
for
runner
fleet,
so
we'll
be
recruiting
in
15-2
and
getting
external
customers
to
be
able
to
talk
to
and
run
our
category
maturity
plan
for
and
then
and
by
the
way,
we're
shooting
for
complete
there
we're
at
bible
right
now,
and
then
we
also
are
wrapping
up
solution,
validation
for
our
new
runner
view.
This
is
really
just
because
we're
carrying
out
moderated
sessions
with
customers
and
15
too.
B
A
Absolutely
thank
you.
That's
super
awesome
and,
as
always,
just
so
much
interesting
and
cool
work
happening
and
they're
on
a
free
category
that
we
made
boundless
strides
in
both
the
experience
and
the
admin
level
and
the
group
level
over
the
past
few
months,
and
so
I'm
looking
forward
to
see
what
we
do
in
the
back
end
of
this
year.
A
in
terms
of
new
features,
I'm
going
to
touch
just
on
one.
The
key
new
feature
that
we'll
be
looking
to
implement
in
the
ronald
core
code
base
in
15.2.
Is
this
heavily
requested
feature
over
the
past
few
years,
which
basically
is
allowing
users
to
specify
a
root?
A
Folder
for
artifacts
and
the
value
propositions
that
to
simplify
today
you
do
as
a
user
when
you
upload
artifacts
to
gitlab
the
path
is
hard
quoted
or
predefined,
and
what
users
want
to
do
is
when
they're
able
to
specify
specific
folder
directories
in
order
to
create
a
zip
or
tar
file,
and
so
the
proposal
at
the
moment
is
to
then
allow
during
the
creation
of
the
uncrack
process,
allow
the
user
to
specify
a
root
directory,
and
so
then,
with
that
feature
in
place,
you
can
zip
up
a
specific
path.
A
If
you
will,
in
terms
of
you
know,
I
want
to
use
this
palette.
I
want
to
include
this
path
and
the
files
on
this
path
which
I've
defined
as
my
root
in
my
zip
or
tar
file.
So
this
is
a
heavily
requested
feature.
It
has
over
235
uploads,
it's
been
out
there
for
a
bit.
We
believe
we
have
a
a
path
forward
with
implementing
this.
Finally,
and
we're
going
to
code
base
here
in
152,
so
super
excited
about
about
that.
A
Moving
on
to
run
assass,
we
don't
have
any
new
features
planned
to
ship
in
15-2
in
renaissance,
we're
spending
most
of
our
time
in
52
all
of
our
time
in
15-2,
really
on
working
through
a
number
of
tech,
debt
items,
and
so
everything
you
see
here
in
our
15
to
iteration
plan,
which
is
publicly
available
and
open
for
everyone
to
take
a
look
at
as
we
click
through
these
issues,
they're
mostly
on
maintenance
activity
related
to
ensuring
that
we
can
deliver
a
reliable
and
scalable
platform
for
runner
sas.
A
So
that's
it
in
terms
of
new
features
for
ronald
caller.
The
one
the
main
thing
to
look
at
for
n52
is
the
ability
to
specify
a
root
folder
for
artifacts
and
then
on
the
result
side
again
we're
doing
some
things
in
terms
of
technical
debt
and
just
before
we
wrap
up.
I
just
want
to
get
call
folks's
attention
because
we
haven't
talked
about
it
in
a
bit.
A
We
do
have
category
direction
pages
for
each
of
these
categories
and
we
revise
these
pages
at
the
end
of
each
release,
milestone
so
there's
a
page
share
under
above
the
github.com
slash
direction,
verify
for
run
a
core
there's
one
for
rona
sas
and
then
there's
one
for
runner
fleet,
and
so
when
you
go
to
each
of
these
pages,
it
gives
you
a
high
level
view
of
some
of
the
big
ticket
items,
we're
planning
some
of
the
strategic
items.
A
We
are
planning
per
quarter,
so
you
can
get
like
this
high
level
sort
of
like
20
000
foot
view
if
you
will
of
where
things
are
headed
and
then,
as
we
do
in
these
iteration
kickoff
meetings.
You've
kind
of
seen
what's
actually
happening
from
a
tactical
perspective
in
each
milestone.
A
So
that's
it
for
15.2
looking
forward
to
to
a
great
release
anything
else
wrap
up
before
we
wrap
up
your
juno.