►
From YouTube: GitLab 15.5 Kickoff - Verify:Runner Core, Fleet, SaaS
Description
Kickoff video for GitLab 15.5 for the Runner Group.
https://about.gitlab.com/direction/verify/runner_core/
https://about.gitlab.com/direction/verify/runner_saas/
https://about.gitlab.com/direction/verify/runner_fleet/
A
Hey
everyone
darren
here,
joined
by
gina
product
design,
leader
for
runner.
This
is
the
github
runner,
15.5,
iteration,
k-pop
video
and,
as
always,
we'll
start
first
with
gina
doll
covering
all
of
the
interesting
things
that
are
happening
from
a
roadmap
perspective
and
also
from
a
design
and
user
experience.
Point
of
view
and
run
a
fleet
hope
to
do
here.
B
So
as
just
a
reminder,
quick
reminder
about
what
runner
fleet
is,
we
are
focusing
on
providing
one
view
where
the
admin,
persona
or
platform
engineer
is
able
to
manage
all
the
runners
in
their
fleet
easily
and
take
actions
on
them
quickly,
depending
on
what
scenarios
that
they're
in
so
for
this
milestone.
Specifically,
we
are,
we
have
a
few
bugs
that
we're
going
to
be
focusing
on,
but
I'm
going
to
go
to
features
first.
B
However,
many
runners
are
available
to
you
and
this
will
help
be
able
to
discover
the
runners
that
are
available
to
run
your
jobs,
so
that
you're
not
wondering
which
one
is
running
your
current
job
and
then
another
feature
that
is
good
to
point
out
is
we'll
be
adding
tags
to
a
tag
filter
to
the
group
runners
view,
which
has
been
really
commonly
asked
for
lately.
So
now,
you'll
be
able
to
filter
your
runners
by
tags
in
the
groups
view
and
one
other
issue.
B
But
the
owner
is
going
to
be
the
group
project
or
the
instance
where
that
runner
was
registered
so
where
that
registration
token
is
linked
to,
and
this
will
really
help
be
able
to
point
users
to
the
person
who
registered
that
and
has
to
make
upgrades
or
configuration
changes
and
so
on,
and
we've
been
asked
for
this
for
a
while.
So
we're
we're
super
excited
to
be
able
to
add
this.
B
On
the
bug
side,
we
have
a
couple
bugs
that
we're
going
to
be
looking
at
one
about
tokens
being
unique,
they're
not
currently
unique,
so
we're
fixing
them
on
the
off
token
side
and
registration
token
side.
And
then
we
also
had
some
group
runners
problems
where,
when
people
were
invited
as
group
owners,
they
weren't
able
to
see
the
runners
that
they
manage
so
we're
fixing
that
as
well
and
then.
Lastly,
on
the
ux
side,
we
are
finally
going
to
be
putting
some
time
into
the
mvc
for
ci
job
queues.
B
We're
really
excited
about
this.
We've
heard
from
many
many
users
that
you're
looking
for
more
insight
into
what
their
runner
queue
is
looking
like
and
why
it
is
taking
so
long.
Possibly
for
them
to
run
jobs,
so
this
is
going
to
be
our
first
iteration
on
displaying
that
for
shared
runners,
so
we're
going
to
start
with
just
the
shared
runners
and
that
is
it
from
the
runner
fleet
side
I'll
hand
it
to
you
darren.
A
A
And
gina
thanks
for
the
call
and
direction
page,
just
a
quick
reminder
to
everyone.
Am
I
looking
in
the
video
we
do
have
separate
direction
pages
for
all
these
categories
run
a
fleet
on
the
genius
managing
and
addressing
the
team
run
a
call
on
renaissance,
and
again
you
can
find
these
pages
in
about
get.com
when
you
go
to
the
wondercore
run
a
sas
or
on
the
fleet
direction
pages.
A
What
we
try
to
do
here
under
strategic
priorities
is
give
you
sort
of
a
big
picture
of
you
by
quarter,
something
like
the
sort
of
like
the
big
things
where
female
thematic
things
we're
thinking
about
and
that
we
are
working
towards.
So
that's
what
you
see
here
and
then
in
the
iteration
plans
we
kind
of
go
obviously
a
little
bit
deeper
and
now
more
into
the
tactical
weeds.
A
If
you
will,
in
terms
of
the
things
that
are
actually
on
deck,
so
for
fifteen
five
people
on
a
core,
as
is
the
case
in
every
iteration
for
running
core,
a
significant
percentage
of
our
engineering,
pro
investment
and
or
prioritization,
is
first
and
foremost
on
resolving
any
known
security
issues.
So
that's
the
first
thing,
you'll
see
here
on
our
list.
It's
on
the
block
section.
A
We've
got
a
couple
of
things
that
are
securely
related
and
then
we
also
have
some
capacitive
significant
capacity
set
aside
for
reducing
our
backlog
of
aged
s2
bugs
and
so
as
you're.
Looking
at
this
video
right
now,
the
particular
the
list-
that's
on
the
screen
for
104
in
terms
of
above
bugs
that
are
on
the
canonies
of
55,
is
a
tad
bit
long,
and
so,
by
the
time
we
actually
get
into
our
iteration
cycle,
we
will
potentially
prune
this
list
along
a
bit
just
because
we
have
limited
capacity.
A
But
this
is
right
now,
the
the
current
thinking
in
terms
of
those
bugs
that
we
have
these
are
considering
to
move
forward
on
in
15.5
from
a
features
perspective,
and
there
are
a
couple
of
things
that
I
want
to
call
your
attention
to
that.
We
really
would
love
to
get
over
the
finish
line
and
15.5,
and
that
will
provide
a
lot
of
incremental
value
to
you,
the
end
user
community,
as
well
as
to
our
customers.
A
The
first
one
here
is
just
masking
of
tokens,
and
this
is
again
it's
a
feature
set
but
also
related
to
security
concerns,
and
we
want
to
add
additional
security
in
our
locking
logging
mechanism
for
certain
types
of
tokens
of
tokens
with
a
certain
string,
and
the
specific
string
in
this
case
is
gl
pad
beyond
this
one.
The
next
new
feature
that
I'm
super
excited
and
hopeful
that
we
will
make
traction
on
in
15.5,
and
this
is
related
to
secure
software
supplies.
A
Chain
strategy
is
native
literally
signing
the
get
the
run
and
build
artifacts.
I'm
gonna
recall
a
few
iterations
ago
we
released
the
mvc
feature
the
where
in
get
that
runner,
we
are
generating
the
attestation,
that's
aligned
with
the
ss
slsa
or
cell
c2
format,
and
that
has
been
received
extremely
well
by
our
user
and
customer
community
and
so
as
part
of
our
long-term
software
supply
and
change
security
strategy
and
we'll
continue
building
on
that
capability.
A
The
next
iteration
for
runner
as
part
of
that
overall
strategy
is
natively,
signing
the
build
artifacts,
and
so
we're
super
excited
about
getting
into
this
and
a
bit
more
here
on
1755
and
so
to
start
get
a
little
momentum
in
terms
of
adding
around
that
capability
set
around
the
entire
entrance
of
the
supply
chain.
Secure
software
supply
chain
flow
so
looking
forward
to
to
us
hopefully
making
meaningful
progress
in
shipping
the
next
iteration
for
software
supply
chain
15.5.
A
The
other
thing
that
will
that's
kind
of
interesting,
that
I'm
really
hoping
that
we
can
get
2015.5
and
to
ship.
For
for
you
to
use
community
and
customers
is
this
particular
feature.
This
feature
right
here
is
called
secure.
Files
run
support
mvc,
and
this
is
actually
in
support
of
our
mobile
devops
strategy
and
it's
really
pretty
cool
there's.
Actually
a
blog
post,
that's
coming
out,
I
suggest
you
look
for
it.