►
From YouTube: GitLab 15.3 Kickoff - Verify:Runner
Description
Release kickoff video for Runner group features planned for GitLab 15.3.
Runner 15.3 iteration plan: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28923
Runner Core Direction: https://about.gitlab.com/direction/verify/runner_core/
Runner SaaS Direction: https://about.gitlab.com/direction/verify/runner_saas/
Runner Fleet Direction: https://about.gitlab.com/direction/verify/runner_fleet/
A
Hey
everyone
welcome
to
the
get
five
runner
150.3
kickoff
video
darren,
eastman
your
product
manager
to
get
that
gonna
call.
Assassin's
creed
joined
by
junior
our
product
design
lead
so
we'll
go
ahead
and
jump
right
into
it,
and
gina
will
share
his
screen
on
and
chat
with
you
about
the
great
new
features
and
capabilities.
That's
coming
in
on
a
fleet
in
15.3
gina.
B
So
just
as
a
reminder,
the
runner
fleet
category
provides
users
who
have
large
fleets
of
runners
with
an
overall
glance
of
all
of
their
runners
at
once
and
provides
a
bunch
of
different
management
capabilities
and
then
in
the
future,
we're
shooting
to
provide
analytics
of
your
fleet
of
runners.
So
it
makes
it
easier
to
manage
all
of
them
and
for
this
for
15
30,
we
are
working
on
a
lot
of
features
to
improve
usability,
specifically
around
runner
version
management.
B
B
So
currently,
when
you
have
project
runners,
you
can
assign
them
to
multiple
projects
and
it
that
makes
it
difficult
to
be
able
to
find
where
that
runner
originated
from
which
project
owns
it
in
that
way,
so
that
sometimes
makes
it
more
difficult
to
manage
them
as
well.
So
we're
gonna
be
adding
this
root
project,
so
you
have
more
insight
into
who
the
owner
is
and
then
on
the
user
experience
side.
B
We
are
working
on
the
group
runners
issue
where
today
we're
only
displaying
that
the
runners
that
are
created
by
that
group,
so
you,
if
you're,
going
into
your
into
your
group
and
then
go
into
the
runners
page,
we
don't
show
you
all
of
the
runners
that
are
available
to
that
group.
So,
like
all
the
shared
runners
available
to
you
all
the
subgroup
runners,
everything
like
that,
so
we
want
to
be
able
to
display
those
so
that
one
there's
more
discoverability
in
those
and
two.
B
If
you
were
to
need
to
set
up
a
runner,
you
would
know
all
the
ones
that
already
exist
and
that
are
available
to
you
and
then
the
other
one
that
the
uf
team
is
working
on
is
the
category
maturity
scorecard
for
runner
fleet.
So
last
milestone.
We
did
recruiting
for
this,
and
this
milestone
will
be
focusing
on
actually
running
the
sessions
with
real
users
and
being
able
to
evaluate
the
maturity
of
our
category
and
hopefully
move
up
in
maturity,
and
that
is
it
from
the
runner
fleet
side.
Darren
I'll
pass
it
to
you,
hey.
A
A
They
were
desperately
needing
this
this
capability
because
of
the
number
of
runs
that
gets
created
automatically
when
they're
testing
out
auto
scaling
with
the
cuban
executives.
So
the
bug
delete
feature
is
super
important
for
for
a
lot
of
different
use
cases.
So
it's
really
excited
to
see
that
coming
in
hey.
A
It
was
in
1501,
we
released
this
as
a
beta
and
since
then,
in
the
last
couple
of
weeks,
we
have
confirmed
that
the
latest
partner
binary
with
the
fixes
that
we've
worked
on
with
our
red
hat
alliance
partners,
actually
solve
all
of
our
issues.
So
we
are
very
confident
we'll
wrap
up
the
world
and
in
1503
you
will
be
able
to
use
spartan
as
a
fully
supported
drop-in
replacement,
with
github
runner
in
place
of
docker.
So
we're
super
psyched
to
see
that
and
then
we'll
continue.
A
Obviously,
as
we
as
we
move
forward,
iterating
on
that
capability
set,
so
pog
man
is
dropping,
replace,
but
that's
coming
in
one
core
and
15-3.
The
other
thing
I
just
want
to
call
out
as
well.
It's
happening
in
15-3
and
that's
part
of
our
longer-term
strategies
and
shouldn't
jump
into
this
set
of
capabilities
here
and
it's
highlighted
or
the
the
preamble
is
next
runner
token
architecture
and
if
you
click
into
them
now
clicking
this,
you
can
have
a
look.
A
A
We're
going
on
changing
out
the
or
taking
a
new
approach
to
the
runner
token
architecture
in
terms
of
run
assassins
is
specifically
focused
on
the
gitlab
sas
runners
that
are
available
for
you,
as
a
customer
or
user
on
getlab.com
just
to
recreate,
if
you're
a
github.com
user.
Today.
If
this
is
your
first
time
onboarding
to
gitlab
gitlab.com,
you
do
not
have
to
set
up
everyone
to
start
taking
advantage
of
the
great
capabilities.
That's
there
with
gitlab
ci
right.
A
The
github
sas
runners
that
we
currently
have
in
place
today
will
automatically
kick
off
your
workflows
on
a
linux
os
machine
with
our
docker
executor.
We
also
have
on
github.com
runners
that
will
run
your
workloads
on
in
windows,
shutter,
executive
windows,
workflows.
You
can
also
run
those
right
away
on
git
fabric
on
without
having
to
set
up
your
own
runners.
A
What
we're
doing
in
15-3
is
we're,
finally
starting
to
pivot
and
expand
in
the
and
work
towards
expanding
the
footprint
in
terms
of
various
resource
types,
I.e
more
compute
choices
for
the
linux
runners
with
our
docker
executives
and
github.com.
So
if
things
go
well
in
15.2
and
593
and
cross
my
fingers
that
we
can
actually
make
meaningful
traction
on
this,
you'll
start
seeing
us
offering
new
machine
types
for
those
gitlab
size,
linux,
runners
and
specifically,
what
we
have
on
deck
of
15.3.
A
We're
gonna
start
off
with
just
some
gcp
n1
standard,
twos
and
standard
four
virtual
machines
and
then
once
we've
gotten
sort
of
that
going
you'll
see
us
kind
of
evolve
that
offer
set
later
on
this
year
and
the
next
day
we'll
start
opening
up
the
aperture
more
and
giving
you
more
computing
choice
on
github.com
and
just
to
kind
of
add
on
one
little
additional
piece
of
clarification
or
information.
For
for
those
folks
that
don't
have
the
full
contacts
our
getlab.com
runner
fleet
is
hosted
on
google
cloud.
A
So
we
take
advantage
of
all
of
the
scaling
of
the
google
cloud
platform,
all
of
the
security,
that's
inherent
in
the
google
cloud
platform
and,
of
course,
all
of
the
various
types
of
compute
offerings
that
are
available
in
the
google
cloud
platform.
So
until
now
we
have
restricted
the
google
compute
resource
types
that
we've
offered.
But,
as
I
mentioned
now,
we're
heading
we're
sending
the
pivot
and
open
up
that
aperture.
A
Then
we've
got
some
other
things,
we're
working
on
as
well
in
terms
of
capabilities
and
reliability.
Work
for
renaissance,
looking
at
some
things
with
regards
providing
some
additional
insights
into
network
health
between
our
gitlab.com
runners,
for
example,
and
connections
to
external
container
registries.
We've
got
a
number
of
large
customers
on
gitlab.com
that
they
don't
want.
They
don't
always
rely
on
our
github
container
registry.
A
So
we've
got
tons
of
work
planned
there
in
53
for
run
assass
and
just
in
closing.
I
just
want
to
call
your
attention
to
just
kind
of
two
kind
of
points
and
wrapping
up
in
each
of
these
kickoff
videos.
We
talk
about
specifically
the
features
that
we're
actively
working
on.
We
feel
pretty
confident
will
shift
in
that
next
release,
and
so
that's
what
you
see
here
on
the
screen
is
that
iteration
plan
you
can
comment
on
this
iteration
plan.
A
You
get
your
feel
free
to
take
a
look
at
it
and
click
through
on
any
of
the
issues
here
and
make
comments.
If
you
want
to
kind
of
step
back
a
bit
and
kind
of
take
a
broader
look
or
20
000
foot
level
view,
if
you
will
at
our
long
term
strategy
to
do
that,
you
want
to
go
to
our
direction
pages,
and
so
we've
got
direction
pages
for
run.
A
call
which
is
here
about
that
getclub.com
directions
very
far
on
the
core.
A
We've
got
the
same
thing
for
runner
sas
and
the
same
thing
for
runner
fleet
and
please
take
a
look
drop
us
in
any
comments
or
feedback
that
you
have.
But
the
idea
is
that
we're
trying
to
provide
you
that
high
level
view
of
just
broadly
speaking,
a
our
vision
for
each
of
these
product
categories
under
the
runner
umbrella
and
then
b,
generally
speaking,
where
things
are
going
over
the
next
few
quarters
and
into
the
next
fiscal
year
kind
of
just
broad
strokes
of
our
long-term
strategy.