►
From YouTube: GitLab 14.6 Kickoff - Verify:Runner
Description
GitLab 14.6 kickoff video for the GitLab Runner team.
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28097
B
Yes,
let
me
share
my
screen,
so
I'm
just
going
to
have
us
look
at
the
iteration
plan
issue.
So
in
this
category
I'll
go
through
some
of
the
stuff.
That's
going
to
be
worked
on
on
the
front
end.
First,
the
theme
there
will
be
stale
runners,
so
we're
going
to
add
this
new
status
to
represent
sale
runners,
which
would
be
runners
that
haven't
contacted
gitlab
after
three
months.
B
B
B
So
one
of
the
big
things
that
we
worked
on
in
14-5
was
improving
our
runner
configuration
details
and
it
was
a
pretty
large
design
task
that
we
came
up
with
I'll.
Just
show
a
little
sneak
preview
here
where
we're
editing
the
edit
view
and
read-only
view
when
you
click
into
a
runner.
So
now
you
can
differentiate
those
two
and
have
some
more
room
with
data
that
will
really
impact
the
actions
that
you
want
to
take
on
that
runner.
B
So
we'll
just
we'll
have
to
do
solution.
Validation
for
that
with
users
to
make
sure
that
those
changes
are
or
resonate
with
users
right
now
and
then
the
last
one
here
is,
there
is
a
stretch
which
is
updating
our
empty
state
when
there's
no
registered
runners,
which
is
something
that
today,
I
think
would
just
say,
no
runners
available
so
it'd
be
updating
that
to
be
more
informative.
B
And
then
we
also
wanted
to
work
on
the
ux
vision.
Part
two,
which
is
more
around
ci
job,
cues
and
being
able
to
like
show
that
in
the
ui
and
we'll
build
on
top
of
the
vision
that
we
did
last
time,
and
I
believe
that
is
all
for
the
ux
area.
So
that
is
again
mostly
just
focusing
on
self-managed
when
you're
looking
at
the
admin
ui
and
that
table
there
with
the
runners
I'll
pass
back
to
you.
Darren.
A
A
A
The
unfortunate
six
and
the
reason
I
say
that
is
that
the
second
bug
in
the
list,
the
four
nine
conflict
bug
the
one
where
you
would
see
a
that
users
would
see
a
409
conflict
error
and
then
the
resulting
situation
would
be.
It
would
apparently
cause
the
runner
not
to
execute
any
jobs.
Subsequently
to
that
error,
we've
done
a
bit
of
analysis
in
the
past
week
and
we
think
we've
got
this
under
control
and
we'll
be
writing
up
our
findings
on
the
the
409
conflict.
A
This
is
part
of
our
fips
compliance
initiative
here
at
gitlab,
and
it's
also
tied
to
a
cube
nfy
22,
q4,
okay.
So
the
goal
is
by
at
the
end
of
14.6,
we
have
a
flips
compliant
runner,
gitlab
runner,
there's
also
a
second
iteration
plan
in
14.7,
where
this
additional
work
plan,
where
we'll
have
a
fixed,
verified
runner
coming
on
the
spot.
A
Unfortunately,
seven
so
the
goal
in
fourth
and
the
sixth
is
that
there
will
be
a
fips
compliant
runner
available
in
fourteen
and
six
and
fifth
compliance
is
for
u.s
federal
government
space
in
terms
of
platform
support.
There
are
a
couple
different
things
happening
in
platform:
support
in
14.6
where
to
get
that
runner,
the
first
is
actually
a
ruler
for
fortnite
five.
A
One
last
thing
in
terms
of
platform
support
that
sort
of
platform:
support
theme
in
14.6,
we'll
be
adding
support
for
windows,
server
version
22.2022,
I'm
totally
not
keeping
up
with
the
different
naming
conventions
of
windows.
These
days,
I
might
be
adding
support
for
windows
server.
I
know
for
folks
in
the
community
that
may
be
looking
at
this
video
there.
A
We
have
had
a
lot
of
feedback
that
we
need
to
improve
our
cycle
times
in
terms
of
how
quickly
we
add
support
for
a
new
vendor's
version
of
windows
server,
so
we're
certainly
taking
another
look
at
our
policy
and
our
processes
around
that
to
try
to
improve
that
cycle
time,
but
at
least
for
14.6.
Right
now
we
do
have
the
work
on
deck
to
add,
support
for
windows,
server
version
2022
to
the
get
that
runner
code
base.
The
last
couple
things
I
just
want
to
call
your
attention
to
in
fortnite
6.
A
It
doesn't
necessarily
fall
very
nicely
into
the
you
know,
sort
of
an
overall
arching
theme
or
one
of
the
categories
I
just
talked
about,
but
I
think
it's
pretty
interesting.
The
first
one
is
we're
working
on
adding
interactive
web
terminal
support
to
the
github
on
the
helm
job.
So
this
is
really
interesting.
It
was
three
to
three
years
ago.
It's
a
really
interesting
feature.
A
A
I
think
that's
a
really
interesting
piece
of
capability,
because
again
it
shows
our
long-term
investment
in
kubernetes
as
our
order
skating
solution
and
then
we're
actually
taking
it
a
step
further
by
doing
some
more
innovative
stuff
in
terms
of
hey.
What
does
it
give
that
woman
need
in
terms
of
managing
its
environment
and
kubernetes,
and
so
that
the
the
part
cleaner
world?
That's
solving
these
two
features,
or
these
two
capabilities
is
super
interesting
from
that
standpoint.
A
A
A
Yeah,
there's
a
lot
of
stuff
again
my
appreciation
to
the
runner
team
and
jd
and
miguel
for
all
the
great
work
and
moving
forward
the
strategy
to
improve
the
macro
user
experience
for
all
things
related
to
managing
runners
and
so
looking
forward
to
to
the
future
iterations
and
see
you
next
time
in
escape.
Cheers.