►
From YouTube: GitLab 13.9 Kickoff - Ops:Verify:Runner
Description
13.9 milestone kickoff video for GitLab Runner.
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/27322
A
A
A
At
the
beginning
of
the
year
we
published,
or
I
published,
a
direction,
video
talking
about
the
running
version
and
strategy,
so
that's
available
today
we're
just
going
to
focus
very
tactically
on
the
key
items
that
we're
working
actively
to
ship
in
the
next
federation
forum,
which
is
13.9
so
with
that
said,
I'm
going
to
turn
it
over
to
hyena
and
talk
a
bit
more
about
what's
happening
in
footnote
9
or
we
actually
planning
to
ship
with
3.99
to
to
ui
ux
and
office.
Enterprise
management,
ayanna.
B
Awesome
so
we
know
that
the
big
item
for
running
wax
is
the
enterprise
management
of
the
run,
experience
and
this
item
in
13.9
talks
about
the
system
usability
as
an
important
team
for
gitlab.
So
it's
a
super
hot
topic
and
it
revolves
around
enabling
automated
install
or
self-managed
runners
initiated
from
the
gitlab
ui.
So
today
is
when
users
have
to
install
at
some
point:
they
go
in
dui,
they're
doing
their
thing
and
they
have
to
switch
context
and
go
to
the
documentation
to
find
more
information.
B
They
go
back
to
the
ui,
so
you
want
to
make
that
experience,
seamless
to
them
and
they're
going
to
be
able
to
install
everything
in
context
with
the
application.
So
this
issue
is
something
that
has
been
been
developed
in
the
past
right
there
and
now
finally
got
to
the
point
where
we're
going
to
ship
the
ui
so
really
excited
about.
This
is
going
to
be
a
small
change.
A
Thanks
yeah
and
just
and
as
I
said,
we
talked
about
this
a
few
releases
back.
We
actually
had
the
code
ready
to
go.
It
was
in
the
code
base
and
we
found
a
few
things
we
wanted
to
improve,
so
we
pulled
it
back,
but
we
feel
pretty
stoked
and
pretty
comfortable
now
that
we'll
actually
finally
get
this
into
into
the
product
in
39
and
then
looking
forward
to
all
the
great
things
in
collaboration
with
hyanna,
as
we
improve
usability
for
managing
runners
in
the
ui,
all
the
different
settings
and
appliance
group
instance
level.
A
A
A
number
of
active
pieces
of
working
flight,
but
what
we
focus
on
on
this
iteration
plan
is
a
few
key
critical,
discrete
features
that
we
want
to
call
attention
to
that.
We
are
actively
working
to
shift
in
39,
so
the
first
one
I
just
want
to
chat
really
really
briefly
about
in
the
roanoke
core
and
again
for
us
just
a
reminder:
runner.
A
When
we
talk
about
runacore,
we're
talking
about
the
core
and
the
codebase,
the
application
that
engineer
makes
get
that
ci
run
the
first
thing
we're
looking
at
in
39,
we
talked
about
infinite,
which
we're
not
quite
finished.
Is
this
whole
concept
of
expanding
the
variables
in
reals
and
it's
a
little
bit
verbose.
Let
me
click
over
on
it
and
give
you
a
little
context.
It's
expanding
variables
you
use
for
topology.
A
Basically,
this
is
allowing
users
of
gitlab
pipelines
to
define
a
variable
within
the
gitlab
yaml
crm
file
and
use
that
defined
variable
later
on
within
that
same
file.
So
we
were
pretty
close
in
getting
the
shift
in
13.8.
We
still
have
a
little
bit
of
reviews
to
do
on
the
on
the
active
amounts.
So
we
are
now
getting
working
actively
to
complete
those
and
ship
this
in
13.9
behind
a
feature
flag.
So
the
idea
is
in
3.9
you'll,
be
able
to
take
advantage
of
this
feature
behind
a
feature
flag.
A
We
still
plan
on
doing
additional
ui
work
to
introduce
a
toggle
later
on,
so
that
you
can
actually
turn
on
and
off
this
feature
within
the
ui,
but
in
39
yards
you
can
start
taking
advantage
of
this
variable
inside
other
variables,
feature
and
you'll
get
that
number
file,
it's
national,
core,
1399
and
and
and
to
be
fair.
This
is
a
little
bit
of
like
splitting
hairs,
even
though
we're
saying
this
I'm
going
to
call
most
of
the
code.
A
The
last
two
things
that
we're
working
on
and
really
this
is
really
part
of
the
recording
called
basic
39-
is
powershell
core
support,
both
in
the
docker
executive
and
linux,
as
well
as
the
kubernetes
executor.
As
folks
know,
we
have
enabled
powershell
core
support
in
get
lab
runner
some
releases
back.
I
can't
recall
off
the
top
of
my
head,
which
release.
A
This,
like
these
last
two
pieces
of
work,
rounds
out
that
that
that
portfolio,
and
so
just
to
give
everyone
sort
of
a
bit
of
understanding
of
what
that
means
is.
When
you
look
at
our
matrix.
Let
me
just
grab
this
really
fast
right
when
we're
talking
about
powershell
for
support.
Today,
we
have
partial
core
support
in
version
7.0,
it's
available
in
the
docker
windows
executive,
so
that's
available
now.
So
what
we're
doing
now
is
rounding
out
that
capability
set
by
adding
the
powershell
7's
core
support
in
the
executive
product
linux
right.
A
So,
if
you're
on
docker
linux,
then
you
can
take
advantage
of
the
polish
up
power,
shell
right
as
a
shell
environment
within
your
duffel
linux,
executor
and
then
windows.
So
that's
what
we're
working
on
delivering
information
is
running
on
that
feature
set.
So
we
have
complete
coverage
for
powershell
as
a
specific
for
powershell
as
a
shell
in
the
renault
base.
A
So
that's
what's
happening
according
to
run
a
core
work
stream
for
flipping
demand.
Some
of
the
key
items
we're
working
to
deliver
for
runner
for
our
cloud
and
39
we're
working
on
our
mac
os
build
cloud,
auto
scaler!
We're
pretty
close
on
getting
the
auto
scaler
done
so
that
work
will
actually
reset
seeing
something
that
was
showing
up
in
the
other
scale
of
code
base
in
13.9
and
folks
that
are
following
the
other
school.
A
You
can
take
a
look
at
that
in
terms
of
how
users
interact
with
that
other
skills
and
how
customers
in
the
community
would
interact
with
the
auto
scale.
This
other
skill
is
the
foundation
of
the
new
mac
os
bell
cloud.
The
mac
os
build
cloud
is
currently
in
closed
beta,
and
so
when
we
wrap
up
the
other
scalar,
the
initial
mvc
fuel
of
the
auto
scale,
the
working
field
at
nine.
It
sets
the
stage
for
us
to
start
pivoting
towards
an
open
beta
construct
for
the
mac.
Os
go
cloud
so
you're.
A
Looking
at
you
know,
a
couple
of
releases
after
3.9
will
be
announcing
the
availability
of
the
mac
os
build
cloud
and
the
beta
stand
from
a
radar
perspective,
and
the
reason
is
it's
the
foundational
work
here.
The
other
scale
is
pretty
close
to
being
wrapped
up.
So
those
are
the
key
things
that
we're
working
on
from
the
running
team
in
13.
At
nine,
when
I'm
just
hanging
over
the
high
end
and
say
hi,
thank
you
so
much
for
joining
the
team.
A
B
A
Okay,
awesome
we'll
go.
Everyone
have
a
great
day
as
always,
if
you
need
specific
questions
or
have
a
specific
question
about
an
issue
or
feature
capability
that
hey,
you
know,
if
you're
trying
to
figure
out
where
it's
at
feel
free
to
ping
me
directly
on
the
issue,
it's
the
eastman
also
drop
me
an
email,
the
eastman
gitlab.com
and
so
on.
So
with
that
said,
talk
to
you
soon.