►
From YouTube: GitLab 15.8 Kickoff - Verify:Runner
Description
Release kickoff video for Verify: Runner and Runner SaaS.
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/29087
A
A
Another
feature
we'll
be
working
on
is
within
the
admin
area,
our
navigations
a
little
bit
behind
speed.
So
even
in
a
project
you
know
we
have
CI
CD
as
its
own
item
and
same
with
groups.
Now
so
we'll
be
improving
that
consistency
by
moving
Runners
into
its
own
cicd
group
in
the
admin
area
and
we'll
move
any
other
items
that
belong
there
like
jobs,
so
that
it's
more
consistent
for
you
to
go
between
different
views.
A
So
one
of
the
things
that
we
have
to
do
there
is
edit
the
API
so
that
we
are
able
to
do
that
so
you'll
see
you
won't
see
much
difference
in
the
UI
there
yet.
But
we
want
to
do
this
so
that
we
can
concentrate
more
on
that
area,
since
we
haven't
done
that
much
because
we've
been
probably
trading
on
admin
and
group
areas
for
runners
so
far
on
the
ux
side
of
things.
A
A
So
I
want
to
take
some
time
to
review
that
feedback
and
kind
of
be
able
to
sort
it
out,
make
sure
that
we
have
issues
that
will
cover
it
and
match
it
up
with
some
of
the
sus
results
that
we
got
from
our
last
quarters
around
Runners,
and
this
will
really
help
us
move
forward
and
validate
the
features
that
we'll
be
creating
in
the
future
and
then
before
I
pass
it
off
to
Darren.
We
did
separate
officially
our
two
groups
within
Runner.
A
Now
we
have
the
runner
group
and
we
have
Runner
SAS
as
its
own
group
and
so
going
forward.
We
will
be
talking
about
Runner,
Fleet
and
Runner
core,
which
is
in
the
runner
group,
but
Darren
for
right
now
is
still
going
to
be
covering
Runner
sass.
So
I
will
pass
it
off
to
him
to
talk
about
rental,
core
and
Runner
steps.
B
B
What
we're
focused
on
in
our
core
for
58,
as
in
all
of
the
previous
milestones,
we
continue
to
heavily,
invest
up
front
and
reducing
the
backlog
of
bugs
in
especially
our
priority
sets
our
P2
S2
bugs
is
currently
in
their
own
core
backlog.
We
have
a
new
clock
time
process,
that's
comprised
of
Gina
Doyle,
who
is
a
designer
Elliott,
rational
engineering
manager,
Seth
Morgan
or
QA
team.
The
QA
team
led
Now
by
Seth
Morgan
they're,
taking
on
responsibility
of
helping
us
organize
prioritizing
working
through
our
about
background.
B
B
B
I'm,
taking
a
look
at
some
of
the
bugs
here
that
they
were
trying
to
work
through
in
terms
of
new
important
features
as
to
call
out
58.
We
are
working
on
the
on
shipping,
the
Alpha
version
of
what
we're
calling
the
AWS
ec2
fleeting
plugin,
so
I'll
just
go
over
to
that
I'll.
Just
kind
of
briefly
explain
what
this
is.
B
The
ec2
feeding
plugin
is
one
piece
of
the
solution
set
for
replacing
the
auto
scaling
mechanism.
That's
today,
based
on
duck
machine,
so
I'm
going
to
click
over
here,
we've
published
our
next
one
on
auto
scaling
architecture
here
in
our
blueprint
style.
So
you
can
take
a
quick
look
at
what
this
the
new
architecture
will
look
like
all
the
details
are
here.
The
tldr
is
basically
this.
B
The
next
One,
auto
scanning
architecture
will
allow
you
to
Auto
scale,
gitlab
runner
on
public
cloud
services
like
Google
AWS
Azure,
but
using
or
leveraging
native
capabilities
and
Native
Auto
scaling
groups
on
those
Cloud
providers,
and
so
what
you'll
see
in
going
back
to
this
one?
What
you'll
be
able
to
start
testing
out,
hopefully
in
15
8,
is
be
being
able
to
use
the
entire
new
auto
scaling
Solution
on
AWS
ec2.
So
the
feeding
plugin
is
the
last
piece
of
the
equation.
B
The
fleeting
plugin
connects
to
gitlab
Runner
and
it's
a
thing
that
allows
us
to
scale
up
the
the
auto
scaling
groups
or
the
runner
within
the
auto
scaling
groups
on
AWS.
So
this
is
a
very
important
piece
on
average
in
in
terms
of
our
journey
to
migrate
away
from
Docker
machine.
So
we're
super
excited
about
this,
because
this
is
a
really
important
milestone
for
us
in
terms
of
providing
you
a
new,
auto
scaling
solution.
Forget
that
Runner,
specifically
on
cloud-based
virtual
machine
instances.