►
A
So
the
way
this
works
is
right.
Now,
when
you're
looking
at
a
list
of
pipeline-
and
you
want
to
run
a
pipeline
manually-
you
would
click
on
run
pipeline.
It
takes
you
to
this
form
where
you
can
specify
the
environment
where
you
want
the
pipeline
to
run
and
then
right
now
the
existing
form
does
not
pre-populate
any
of
the
possible
variable
key
values,
and
we
certainly
want
to
make
that
a
more
user-friendly
experience.
A
One
of
the
possible
solutions
is
to
allow
defining
the
inputs
in
the
cimo
file
itself
the
inputs
of
the
the
variables
the
the
possible
key
and
values.
So
that's
one
approach
to
solving
for
this.
This
story.
This
issue
is
also
particularly
helpful
if
you're
used
to
parameterizing
your
builds
and
you're
migrating
from
jenkins
to
gitlab
ci.
A
The
the
stages
in
your
pipeline
you'll
see
that
it's
represented
to
the
right
and
then,
as
you
go
along
and
you're,
looking
at
your
gamo
file
with
jobs
that
are
defined
to
be
dependent
on
each
other.
In
this
example,
test
two
job
is
needs
the
and
is
dependent
on
the
build
job
above
you'll
see
in
the
graphical
representation
that
there
is
a
connector
between
test
two
and
the
build
jobs
to
indicate
that
those
are
dependencies.
A
And
that's
these
are
just
preliminary
designs
for
that.
But
it
gives
you
a
general
idea
of
how
we
want
to
give
you
a
clear
representation,
graphically
of
your
ci
yaml
file
and
then
later
we'll
iterate
on
that
and
and
give
you
the
ability
to
edit
from
the
right
side,
which
will
change
the
syntax
in
and
of
the
the
yaml
file
on
the
left
based
on
this
design
here.
A
One
of
the
reasons
we're
targeting
this
and
other
bugs
that
I
wanted
to
highlight
is
wanting
to
make
it
to
improve
the
experience
for
you
in
using
both
gitlab
ci
and
then
merge
train
as
well.
That's
it
for
the
three
issues
that
I
wanted
to
highlight.
I'll,
add
links
to
these
issues
under
this
video
feel
free
to
ping
me
on
the
issues.
If
you
have
any
comments
or
questions
or
suggestions,
thanks
for
listening,
take
care.