►
From YouTube: GitLab 14.1 Kickoff - Verify:Runner
Description
GitLab Runner 14.1 kickoff video.
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27972
A
Hey
everyone
welcome
to
the
github
runner,
14.1
kickoff
video,
I'm
daryn
eastman
product
manager
for
github
burn,
so
today,
I'll
cover
a
few
of
the
key
features
and
capabilities
that
we're
working
to
deliver
and
get
lab
runner
forth
in
that
one
starting
first,
we'll
run
a
core
category,
which
is
basically
the
distribution
of
github
runner
during
a
core
application,
binary
and
so
on.
That
is
able
to
run
on
multiple
platforms
and
computer
architectures.
A
So
in
fourth
number
one
you'll
notice.
There
are
a
couple
of
features
here,
I'm
starting
on
the
top
of
the
list
that
we
have
planned
the
ship
in
fort
neto.
But
unfortunately,
we
have
not
completed
those
features,
and
so
our
plan
now
is
to
get
those
wrapped
up
into
fortnite
one.
The
first
feature
in
question
is
adding
support
for
windows,
build
parts
and
the
cubans
executor.
A
As
I
mentioned,
I
spoke
about
this
the
last
time,
which
is
basically
this
feature
says
adding
those
capabilities.
That's
not
that's
not
protein
kubernetes,
which
is
I.e
the
support
for
windows,
billboards
and
adding
that
into
the
kubernetes
executor
next
up
in
terms
of
capabilities
related
to
windows
that
we're
looking
to
deliver
in
fourth
in
one
is
adding
support
for
windows,
server,
core
version,
20
h2,
the
summer
annual
trial
release,
and
we
had
really
hope
to
get
disruptive
in
four
to
no.
The
merge
request
is
pretty
much
ready
to
go.
A
We
had
some
last
reviews
pending
on
it
and
so
we'll
wrap
those
reviews
up
and
get
it
shipped
to
you.
In
fourth
note
one:
the
next
feature
capability.
I
want
to
draw
your
attention
to
that.
We're
working
on
the
fortnite
one
is
the
variable
inside
other
variable
feature.
Now,
if
you
recall
I've
been
speaking
about
this
for
quite
some
time
now,
because
we've
been
doing
this
work
over
the
past
few
months
and
make
making
iterative
changes
towards
getting
this
this
one
laptop.
Okay,
where
we're
at
today
is
that
the
capabilities
in
place.
A
We
currently
have
a
behind
the
feature
flag
on
gitlab.com,
so
our
goal
and
our
goal.
Our
idea
is
that
we'll
continue
to
do
some
additional
testing
on
github.com
unfortunate
one
wrap
up
any
additional
issues
or
sort
of
like
minor
tweaks.
That
needs
to
be
done
and
get
this
feature
finally
shifted
out
of
the
door
with
this
feature
delivered
and
available.
If
you
recall,
the
value
proposition
is,
as
a
user
of
github
ci
you'll
be
able
to
define
a
variable
within
your
gitlab.yaml
file
and
then
later
on
within
the
same
file.
A
The
other
interesting
capability
we're
working
on
for
running,
quad,
491
I'll
call.
Your
attention
to
this
unisex
is
related
to
puff
cleanup
if
you
one
of
our
users
or
customers
that
rely
on
the
communities
executive,
you'll
notice
that
we
have
a
couple
of
issues
in
our
backlog
related
to
pub
prenup.
This
was
one
of
them
and
there's
actually
another
one
here
as
well.
That's
linked
to
this
issue,
where
we
talk
about
challenges
with
all
runner
parts
hanging
around
and
having
eventually
welcome
new
parts
from
starting.
A
A
So
again,
if
you've
been
following
along
over
the
past
couple
of
releases,
and
especially
at
the
cubans
executives,
one
or
two
that
you
use,
you
have
noticed
that
there
have
been
a
lot
of
incremental
features
being
added
and
capabilities
and
bulks
being
resolved
around
q
a
so.
I
just
want
to
call
that
out
that
we
continue
to
do
a
lot
of
investments.
A
lot
of
work
on
the
cuban
executor
and
all
things
cuban
is
for
the
runner.
A
So
this
is
coming
again,
mr
up
in
fourteen
one,
the
last
last
issue
that
seems
interesting
to
talk
about
in
terms
of
fourteen
one.
Is
this
one
here
in
terms
of
specifically,
you
run
a
core,
and
this
is
around
features.
That's
really
impacting
our
use
of
the
runners
on
gitlab,
sad
and
supporting
our
customers
on
gitlab
sas
on
github.com.
A
So
at
this
point
system,
failure
is
in
some
scenarios
about
system
failure,
but
other
scenarios
is
not,
and
so
we
want
to
kind
of
implement
this
in
such
a
way
so
that
it's
no
longer
resulting
and
impacting
our
sli
and
no
longer
resulting
in
you
know,
inherent
alerts
being
being
raised.
So
we're
working
on
that
as
well
and
we'll
get
it
wrapped
up
for
an
impact
in
a
positive
way.
The
experience
for
srv
teams
and
experience
on
on
gitlab
runners.
A
So
those
are
the
key
things
that
we've
got
in
store
on
deck.
For
you
know
core
get
lab
application.
If
you
will
for
fortnite
one
and
switching
guests
to
run
a
cloud
I.e
again.
The
gitlab
runners,
this
github,
sharedrunners
and
gitlab.com.
That's
a
bit
of
a
mouthful.
I
know
so
we're
continuing
our
investment.
A
As
you
can
see
in
the
first
line
item
here
and
ensuring
that
we
have
a
continued
focus,
release
after
release
on
improving
the
stability
and
the
reliability,
the
scalability
of
the
gitlab.com
runner
fleet
and
so
we'll
continue
that
investment
and
and
you'll
you're
slowly
starting
to
see
the
impact
of
that
investment
and
improve
slo
scores.
We're
going
to
talk
about
a
bit
more
about
in
the
future
in
future,
kickoff
videos
and
the
future
direction.
A
Page
updates
will
continue
to
to
add
more
details
around
that,
so
that
investment
is
continuing
in
fortnite
one,
the
other
bit
new
features
and
capabilities
are
coming
in
fortnite
and
one,
and
we
talked
about
this.
Unfortunately,
we
had
to
delay.
It
is
that
in
fortnum
one
we
finally
hope
to
open
up
to
a
larger
customer
and
user
base.
The
mac
os
build
cloud
runners
on
gitlab
sas.
A
We
currently
have
a
number
of
customers
and
organizations
using
the
mac
os
build
cloud
runners
in
the
closed
beta
time
scenario.
We've
been
doing
that
for
some
time.
Some
time
now
our
goal
in
ford
net
one
will
be
to
open
up
the
aperture
so
that
more
folks,
more
customers,
more
users
can
start
testing
it
out
and
give
us
feedback,
and
so
that
we
can
iterate
towards
moving
this,
offering
to
ga.
A
Ui
news
experience
category,
but
there's
tons
of
great
work
happening
here
by
our
front-end
engineer
and
front-end
design,
lean
team,
a
couple
of
pieces
of
foundational
work
that
we
have
been
working
on
and
fortnite
or
continues
in
fortnite
one
I'll,
just
kind
of
speed.
That,
really
briefly,
is
that
so
the
first
thing
that
we
want
to
do
in
the
github
ui's,
when
is
to
run
us,
is
ensure
that
we
have
the
foundation
so
that,
as
so
that
we
can
actually
deliver
to
you.
A
A
first-class
enterprise
management
experience
for
runners
at
scale,
and
so
part
of
my
work,
as
I
mentioned
in
fortnite
know,
is
that
the
current
admin
views
that
are
in
the
gitlab
ui
and
use
our
legacy.
Front-End
framework
and
we've
been
migrating.
Those
views
and
the
online
technology
to
view
most
some
of
that
looks
already
done.
We
have
some
wrapper
built
in
doing
fourth
number
one.
A
That's
what
you're
seeing
here
with
admin
list
view
being
migrated
from
helmet
to
view
admin
run
on
detail,
views
being
migrated
from
hamilton
view,
so
that's
going
to
wrap
up
in
1491
there's
another
work
as
well
being
planned.
So
again,
when
that
conditional
work
is
in
you'll,
see
us
in
subsequent
release.
Talk
a
bit
more
now
in
terms
of
new
features
and
capabilities
around
the
management
experience
both
for
the
admin
level
and
then
also
for
the
group
level,
and
the
group
level
of
is,
of
course,
very
important
for
our
customers
that
rely
on
gitlab
sas.
A
So
we
need
to
cover
both
scenarios
in
both
use
cases.
Of
course,
our
self-managed
customers,
as
well
as
our
customers
that
are
relying
on
gitlab's
ass,
which
is
key
for
us,
but
having
this
foundation
in
place,
covers
both
tracks
and
so
once
we
get
that
done,
we'll
be
able
to
accelerate,
adding
incrementally
adding
new
features
going
forward
and
then,
finally,
in
1491,
there's
other
work
being
planned.
The
auto
work,
that's
underway
in
terms
of
making
runners
within
products
and
groups
visible
in
first-class
citizen.
A
One
so
you'll
see
some
more
mock-ups
around
this
you'll
see
some
more
design
iterations
around
that
first-class
experience
in
terms
of
the
the
runners
in
the
group
and
the
use
of
you,
and
so
that's
that's
kind
of
a
lot.
Actually,
I
think
for
what
that
one,
especially
coming
out
for
a
major
release,
but
you
know
we
at
gitlab.
A
So
that's
it
for
the
491
kickoff
video.
As
always,
if
you
have
any
questions
about
a
feature
or
capability
on
this
list
or
featuring
capability
or
bug,
that's
currently
sitting
in
one
of
our
main
github
runner
backlogs
feel
free
to,
as
always
ping
me
directly
on
it.
Darren
eastman,
it's
my
gitlab
tag,
I'm
trying
to
give
you
an
answer
in
terms
of
what
we're
thinking
in
regards
to
prioritization
and
how
quickly
he
gets
around
to
it
or
what
our
current
thoughts
are.