►
From YouTube: GitLab 15.0 Kickoff:Verify-Runner
Description
GitLab Runner kickoff video for GitLab 15.0
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28762
A
Hey
everyone
very
eastman
here,
product
manager
for
get
blogging
joined
with
by
junior
doyle
designer
for
gitlab
as
well
get
labrunner
and
some
other
groups
as
well
anyway.
Today
is
the
50.00
team,
iteration
kickoff
video,
so
you
know
I'll
pass
it
over
to
you
to
discuss
some
of
the
cool
things
that's
being
worked
on
in
the
run
of
fleet
category.
B
All
right
so
I'll,
walk
through
what
our
development
team
is
going
to
be
taking
on
for
runner
fleet
and
just
as
a
reminder,
runner
fleet
is
around
managing
large
pools
of
runners
in
the
avenue
and
in
the
group
view.
So
today
we're
for
15-0
we're
focusing
on
automatically
purging
runners
that
have
been
inactive
for
a
long
time.
A
lot
of
customers
are
really
interested
in
this
and
we're
gonna
start
with
just
allowing
for
this
to
be
done
in
the
api.
B
B
There
is
an
edit
view
today
that
you,
if
you're
an
admin
at
the
instance
level,
you
can
edit
your
runners,
including
like
configuration
job
timeout
stuff
like
that,
and
then
editing
the
assigned
projects
and
we're
just
ramping
that
up
to
be
more
pajamas
compliant
and
then
making
it
easier
to
use.
In
general
and
then
the
last
two
are
adding
a
token
reset
audit
event
when
a
runner's
registration
token
is
reset.
B
We
have
the
capability
to
track
some
events
with
runners
today,
but
it's
pretty
limited
right
now,
so
we
are
adding
the
ability
to
see
when
you
reset
a
runner's
registration
token
in
that
audit
stream,
so
you'll
be
able
to
see
that
and
then
lastly,
we're
working
on
creating
a
clear
route
project
for
project
runners.
Today,
when
you
have
a
product
runner,
you
can
share
it
across
many
projects
and
there's
not
really
a
capability
to
be
able
to
see
where
that
runner
originated
from.
B
So
we're
going
to
make
that
clear
with
adding
a
root
project
and
that's
going
to
be
in
the
back
end
first.
So
then
we'll
show
it
in
the
in
the
front
end
which
carries
over
to
my
ux
issues
as
well,
which
I'll
jump
into
the
association
column
that
we're
going
to
be
adding
to
the
runners
table
in
the
admin
area.
B
We
don't
show
that
at
all
in
the
table
today
in
the
admin
area,
so
we'd
like
to
add
this
new
column
for
displaying
what
the
association
of
that
runner
is
and
then,
if
it's
in
a
shared
runner,
for
example,
we
would
say
that
the
association
is
instance
and
the
other
issue
I'll
be
working
on
is
improving
the
runner
table
design.
If
you
have
seen
our
admin
table
today,
it's
there's
a
lot
of
information
on
it.
A
A
So
we
have
a
number
of
removals
planned
in
15.00
and
they're
under
this
section
here,
so
you
can
take
a
look
at
what's
planned,
specifically
for
runner
core,
as
it
relates
to
removals
in
15.00,
and
this
obviously
will
be
communicated
as
part
of
our
regular
release
process
that
150
network
comes
out
as
well.
But
here
are
the
lists
of
things
for
15.
that
we're
removing
in
terms
of
new
development,
that's
happening
in
ronald
corn5o,
because
we
have
to
do
breaking
changes.
So
that's
taking
a
part
of
our
capacity.
A
The
other
focus
area
from
an
investment
capacity
perspective,
is
on
bugs
and
and
security
issues
first
and
then
moving
into
resolving
our
age
backlog
of
s2
bugs.
So
that's
what
you
see
here
in
three
things
that
are
currently
on
deck
are
some
security
issues.
The
security
bugs
are
working
on
and
then
the
other
thing
that
we're
working
on
or
I'm
hoping
to
get
to
in
15-0
from
above
perspective,
is
making
progress
on
the
specific
documentary
preparation
fail,
bug
it's
one
of
many
age
severity,
2
bugs
that
we
want
to
get.
A
We
want
to
eliminate
from
the
background
in
terms
of
new
features,
we
don't
have
a
significant
number
of
new
features
planned
for
15.00,
but
one
thing
that
we
do
hope
to
ship
n15.0,
which
coincides
with
some
work.
That's
happening
over
with
our
alliance
partners
is
adding
support
for
red
hat's
part
man
to
get
lab
runners
an
executive
type.
A
A
15,
though
the
team's
main
focus
is
on
transitioning
the
get
love
sas
for
mac
os
runners.
This
is
basically,
if
you
are
a
customer
on
gitlab
sas
and
you
want
to
take
advantage
of
a
mac
os,
build
environment
natively
on
gitlab
sas.
Today
we
have
been
for
the
past
12
months
or
so
offering
customers
and
open
source
customers
access
to
our
beta
program
and
15-0.
A
So,
as
things
progress
over
the
next
few
weeks
towards
the
fifth
grade
or
release,
that's
when
we
will,
as
15.
comes
up
we'll,
have
the
related
blog
posts
with
additional
information
in
terms
of
how
to
use
the
pricing
structure
and
those
types
of
things,
because
the
main
goal
for
us,
I'm
professional
foreign,
is
getting
and
they
get
left
sides
for
mac
os
la
shipped
to
customers.