►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
So
I
wanted
to
provide
some
context
and
background
because
I
think
runners
is
something
that
is
kind
of
like
a
hidden
feature.
I
would
say,
and
if
you
don't
go
looking
for
it,
you
don't
really
have
to
interact
with
it.
So
generally
runners
are
used
to
execute
a
job.
So
whenever
you
run
a
job
or
a
pipeline,
usually
we're
using
shared
runners
on
gitlab.com
today,
and
we
don't
like
have
to
worry
about
anything
they're
just
set
up
to
run
stuff
and
just
for
an
example.
A
I'm
just
gonna
skip
over
to
a
job
right
now.
So
this
job,
for
example,
is
running
with
this
runner.
So,
like
I
said
it's
just
like
a
kind
of
hidden
feature,
you
don't
have
to
worry
about
it
if
you
don't
have
to
take
care
of
them.
A
You
can
make
sure
that
shared
runners
will
only
run
the
jobs
that
they're
equipped
to
run
so,
for
example,
at
gitlab
we
have
runners
tagged
with
rails
and
if
they
contain
the
appropriate
dependencies
to
run
rails
test
suites,
then
they'll
be
picked
up
to
run
that
job
and
then
I'm
gonna
hop
over
into
what
we're
really
focusing
on
for
this
vision
is
around
the
admin
area
of
runners
and
I
have
jdk
running
so
I
just
wanted
to
show
you.
A
The
way
that
you
can
get
to
this
area
is,
if
you're
in
the
menu
and
then
you
go
to
the
admin
area
and
then
you'll
hop
over
to
this
runner's
tab
or
a
nav
item.
This
has
actually
been
updated
since
I
first
joined
the
team
in
july,
so
it
looks
a
bit
different
already
because
we're
taking
steps
to
get
there
and
we'll
zoom
in,
but
I
just
wanted
to
go
through
these
types
of
runners,
because
those
are
pretty
important
to
understand
when
I
was
just
talking
through
the
shared
runners.
A
Then
you
can
have
group
runners,
which
are
only
runners
that
are
available
for
a
group
and
its
subgroups,
and
then
you
have
project
runners
that
are
also
called
specific
and
they
are
runners
that
are
only
equipped
to
run
for
that
project
or
projects
that
you
share,
the
runners
with
which
is
a
little
complicated,
and
then
I'm
gonna
hop
back
over
here.
A
So
the
core
job
that
we
wanted
to
solve
with
this
is
when
you're
managing
the
execution
of
many
ci
jobs.
You
want
an
overall
understanding
of
the
job
executors
connected
to
your
organization,
so
you
can
make
effective
decisions
so
that
job
really
centers
around
that
table
view
and
sorry,
I'm
jumping
all
over
the
place.
A
So
it
is
pretty
difficult
to
find
something
very
quickly
if
something
was
going
wrong
and
then
we
also
allow
you
to
look
at
that
runner
and
then
see
the
details
of
it,
which
is
also
a
pretty
cluttered
experience
today,
and
one
of
the
things
that
I'll
just
bring
up
really
quickly
is
that
if
you
have
a
project
runner,
it's
associated
with
a
project.
So
if,
if
a
job
is
not
running
correctly,
and
it
has
to
do
with
that
runner,
you
want
to
be
able
to
navigate
to
that
job.
A
I
mean
to
that
project
very
quickly
to
be
able
to
find
it.
We
allow
you
to
assign
projects
with
this
right
here,
but
in
order
to
even
navigate
to
that
project,
you'd
have
to
go
up
here
and
then
go
to
projects
go
into
that
project,
go
into
settings
and
then
go
to
your
runners
from
there.
So
it's
a
pretty
like
disjointed
experience
and
definitely
makes
for
more
time
to
complete
the
job.
A
So
with
that
said,
a
lot
of
the
things
that
I
learned
for
the
gaps
in
the
experience
actually
came
from
the
ux
scorecard
exercise
right
when
I
joined
the
team-
and
I
linked
the
issue-
I'm
not
going
to
go
through
that
today,
but
there
were
a
lot
of
like
low-hanging
fruits
that
we
got
from
that
overview
that
we
brought
in
to
just
make
like
quick,
quick
changes
to
help,
and
then
we
also
were
brainstorming
as
a
team.
We
have
refinement
meetings.
A
We
had
other
meetings
that
were
specifically
for
brainstorming
for
this
larger,
like
vision
that
we
had
and
then
I
collaborated
with
the
pm
to
prioritize
and
break
up
the
work
into
epics.
So
I'll
show
you
that
it's
a
huge
epic.
A
It
has
a
lot
of
sub
epics,
but
we
wanted
to
break
it
up
so
that
we
have
like
a
timeline
of
what
we
can
get
to
first
and
then
where
we
want
to
go
after
which
are
kind
of
represented
by
these
sub
and
then
finally,
we
brainstormed
vision
criteria
and
talks
through
the
jobs
to
solve.
I
did
that
with
my
pm
in
a
sync
meeting
and
that's
where
this
vision
was
kind
of
documented,
and
I
documented
that
in
this
issue,
so
now
I'm
going
to
hop
into
actually
like
talking
about
the
vision.
A
I
just
documented
a
bunch
of
the
notes
of
what
we
want
to
solve
for
this
vision,
where
we
want
to
go
and
then
created
these
designs,
which
are
pretty
low-fi
but
nadia
and
vithiga
had
come
up
with
this
format
before
and
I
wanted
to
steal
it
because
it
was
a
little
more
intriguing
than
just
like
blocks
on
page.
A
So
for
the
vision
that
we
have
for
runners
in
the
admin
view,
we
would
want
a
system,
admin
or
a
platform
engineer
to
come
in
here
and
easily
be
able
to
find
their
runner.
We
could
present
a
breakdown
of
the
statuses
that
are
really
important
for
runners.
So
that's
what
these
things
are
up
here
and
these
could
change,
but
I
just
picked
up
some
some
really
important
ones.
That
would
allow
you
to
then
like
take
an
action
on.
A
One
of
them
is
projects
assigned,
for
example,
so,
going
back
to
the
example
that
I
was
bringing
up
before
when
you're
looking
at
a
project
runner,
you
want
to
be
able
to
know
what
what
projects
are
assigned
to
that
runner.
So
if
I
clicked
projects
assigned,
I
could
then
like
select
a
project
and
then
see
all
the
runners
that
are
assigned
to
that
project.
For
example,
we
also
wanted
to
break
up
the
way
that
we're
presenting
actions
here.
A
So
if
you
were
eventually
able
to
take
bulk
actions
on
a
spec
on
many
runners,
like
deleting
many,
for
example,
we
could
do
that
by
adding
the
bulk
actions
pattern
and
then
something
that
would
be
like
super
future
would
be
presenting
recommendations
of
what
to
do
with
runners.
That
may
fall
into
these
special
areas.
A
We
have
this
concept
of
stale
runners.
That
would
be
runners
that
haven't
contacted
gitlab
in
over
three
months
and
if
they
haven't
done
that,
then
usually
they're
just
not
being
used
and
right
now
there
can
be
like
tens
of
thousands
of
runners
that
you're
dealing
with
and
many
of
them
could
just
be
not
contacting
so
in
reality.
We
want
those
to
be
deleted.
A
So
as
a
a
very
future
thing,
we
could
provide
a
alert
that
those
will
be
deleted
at
a
certain
time
and
date
or
to
get
there
like
a
step
in
between
there
is.
We
could
provide
a
recommendation
to
delete
those
and
then
that's
where,
like
bulk
actions,
could
come
into
play.
A
A
Let
me
just
hop
back
over
so
then
that's
the
vision,
but
we're
taking
a
lot
of
steps
to
get
there,
which
you
kind
of
already
saw
from
the
ui
that
I
was
showing
from
gdk.
We
have
this
sub
epic.
That's
around
admin
view
usability
improvements,
so
we
want
to
improve
that
table
view
and-
and
I
listed
some
of
these
designs
that
were
worked
on
in
14,
4
and
then
5
and
there's
a
ton
of
other
issues
that
we
also
are
using
as
steps
to
get
to
that
vision.
A
B
B
Rona
has
been
in
a
state
where
we
need
to
move
forward
with
the
low-hanging
fruits,
while
defining
the
vision
and
defining
the
technical
problems
and
understanding
that,
but
with
limited
resources,
for
I
would
say,
almost
a
year
now,
so
it's
really
great
to
see
the
design,
vision
and
everything
around
usability,
because
that's
a
big
big
issue
and
the
pain
point
for
the
enterprise
customers
that
we
have
today
so
solving
that
will
really
unlock
a
lot
of
attention
in
terms
of
adoption
or
verify.
B
Austin,
you
have
the
next
point.
Next
non-read-only.
C
Point
I
lost
where
my
zoom
screen
went
as
I
was
typing
out
my
note,
so
my
first
introduction
to
runners
was
probably
last
fall
when
I
was
trying
to
get
terminal
to
run
in
the
web
ide.
It
requires
a
runner
to
do
something
and
truthfully
I
never
fully
figured
it
out,
but
I
got
it
running
enough.
No
pun
intended
that
I
could
actually
get
the
button
to
appear
so
that
I
could
test
it
for
a
button
migration.
C
A
Yeah,
I
think
well,
some
of
the
docs
has
helped
me
at
least
configure
that
I'll
get
the
link
and
post
it
in
the
google
doc.
A
But
I
think
another
thing
is
that
I
mean
if
you
could
make
an
issue
around
the
experience
that
you
had
there,
because
I
think
we're
missing
a
lot
of
those
like
pieces
in
the
middle,
where
we're
providing
help
along
the
way
when,
when
a
runner
is
needed,
for
example,
and
and
you
need
to
go
and
then
like
set
it
up,
so
that
would
be
great
but
I'll
give
you
the
the
doc
link.
That
has
helped
me
at
least.
Hopefully
it
will
help.
C
Sweet
yeah,
I
mean
I'll,
get
me
started
and
I'll
out
to
my
to-do
list
for
friday
to
walk
through
where
I
got
stuck
and
then
maybe
they'll
give
us
a
point
to
start
with.