►
From YouTube: GitLab 13.12 Kickoff - Verify:Runner
Description
Kickoff video for GitLab Runner 13.12
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27718
A
Third
time
is
a
joke:
hi
welcome
to
the
1312
runner
kickoff,
I'm
hannah
betty
simon
product
design
manager
for
citd.
Currently,
the
ux
drive
for
the
runner
team,
and
today,
I'm
here
with
darren
our
product
manager,
we're
going
to
be
covering
the
kickoff
for
runner
and
all
the
awesome
stuff
that
we're
going
to
be
delivering
this
milestone.
So
here
you
can
see
the
iteration
plan
and
I'll
start
by
covering
some
of
our
ux
business.
A
So
far,
three
four
issues
and
a
number
of
merge
requests
related
to
improvements
to
the
runner
admin
view
to
the
settings
group
and
project
pages,
which
is
really
awesome,
and
I
wanted
to
give
a
shout
out
to
miguel
and
suzanne
for
helping
us
achieve
this
and
for
the
continued
efforts
to
improve
and
polish
the
ui
of
the
runner
view.
So
thank
you.
So
much
for
all
you're
doing
for
our
teams
and
looking
forward
to
continue
working
on
improving
the
usability
of
runners
in
q2.
A
We
are
still
focusing
on
the
usability,
so
that's
a
overall
goal
for
the
ux
department
and
the
issues
that
we
couldn't
deliver.
This
quarter
probably
will
cascade
to
the
upcoming
to
the
upcoming
milestones
in
the
next
quarter,
and
my
second
update
is
actually
related
to
my
availability.
With
my
recent
transition
to
the
product
side
manager,
role
for
cicd,
my
focus
switched
to
hiring
a
product
designer
that
will
cover.
A
I
will
back
fill
my
role,
so
in
the
meantime,
in
132,
I
will
continue
supporting
the
runner
team
by
facilitating
ux
reviews
in
the
merger
quest
so,
for
example,
with
miguel
I'll
continue
reviewing
any
front-end
updates
that
inc
that
affect
the
user
interface,
so
that
we
can
keep
the
conversation
going
and
make
sure
that
front-end
is
generating
improvements
and
that
ux
is
involved
in
providing
best
practices
and
fixing
minor
issues
and
following
up
with
ux,
that
in
the
merge
request
phase.
A
B
Hey
thanks
a
bunch
hyanna,
and
just
I
want
to
say
thank
you
for
your
leadership
on
the
on
the
ux
front
and
also
an
echo
that
that
shout
out
to
miguel
and
susan
for
just
their
proactive
leadership
and
and
moving
the
ball
forward
in
terms
of
improving
our
system
usability
score
for
things,
whether
it's
a
runner,
I'm
just
super
working
on
that
front,
I
said,
that's
been
awesome,
so
folks,
just
kind
of
back
to
sort
of
the
tour
de
frost
and
the
force
for
us
here
chatting
a
bit
in
terms
of
what's
coming
with
the
core
running
capabilities
for
entertainer
one
two,
I'm
just
gonna
go
over
this
really
quickly,
one
of
the
first
things
we're
looking
to
deliver
in
31
term.
B
Actually,
pretty
close
is
this
this
feature
here,
which
is
called
unable
to
pass
variable,
name
and
secret
volcano.
So
let
me
translate
that
into
something
that
means
a
bit
more
english.
B
Basically,
when
we
were
implementing
the
mvc
for
default
integration,
a
few
releases
back,
we
chose
to
expand
variables
only
in
two
places
very
called
correctly
was
the
auth
jwt
and
auth
role
entries.
What
this
new
feature
will
do
to
prevent
layman's
term.
It
will
allow
the
ball
secret
configuration
to
be
applicable
for
various
expansion,
so
this
it
unlocks
use
case
as
described
here
where
the
user
is
trying
to
use
an
environment
and
variable
in
this
in
the
configuration
setting
for
passing
in
those
fault
values.
B
So
this
feature
is
pretty
close
and
there's
actually
an
active,
merge
request
under
review,
so
we've
got
a
deliverable
label
on
there
and
it's
looking
to
ship
in
131.2
the
other
thing
that
we're
working
on
in
31.12
and
we
actually
chatted
about
a
bit
about
this
in
131
scale.
Video
is
this
feature
here
called
the
supporting
the
git
strategy
with
the
cuban
news
executor.
B
We
started
work
on
this.
We
hope
to
ship,
including
that
one
month,
however,
there
are
still
ongoing
reviews
of
the
associated
amounts
in
progress,
and
so
that's
that's.
The
result
of
us
now
moving
the
target
milestone,
but
just
quick
recap
with
in
terms
of
what
this
one
does.
A
quick
reminder
is
that
this
feature
enables
to
get
strategy.
Ci
cd
setting
in
the
github
run
the
communities
executor
just
a
quick
recap
and
get
labrunner.
There
are
various
executives
that
we
offer
with
git
lab
runner,
docker,
kubernetes,
shell
and
so
on.
B
This
is
specific
to
the
community's
executive
and
what
git
strategy
does
is
basically
enables
the
use
of
gitlab
ci
to
choose
a
default
way
that
the
project
repo
is
fetch
from
gitlab
during
pipeline
execution.
So
it's
a
very
important
feature
for
our
users
that
are
relying
on
the
kubernetes
executor
to
execute
their
ci
jobs,
the
other
one
that
we
are
working
on
as
well.
B
It's
also
related
to
q
and
a
and
this
again
this
theme
of
kubernetes
will
keep
coming
up
throughout
the
year
and
if
you
recall,
I
mean,
if
you've
been
looking
in
our
kickoff
video
for
the
year,
we
talked
about
around
the
strategy.
I
spoke
a
bit
about
kubernetes
being
one
of
those
key
pillars
for
us
throughout
fy
22..
So
another
thing
we're
working
on
is
the
support
for
windows,
build
pods
in
the
kubernetes
executor.
B
What
this
basically
allows
you
to
do,
and
it's
a
super
important
feature
for
customers
that
have
hybrid
kubernetes,
cluster
configurations
and
basically
they've
got
a
mix
of
linux
and
windows,
virtual
machines,
as
they're
created
in
these
nodes
today,
those
folks
that
have
those
types
of
hybrid
configurations.
B
That
capability
will
not
be
available,
so
you
will
now
support
that
hybrid
configuration,
in
other
words,
will
now
support
you
using
a
window,
a
node,
backed
by
windows
and
your
kubernetes
cluster
for
executing
your
ci
jobs.
So
those
are
the
key
things
we
are
working
on
that
we
have
planned
that
we
are
planning
to
deliver.
We
are
prioritized
for
delivery
and
run
according
to
one
two.
There
are
a
couple
other
things
as
well
that
we
may
get
to
that.
B
You
can
see
here
in
the
list,
but
I'm
not
going
to
chat
about
those
today
in
terms
of
runner
cloud
13.12
focuses
we're
continuing
some
activities
around
ensuring
that
we're
supporting
a
high
level
of
stability
and
attainment
of
our
aptx
slos
for
the
github
become
ci
runners.
So
there's
some
additional
work
that
we're
doing
in
support
of
that
and
we're
focused
a
lot
of
in
terms
of
that
as
well.
From
around
a
quality
perspective,
we've
got
a
lot
of
leadership
from
zeff
our
quality
lead.
B
We
won't
actually
be
shipping
anything
as
a
customer
consumable
feature
in
13.12
related
to
quality,
but
what
we're
doing
is
a
lot
of
work
in
terms
of
improving
on
the
maturity
of
how
we
handle
quality
as
a
construct
as
a
concept
for
gitlab
forget
labrador,
specifically,
and
so
for
folks
that
are
interested.
B
I
mean
you
take
a
look
at
this
runner
incept
link
here,
there's
a
number
of
different
activities
related
to
sorry
related
to
to
quality
and
improving
how
we
test
runner,
how
we,
how
we
support
runners
at
scale
and
so
forth
and
gitlab.com.
So
this
is
the
thing.
That's
a
quick
recap
for
runner.
B
B
A
Everything's
good,
at
my
end,
thank
you
so
much
darren
for
for
the
overview.
If
you
have
any
questions,
you
can
always
reach
us
out
right
at
the
gitlab.
I
have
our
fedeximo
and
darren's
as
well,
and
it's
going
to
be
the
best
release.