►
From YouTube: Runners with multiple machines: Design share
Description
Gina Doyle (Sr Product Designer: Runner Fleet) shares a design variation for runners with multiple machines.
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/388854
A
A
More
information
can
be
found
about
this
use
case
in
this
issue,
and
so
what
I
did
here?
The
biggest
thing
I
did
here
was
try
to
differentiate
those
Runners
that
have
many
machines
from
the
runners
that
don't
the
runners
that
don't
are
you
use
the
auth
token
to
register
them
once
and
never
use
it
to
register
another
Runner
again
so
to
do
that.
I
added
this
icon.
Now
that
might
represent
machines.
I
still
have
to
get
feedback
about
this
design
and
then
I
added
the
total
count
of
machines.
A
But
all
those
Runners
will
still
contain
the
same
ID
and
the
same
token.
So
those
pieces
of
information
up
here
apply
to
all
machines,
and
so
does
the
configuration
so
the
tags,
if
it's
locked
and
assuming
the
type
so
the
project
group
or
if
it's
an
instance,
Runner
and
then,
if
it's
a
project
Runner
the
owner
project,
would
also
be
applied
for
all
those
machines.
A
The
other
things
that
in
in
the
description
would
be
for
all
of
them,
the
other
things
that
would
that
would
be
different
for
them
are
versions.
So
in
this
case,
I
ended
up
just
totaling,
the
number
of
updates
that
were
available
and
then
the
other
one
would
be
that
when
it
was
created
and
when
it
was
last
contacted
as
well
as
IP
address
and
jobs,
but
we'll
get
to
those
things
later.
A
The
only
thing
I
added
here
was
when
the
last
machine
was
created
and
by
who
and
then
the
other
thing
that
I
summarize
are
the
statuses
I
did
pull
out
the
actual
text
from
the
statuses,
because,
as
an
edge
case,
if
somebody
decided
to
create
I,
don't
know
200
Runners
with
the
same
auth
token,
then,
if
you,
if
you
imagine
having
some
sales
some
online,
some
offline,
some
pause
some
running
and
some
idle.
Those
statuses
would
really
pile
up
and
make
that
row
height,
pretty
tall.
A
What
gets
even
more
interesting
is,
when
you
decide
to
view
the
details
here,
so
here's
where
I'm
thinking
of
using
a
drawer
again
I
still
am
working
on
the
design,
but
this
feels
better
that
to
me
than
the
other
iterations
I
created.
So
all
the
attributes
that
are
shown
up
here
apply
to
all
machines.
A
So
I
decided
to
keep
edit
at
the
top
level
and
then
I
only
allowed
pause
and
delete
down
here
and
then
also
when
you
edit
this,
you
should
be
able
to
delete
the
full
Runner
which
I
don't
know
if
we
want
to
allow
doing
that,
because
that
would
in
turn
delete
all
machines.
So
maybe
we
remove
the
ability
to
delete
we'll
have
to
figure
that
out,
I
didn't
think
about
that
and
then
for
the
jobs.
A
This
is
where
the
machine
ID
really
comes
in
handy
because
we'll
have
to
add
another
row
for
machine
ID
and
by
default
filter,
so
that
you're
showing
all
machines.
But
then
the
user
can
filter
so
that
they
only
see
jobs
run
by
Machine
one
or
whatever,
so
yeah,
it's
pretty
complicated
at
the
moment
and
I
think
I'm
still
missing
some
requirements.