►
From YouTube: GitLab 14.5 Kickoff - Verify:Runner
Description
Iteration kickoff video for GitLab Runner 14.5
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28096
A
Hey
everyone
darren
eastman
here,
product
manager
for
gitlab
runner
again
and
I'm
we're
joined
by
gina
doyle.
Ux
designer
forget
labrunner.
This
is
the
14.5
kick
up
video,
I'm
going
to
hang
it
over
to
gina,
so
she
could
walk
us
through
all
of
the
great
things
that
are
happening
and
the
runner
enterprise
management
and
the
ui
and
user
experience
space
now
I'll
come
back
and
talk
about
the
things
that
we're
doing
in
a
course
so
gina.
B
Sure
I'm
going
to
share
my
screen
and
we'll
look
through
some
of
the
issues
for
14.5
in
the
ux
area.
So
in
144
we
were
able
to
get
a
lot
of
good
amount
of
design
work
done
so
for
this
milestone
now
we'll
turn
to
validating
those
solutions.
So
a
big
issue
that
we'll
be
looking
at
is
solution,
validation
for
improving
runner
configuration
details
and
the
other
two
that
we
have
on
the
list
are
to
make
additional
improvements
to
the
larger
design
issues
we
already
took
on.
B
So
one
of
them
is
around
improving
the
consistency
and
breakdown
of
runner
statuses.
In
the
admin
view,
we
did
some
additional
enhancements
to
the
admin
view
table
for
runners
today,
but
there
are
some
inconsistencies
with
how
we're
representing
statuses
throughout
the
runner
areas,
depending
on
what
level
you're
in
so
we're
going
to
just
make
sure
that
that
is
more
consistent
moving
forward
and
then
the
next
one
is
improving
the
messages
after
you
delete
a
runner.
So
you
can
delete
individual
runners
today,
but
you're
not
given
a
success
message.
B
If
that
is
successful,
or
if
there
was
an
error,
it's
not
really
providing
a
great
amount
of
information
to
be
able
to
fix
that
error.
So
we're
going
to
look
at
that
as
well,
and
those
two
issues
came
from
the
ux
scorecard
evaluation
that
we
did
a
few
milestones
back
as
well.
So
we
know
that
that
will
greatly
improve
the
usability
of
the
whole
runner
workflow,
which
will
be
good
I'll.
Give
it
back
to
you
darren.
A
For
folks
that
are
looking
at
this
for
the
these
kickoff
videos
for
the
first
time
or
maybe
looking
at
these
kickoff
videos
for
a
second
or
third
time
and
just
trying
to
get
a
bit
of
context
in
terms
of
where
things
are
at
yeah,
we're
still
in
the
middle
of
doing
a
bunch
of
the
foundational
work.
And
so
we
haven't
yet
started
to
the
point
where
we're
pivoting
to
in
terms
of
delivering
net
new
features
capabilities.
A
But
as
we
move
into
the
back,
you
know
back
end
of
this
year
and
more
likely
more
early
next
year,
you'll
start
seeing
some
of
these
changes,
starting
to
show
up
and
again
along
the
lines
of
towards
the
sort
of
end
goal
of
improving
right,
the
runner
administration
and
experience.
What
are
the
admin
level
first,
obviously,
and
then
we
have
to
also
think
about
the
group
level
for
gitlab
says,
which
is
a
key
priority
for
us
as
well.
A
So
thanks,
gino,
really
quickly
for
run
a
core
which
again
is
the
the
sort
of
core
runner
on
the
code
base.
I'm
getting
my
screen
out
very
fast
and
since
I
am
not
sharing
my
screen
right
now,
so
everyone
can
at
least
hopefully
see
this
so
for
around
the
core.
A
couple
of
things
are
going
on
and
we're
kind
of
clean.
We
kind
of
changed
the
layout
of
the
iteration
plan,
as
you
probably
just
saw
a
second
ago
on
genius
screen.
A
When
you
go
to
the
iteration
plan,
now
you'll
see
it
segmented
under
the
run
a
course
section
in
terms
of
bugs
and
then
the
second
subheadings
features.
So
under
the
bugs
subheading,
there
are
a
couple
of
the
few
bugs
that
we're
working
on
delivering
the
first
one.
That's
on
there.
We
talked
about
it
for
the
last
two
releases,
it's
denali
cuban
and
the
executor
ignoring
docker
entry.
Point
bug
the
app
there's
an
active
mr
under
review
for
that
bug.
A
So
my
hope
and
goal
is
that
we
get
mr
review
and
actually
get
that
bug.
Finally,
wrapped
up
in
in
14.5
and
there's
also
another
community's
bug
as
well.
As
you
can
see
here
on
the
list.
This
one
is
specific
to
on
the
kubernetes
when
there's
no
windows
nodes
and
has
an
issue
with
that,
the
the
nodes
would
fail
unless
you
set
the
shell
as
pwsh.
A
You
can
drill
into
that
into
that
bug
and
see
a
little
more
details.
Active
work
is
happening
on
this
one,
so
we
hope
to
clean
it
up
as
well.
So
two
kubernetes
buttons
are
on
deck
for
14.5,
and
then
we
have
two
other
bugs
as
well.
One
is
really
reading
to
a
passing
error
that
has
to
do
with
a
new
max
feature,
a
new
mass
feature
that
we
delivered
a
few
minutes
back
and
the
last
one
is
a
long
standing
belt
that
we
had
related
to
four
nine
conflicts
and
the
runner.
A
I
really
hope
that
we
can
make
some
some
some
serious
traction
if
you
will
on
the
four
nine
conflict,
but
and
hopefully
the
deliveries
in
14.5
and
then
just
to
kind
of
give
everyone
some
additional
context.
Earlier
on
this
year,
jackie
porter,
a
group
product
manager
for
the
verify
stage,
one
of
the
okrs
that
we
set
was
around
reducing
the
backlog
of
product
of
p2,
bugs
it
across
the
entire
verify
stage.
A
The
feature
list
here
is
related
to
kubernetes.
We've
talked
about
this
on.
For
the
last
couple
of
milestones,
it's
a
super
complex
feature
and
that's
why
it's
taking
a
bit
of
milestones
to
deliver
it's
around
having
the
ability
to
clean
up
cuban
interest
resources
once
the
job
is
complete,
and
so
this
particular
feature
is
around
creating
a
schedule
cleaner
to
ensure
that
all
the
communities
resources
are
correctly
cleaned
up,
and
so
we
don't
have
issues
with
you
know.
Parts
hanging
around
after
job
execution
is
complete.
A
The
I'm
going
to
skip
the
other
kubernetes
feature,
that's
already
actually
in
the
code
base,
because
it
was
community
contribution
and
go
to
the
github
run
operator
of
openshift.
Earlier
on
this
week,
there's
a
great
bit
of
announcement
around
the
fact
that
the
actual
get
gitlab
itself
is
now
available
as
an
operator
on
red
hat,
the
github
runner
operator
for
redhatments,
because
they've
also
been
available
as
well
for
a
few
months
now.
So
both
of
those
products
are
ga.
A
You
have
github
and
you
have
to
get
that
runner
as
operators
for
red
hat
openshift,
and
what
we're
doing
here
for
the
gitlab
runner
operator
is
not
looking
to
release
a
version
of
that
operator,
specifically
for
ppc
64,
led,
compute,
architectures
or
otherwise
supporting
ibm
power,
9
and
also
power.
10
systems,
so
ppc
64
le
gets
runner
operator
for
openshift
extends
our
platform
capabilities
as
it
relates
to
get
web
runner,
and
this
is
again
specifically
to
the
openshift
platform
and
then
finally,
the
other
main
feature.
A
I
want
to
call
your
attention
to
under
the
runner
core
category
that
we'll
be
looking
to
work
on
in
1495
is
the
first
iteration.
We
actually
have
two
iterations
spanned
in
order
to
deliver
a
fips
compliant
gitlab
runner,
and
this
particular
work
is
in
support
of
a
very
important
cute,
q4
fy22,
I'm
chief
product
officer
and
chief
technology
of
officer.
Okay,
our
goal
so
run
a
call.
A
We've
got
a
couple
of
kubernetes
features
on
dank
and
we've
got
the
power,
nine
or
ppc
64
le
get
runner
operator
on
deck
in
145
and
then
we're
starting
the
first
iteration
of
pips
pips
compliance
and
get
it
out
correctly
before
get
that
running
14.5.
So,
let's
run
a
call
in
terms
of
run
a
cloud
we
don't
have
any
features
planned
to
ship
in
14.5,
the
mac
os
or
the
github
runner.
A
The
github
file
for
mac
os
beta
is
ongoing,
and
so
we've
got
a
lot
of
good
feedback
on
that,
and
so,
if
you're
interested
in
participating,
that
is
to
open
that's
still
ongoing
in
a
couple
of
next
takeoff.
Videos
we'll
talk
a
bit
more
in
terms
of
our
plans
for
moving
that
offering
from
beta
to
ga
and
what
it
all
means
for
for
your
customers
and
user
community.