►
From YouTube: UX: Adding more actions to GitLab CI/CD jobs
Description
Nadia, the Senior Product Designer at Verify:Pipeline Authoring walks through her design exploration for adding more actions to CI jobs in GitLab UI.
A
The
product
designer
for
verify
pipeline
authoring
and
today
I'm
recording
a
quick
walkthrough
of
my
design
exploration
for
adding
additional
actions
to
ci
jobs,
so
in
this
particular
case,
we're
going
to
add
an
action
to
the
manual
jobs
to
run
a
job
with
variables
or
to
retry
a
job
with
variables.
So
here
we
have
two
manual
jobs
in
two
different
states.
This
job
hasn't
run,
yet
it's
ready
to
run
so
it
has
the
play
button
and
the
more
actions
drop
down
and
this
job
has
run
and
failed.
A
So
it
has
a
retry
button
instead,
so,
let's
see
if
we
want
to
run
this
job,
but
we
want
to
run
it
with
some
different
variables,
not
the
default
variables,
so
we
can
click
on
more
actions
run
with
variables,
and
that
takes
you
to
the
job
page
where
you
can
run
this
job
with
variables.
This
is
the
page
that
already
exists.
This
is
basically
the
manual
job
page,
but
we
found
that
it's
not
discoverable.
A
So
users
don't
really
know
to
click
on
the
job
to
run
the
job
with
variables.
What
they
do
instead
is
they
simply
click
on
the
play
button
and
they
never
learn
about
the
option
to
add
variables.
A
A
So
what
I'm
suggesting
instead
of
recreating
a
separate
page
for
this,
is
to
use
a
model
which
is
less
disruptive.
It
means
you
still
stay
on
the
pipeline
graph.
A
You
don't
have
to
go
to
a
different
page
and
you
can
just
input
your
variables
here
and
retry
the
job
and
boom
the
job
is
running,
so
that's
just
less
disruptive
than
running
it
from
a
separate
page
yeah.
So
these
are
the
designs
that
I'm
exploring.
Let
me
know
what
you
think.
If
you
have
any
concerns
in
the
future,
we
want
to
use
this
ellipsis
drop
down
for
more
actions.
So,
for
example,
we
might
use
it
on
trigger
jobs
to
allow
you
to
retry
failed
jobs.