►
From YouTube: GitLab 14.9 Kickoff - Verify:Runner
Description
GitLab Runner Group kickoff video for the 14.9 milestone.
A
Hey
everyone
welcome
to
the
gitlab
runner
group,
4.9,
kickoff,
video,
I'm
danny
smith,
product
manager
for
get
lab
runner
and
with
me,
is
gina
doll,
senior,
probably
designer
for
all
things,
get
lab
runner
and
as
well
some
other
stages
here
get
loud.
I
noticed
that
as
part
of
our
release
post
process
folks
are
like
using
themes
now
as
part
of
the
release
post,
that's
happening
for
14
8,
so
I
will
get
that
runner.
A
B
Okay,
so
the
we
have
a
bunch
of
deliverables
that
we're
getting
out
for
14.9,
but
I
wanted
to
highlight
some
of
the
things
that
we
have
going
on
for
the
group
runners
view.
Thus
far
for
runner
fleet
we've
been
concentrating
on
improving
the
admin
view
and
like
adding
a
better
foundation
so
that
we
can
create
more
features
in
that
view,
and
then
our
hope
was
that
we
could
then
pull
those
features
into
the
group
view
so
that
we
could
help
out
our
sas
customers,
who
are
using
group
runners.
B
So
that
is
exactly
what
this
issue
is
doing.
We'll
be
updating
the
group
view
so
that
it's
no
longer
in
settings
and
we'll
be
pulling
that
out,
so
that
it's
become
its
own
page
under
ci
cd.
And
then
we
also
because
our
development
team
is
so
great
they've,
already
transferred
some
of
the
features
we've
added
in
the
admin
view
and
have
added
it
to
the
group
view,
so
that
it's
ready
to
go
and
it's
kind
of
up
to
speed
with
what
we've
done
in
the
admin
view.
So
far.
B
B
The
other
big
deliverable
that
we're
we're
carrying
out
in
149
is
bulk,
deleting
runners
from
the
admin
view.
So
the
problem
around
this
was
that
runners
can
become
stale
after
a
certain
amount
of
time
and
right
now,
there's
no
easy
way
to
be
able
to
delete
those
from
the
ui.
So
we
wanted
to
provide
the
ability
to
do
that,
and
this
will
will
get
out
like
a
very
early
iteration
of
this,
so
that
you
can
delete
many
runners
at
one
time.
B
B
B
Today
we
just
show,
in
the
admin
view
just
like
a
list
of
the
version
that
the
runner
is
at,
but
we
don't
provide
any
indication
of
how
far
that
is
behind,
so
we're
going
to
start
with
a
small
iteration
to
be
able
to
do
that
and
then
move
forward,
and
then.
Lastly,
this
is
something
that
we
actually
investigated
in
14
8,
so
we
did
this
pretty
early
on,
but
we
noticed
that
shared
runners
setting
is
disabled
on
projects
sometimes,
and
we
don't
know
why.
B
So
we
were
investigating
this
and
we
actually
came
up
with
an
issue
to
track
audit
events
to
be
able
to
track
this
in
the
future.
So
now
we'll
be
able
to
find
the
source
of
the
request
that
would
have
disabled
the
shared
runners
and
then
it
will
be
a
lot
less
confusing
for
users
so
that
they
can
pinpoint
it
down
to
where
that
came
from
that
is
it
from
the
runner
fleet
side
so
I'll
pass.
It
pass
it
back
to
you
darren.
A
Sorry,
just
looking
for
the
mute
button,
hey
thanks
a
bunch
gina
and
for
folks
looking
at
the
video,
I
just
want
to
reiterate:
gina
doyle,
miguel
rincron
pedro
cambriero,
they're,
the
actual
run
of
fleet
team
they've
been
the
ones
that's
driving
the
vision
and
the
execution
and
super
kudos
out
to
that
team.
So
thanks
a
bunch.
This
is
awesome.
So
let
me
see
if
I
can
share
my
screen
really
fast
and
just
chat
a
bit
about
what's
happening
in
the
runner
core
categories
in
49
and
run
assassins
I'll
cover
on
a
sas.
A
First,
nothing
major
in
terms
of
new
features
happening
in
the
science
front
in
49,
for
we're
doing
a
bunch
of
foundational
work
in
terms
of
our
scaling
architecture.
So
you'll
see
more
of
that
in
the
next
few
iterations
we
get
closer
to
what
that
looks.
Like
our
mac,
os
runners
beta
for
gitlab
sas.
A
A
A
How
that
fits
within
the
broader
surface
supply
chain
strategy,
there's
a
bunch
of
different
conversations
that
have
been
happening
so
what
we've
kind
of
focused
on
right
now
over
the
last
couple
of
days
in
thinking
about
how
the
runner
fits
into
this
is
thinking
about
the
in
total
metadata
standards.
Some
works
that
work
that's
been
happening
over
with
the
group,
testified
security
team
and
their
witness
product
and
thinking
about
how
that,
in
total
framework,
some
of
the
rappers
are
coming
out
from
the
with
the
from
the
testify
team
with
mittens.
A
How
that
plays
into
our
overall
see
the
pipeline
approach
and
how
to
run
and
fix
into
that.
So
49
will
be
some
investigational
work.
Hopefully
we
get
to
that
kind
of
think
more
deeply
about
what
is
actually
required
to
support
this
software
supply
chain
vision,
this
attestation
framework,
et
cetera,
et
cetera,
so
just
to
wrap
up
for
49th
from
runacore.
It's
really
going
to
be
focused
in
terms
of
bugs
getting
rid
of
of
hp,
2
bugs
and
then
in
terms
of
moving
the
ball
forward
in
terms
of
new
features
and
capabilities.