►
From YouTube: GitLab 14.4 Kickoff - Verify:Runner
Description
Category Direction: https://about.gitlab.com/direction/verify/runner/
Runner 14.4 Iteration Planning Issue: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28045
A
B
Thanks
all
right,
so
I
will
start
by
just
sharing
my
screen
to
look
at
some
of
the
issues
that
we'll
be
going
taking
on
for
14
4
and
just
to
give
some
background
here
as
well.
We
do
have
a
few
epics
that
these
are
associated
with,
so
we're
going
to
specifically
focus
on
the
admin
view
for
14
4
and
improving
the
usability
there,
and
the
three
issues
for
this
are
the
runner
table.
Design
is
outdated
and
doesn't
allow
for
the
addition
of
more
data.
B
The
next
one
is
improve
the
location
of
where
the
runner
registration
information
lives,
and
this
one
is
mainly
around
the
card
that
appears
today
above
the
runner
table
in
the
admin
view,
and
we
have
some
runner
registration
information
that
lives
there
today
that
we
think
that
we
can
move
so
that
it
uses
the
space
in
that
page
better
than
it
does
today
and
then
there's
additional
information
there.
That
could
also
be
moved
around
so
that
we
get
more
space
for
that
table
rather
than
using
the
card
and
then
finally,
the
third
issue
is
improving.
B
The
usability
of
runner
configuration
details.
So
this
is
when
you're
actually
looking
into
a
specific
runner,
and
we
kind
of
just
throw
all
the
information
at
you
today.
It's
a
little
bit
inconsistent
with
the
other
ways
that
we're
doing
this
across
git
lab.
So
we
wanted
to
make
that
more
consistent
and
focus
on
the
action
that
the
user
has
to
do.
B
And
then
we
have
a
bunch
of
additional
issues
if
you
want
to
take
a
look
in
the
enterprise
management,
epic,
which
we
have
sub-epics
in
and
they're
kind
of,
grouped
by
theme.
So
if
we're
focusing
on
usability
improvements
this
time,
but
then
we
can
use
what
we
get
from
that
to
flow
into
the
group
view
for
future
iterations
as
well.
A
A
So
you
actually
won't
be
seeing
any
new
features
show
up
in
144
and
likely
not
even
14.5
as
well,
but
this
will
set
the
foundation
for
our
improvements
in
the
admin
views,
the
group
views
and
improvements
and
capabilities
in
the
ui
and
the
ux
experience
around
managing
fleets
of
runners
around
finding
one.
So
I
know
it
seems
a
bit
slow
and
so
bear
with
us,
but
we
have
to
set
the
foundation
and
once
we
get
the
foundation
going
we'll
be
able
to
build
the
house.
I
promise
you
much
more
quickly.
A
A
A
So
there's
a
quick
recap:
nothing
specifically
new
alcohol.
Again,
some
of
the
issues
the
cuban
is
executive,
executor
ignoring
dr
entry
point.
That's
pretty
close
to
getting
done.
We're
also
working
on
these
two
issues.
Right
here
hope
runner
parts
are
hanging
around
and
it's
the
specific
issue
that
fixes
that
the
last
piece
of
it,
which
is
having
a
schedule
cleaner
to
ensure
that
all
the
related
communities
pod
resources,
are
cleaned
up.
So
we
ship
something
in
14-1
along
these
lines.
A
That's
interesting
in
144.
Is
that
we're
pretty
close
to
implementing
this
graceful
shutdown
feature
it's
something
that
we
shipped
a
while
back
for
believe
it
was
a
shell
executor.
We
are
pretty
close
to
implementing
graceful
shutdown
for
the
doppler
executive
and
so
you'll
see
that
in
144
a
stretch
goal
for
us
in
144
will
be
this
last
issue
here.
The
ability
to
pass
power
shuttle
scripts
through
a
mounted
file
and
a
docker
executor.
That's
likely
going
to
be
a
stretch
goal
for
us
in
144.,
so
44
some
issues.
A
We
started
working
on
and
14
243
of
rolled
over
we're
pretty
close
to
wrapping
that
up.
144
ships
you'll
see
a
bunch
of
new
capabilities
around
a
very
important
strategic
area
for
us,
which
is
a
cuban
executor
and
again.
The
reason
why
that's
super
important
is
that
it
allows
you
to
scale
up
or
run
a
containerized
build
fleet
super
easy
on
kubernetes
platforms,
and
so
it's
a
very
core
piece
of
of
a
runner
strategy
for
runner
cloud.
A
We
don't
have
anything
planned
to
ship
in
14.4
we're
currently
in
the
midst
of
our
beta
for
the
mac
os
bill
cloud
and
the
additional
engineering
resources
doing.
My
team
will
focus
on
work
related
to
gitlab.com,
so
nothing
to
shift
in
and
run
a
cloud
category
in
144..
So
that's
it
again.
As
always,
if
you
have
any
questions
about
the
github
runner
roadmap,
the
category
erection
page
issues
that
you're
interested
in
free,
free,
oaster
ping
me
the
esplanade.
Git
lab
I'm
happy
to
engage
with
you
and
discuss
our
priorities.