►
From YouTube: GitLab 13.3 Kickoff - Verify:Runner
Description
Kickoff video for GitLab Runner 13.2
A
Okay,
hey
everyone!
Welcome
to
hey
everyone!
Welcome
to
the
runner,
13.3
kickoff,
video,
darren,
eastman
product
manager
for
github
runner,
and
here
again
with
me,
is
juan
ramirez.
How
are
you
x,
engineering
designer
forget,
live
runner
today,
we'll
cover
a
couple
of
things
that
are
happening
on
the
ux
side
and
I'll
go
over
a
couple
of
the
items.
That's
happening
on
the
core
on
this
side
as
well
that
we're
hoping
to
ship
in
13.3.
B
B
We
have
some
incoming,
mrs,
that
are
going
to
get
merged
soon
and
we're
going
to
build,
on
top
of
those,
mrs
to
keep
evolving
and
improving
our
settings.
So
one
of
those
is
updating
the
runner
settings
layout.
There's
some
foundational
work
that
we
want
to
do
on
the
design
side.
For
that
making
sure
that
we
can
modernize
that,
since
this
is
already
an
outdated
design
that
doesn't
work
that
well
so
13.3
we're
gonna
be
producing
designs
for
that.
B
We
also
have
the
gold
star
addressing
some
things
from
those
and
mars
that
are
coming
one.
One
of
those
things
is
that
since
we're
now
introducing
the
group
level
management
for
the
runners,
we
also
want
to
start
allowing
our
customers
to
browse
jobs
at
the
group
level.
So
we
need
some
designs
on
that
particular
area
just
to
accommodate
some
performance
limitations
and
constraints
that
we
have
there
so
basically
working
on
that
as
well.
B
I'm
finally
not
seeing
the
stream,
but
we're
also
working
on
this
milestone,
facilitating
a
discussion
on
the
next
things
that
we're
gonna
be
working
on
the
runner
ux
and
how
we're
gonna
keep
improving
the
overall
customer
experience
when
it
comes
to
using
runners.
Yeah,
that's
pretty
much
it
back
to
you!
Darren,
hey.
A
Thanks
so
much
juan,
so
let
me
cover
really
fast
what's
happening.
Let
me
share
my
screen
off
everyone.
Let's
see,
if
I
can
do
it.
Okay,
a
couple
of
some
of
the
key
things
we're
going
to
try
to
get
delivered
here,
including
this
referral
on
a
call
I
just
shared
my
screen
out
and
and
what
you're
seeing
here
is
the
the
kanban
wall
for
runner.
A
The
first
one
is
issue
number
four,
eight
four
three,
and
this
is
really
a
foundational
piece
of
code
that
we're
shipping
is
in
the
runner
code
base
itself
and
what
this
has
enabled
it's
the
the
run
after
script
from
codebase.
It
is
a
prerequisite
for
this
particular
feature
over
at
ci
continuous
integration,
which
is
gives
you
the
ability
to
ensure
after
script
is
called
for,
cancel
time.pipelines,
so
what's
happening.
Is
that
we're
wrapping
up
the
prerequisite
code
and
getting
that
merged
in
finally
increasing
the
three?
A
And
now
we're
going
to
be
an
enabler
to
allow
that
feature
to
ship?
The
other
thing
that's
pretty
close
to
getting
over
the
finish
line
as
well.
That
will
shift
and
fit
into
three
for
runner.
Is
the
this
entry
point
script
being
added
to
the
helper
image
with
docker
files
with
this
particular
fixes,
and
what
this
will
do
is
actually
resolve
issues
that
folks
were
having?
We
were
seeing,
for
example,
with
this
particular
issue
that
537.1,
where
folks
were
unable
to
upload
a
cache
to
menu
s3
server.