►
From YouTube: GitLab 15.10: Kickoff - Verify:Runner
Description
Kickoff video for GitLab 15.10 for the Runner product categories:
https://about.gitlab.com/direction/verify/runner_saas/
https://about.gitlab.com/direction/verify/runner_fleet/
https://about.gitlab.com/direction/verify/runner_core/
B
A
Awesome
well
I'm,
so
happy
to
have
Gabriel
here
as
folks
that
have
been
looking
at
the
videos
might
know.
Typically
in
the
past
I
cover,
you
know
things
for
around
a
core
run.
A
SAS
and
Gina
do
I
look
at
Nick,
Edition
couples
running
Fleet,
but
Gabriel
is
taking
over
as
a
new
Runner,
SAS
PM,
so
I'm
super
excited
to
have
Gable
and
very
thankful
to
educate,
will
join
the
team.
So
today
we're
going
to
cover
the
15
or
10
Runner
group
iteration
plan
and
the
runner
group
is
comprised.
A
This
is
a
quick
recap.
It's
comprised
of
run
Accord,
Runner
SAS
and
run
a
fleet
and
again
Gabriel
is
a
piano.
So
let
me
just
jump
in
and
talk
a
bit
today.
I'll
try
to
do
my
best.
Junior
impression,
I'll
talk
a
bit
about
what's
happening
around
a
fleet
and
then
I
pass
it
over
to
Gabriel
the
chat
about
science.
A
It's
really
going
to
simplify
the
the
management
experience
long
term
and
also
also
simplifies
the
oil
experience.
So
we've
we
made
a
lot
of
actually
pretty
good
progress
on
it
in
59,
but
we're
not
quite
there.
So
1510
will
be
wrapping
up.
This
will
book
so
that,
at
least
in
the
admin
area,
then
you're
going
to
Creation
workflow.
Would
be
visible
and
would
be
available
as
part
of
the
15910
release.
A
So
that's
a
key
thing,
that's
happening,
and
so
that
I
want
to
think
category
and
15.10,
and
actually
some
of
that
work
will
create
well,
we'll
click
over
in
the
next
release
as
well,
because
we
have
to
be
doing,
we
will
have
to
be
adding
this
neuron
creation
workflow
for
our
group
views
and
for
our
project
views,
but
just
to
recap
in
1510
we're
looking
to
wrap
up
the
last
bit
of
work
so
that
the
creation
workflow
is
available
in
the
admin
area.
Runner
screen.
A
B
B
Perfect,
so
that's
our
Direction
page,
as
you
probably
know
we
updated
once
a
month
and
I'm
gonna
walk
you
through
just
quickly,
what's
happening
for
the
runner
SAS
topic
for
the
next
iteration.
You
can
see
it
mainly
here
on
what
we're
currently
working
working
on.
There's
two
topics
in
parallel:
we
are
working
on
a
top
priority.
For
us
right
now
is
to
do
some
background
work
for
our
Mac
OS
runners
to
really
push
for
making
it
available,
starting
with
limited
availability
and
then
later
General
availability
for
the
next
iteration.
B
We
will
work
together
with
our
beta
customers
to
get
the
transition
done
to
the
new
M1
chips
and
then
later
also
make
it
available
for
the
general
public
and
then
second
priority.
What
we
are
working
on
there
is
our
GPU
enabled
Runners
for
all
of
the
model.
Ops
customers
out
there,
perfect
I'll,
just
quickly
show
also
the
two
issues
we
have
for
both
of
these
topics.
Just
so
you
can
have
a
quick
look.
So
that's
the
first
one
for
our
Runners
Mac
OS.
A
Hey
thanks,
Google,
that's
super
exciting
to
see
all
the
new
capabilities
that
are
coming
over
from
the
SAS
team
and
in
just
in
chatting
with
Gable
I
know,
there's
tons
more
interesting
things.
That's
already
been
discussed
in
planned,
so
I'm
looking
forward
to
that.
So
let
me
start
sharing
my
screen
again
and
talk
a
bit
about.
What's
going
on
back
on,
104
see
if
we
get
a
screenshot
going.
A
All
right
so
just
to
recap
for
everyone,
so
we're
going
to
call
that's
the
of
course.
The
the
Engine
That
Could
the
get
that
one
application
itself
that
you
know
enables
the
GitHub,
CI
John
jobs
to
run
on
the
plethora
platforms
as
we
support
in
terms
of
new
features
well
in
terms
of
what
we're
working
on
first
in
1510.
A
So,
as
has
been
the
case
for
the
past,
at
least
two
or
three
released
two
or
three
months
actually,
and
even
beyond
that,
we've
been
heavily
focused
and
invested
in
working
on
reducing
our
backlog
of
age
bugs
and
that
priority
continues
in
15.10.
So
as
you're
looking
here
at
our
iteration
plan,
you'll
see.
B
A
All
right
thanks
so
yeah
so
for
one
Accord
as
you
look
here,
you'll
see
that
there's
a
heavy
waiting
towards
bug
work
right.
So
we
continued
about
this
for
the
past
three
or
six
months.
Actually,
we've
been
doing
a
lot
of
work
on
trying
to
work
through
our
back
level
of
age
bugs,
and
so
that
effort
continues
in
15.10
and
we're
making
progress
on
some
of
the
I
want
to
kind
of
turn
them
as
esoteric
bugs
that
negatively
impact
the
overall
experience
of
using
one
as
a
scale.
A
Things
really
hit
the
job
timeouts
things
related
authentication
phase,
where
I
could
use
executor
and
so
on,
and
so
that's
going
to
be
a
primary
focus
for
us.
N15910
and
you'll
see
that
happening
as
well
as
we
move
into
team
one
and
into
the
next
releases.
We'll
continue
that
that
focus
on
working
through
some
of
the
more
in
that
and
more
intricate
bugs
that
are
currently
in
our
backlog
in
terms
of
new
features
and
capabilities.
A
The
Running
part
Timeout
on
an
openshift
kubernetes
cluster.
The
other
important
work
as
well
that's
happening
in
core
and
that
will
pick
up
traction
as
we
move
into
15.
1,
1
and
160
is
the
next
Runner
Auto
scaling
architecture
we'll
be
talking
about
this
for
a
bit
and
just
to
recap
for
everyone.
This
is
the
replacement
for
our
Docker
machine
based
autoscaler.
A
That's
proven
very
reliable
and
sort
of
very,
very
valuable
to
a
number
of
customers,
we're
pretty
close
on
on
getting
ready
to
release
the
next
Auto
skiing
Solution
on
AWS
and
specifically
the
Alpha
version
of
what
we're
calling
our
AWS
ec2
fitting
plugin.
Just
to
write.
To
recap:
this
oil
scaling
solution
kind
of
refunds,
the
approach
that
we
that
we
currently
have
a
double
machine
because
it
relies
on
new
technology
and
relies
heavily
on
the
abstraction
layers
that
are
currently
available
on
the
clock.
A
Revised
expression
layers
such
as
instance,
groups
all
the
scaling
groups
on
the
file
providers,
and
so
we'll
have
much
more
to
share
on
that
feature
set
as
it
rolls
out.
But
the
goal
would
be
to
get
the
output
version
of
The
Next
One,
auto
scanning
solution,
specifically
for
Amazon
web
services
and
to
be
more
to
me
even
more
specific
or
on
virtual
machine
Auto
scale
on
Amazon
web
services.
A
Ec2
instances
would
be
the
goal
for
us
in
1510,
so
in
terms
of
in-depth
capabilities,
we're
adding
more
features
for
the
Q
links,
executor
and
just
to
kind
of
make
a
note
on
that
in
fy24
and
Runner
core.
In
addition
to
a
lot
of
investment
to
burn
down
our
about
backlog,
the
other
significant
investment
area
for
us
will
be
on
the
kubernetes
executor.