►
Description
Nadia, Senior Product Designer at GitLab, walks through a prototype for a new pipeline editor feature.
Simulate pipeline as if it ran for a default branch commit: https://gitlab.com/gitlab-org/gitlab/-/issues/337282
A
Hey
everyone,
this
is
nadia
and
I'm
recording
a
quick
walkthrough
of
the
updated
prototype
for
the
pipeline
simulation
feature
in
the
pipeline
editor.
Thank
you
so
much
to
everyone
who
provided
feedback
on
the
previous
design
iteration.
I
took
all
of
your
feedback
into
consideration
and
made
some
updates
to
how
it
all
works,
and
I'm
gonna
demonstrate
it
here.
A
So
the
link
tab
is
transformed
into
the
validate
tab
and
when
you
click
into
the
validate
tab
by
default,
we're
linking
your
pipeline
configuration
using
static,
syntax
linting,
so
it
happens
continuously,
just
just
like
it
currently
does
in
the
lint
tab
and
it's
represented
by
this
option
of
pipeline
conditions.
None
pre-selected
in
the
drop
down,
so
none
means
that
we're
going
to
validate
only
the
configuration
syntax
and
not
apply
any
pipeline
conditions
like
the
pipeline
source
to
the
validation.
A
So
if
you
select
a
pipeline
source
like
a
default
branch,
commit
we're
going
to
validate
the
pipeline
as
if
it
ran
for
a
default
branch
commit.
So
let's
do
that
now,
once
you
select
this
pipeline
condition,
you
will
be
able
to
simulate
the
pipeline
under
those
selected
conditions.
So
in
the
future,
when
we
have
more
options
here
like
different
pipeline
sources
or
perhaps
variables,
you
will
be
able
to
select
them
here
and
then
simulate
pipeline
with
all
of
those
conditions
and
inputs.
A
For
now,
we
will
only
have
one
option,
because
this
is
the
current
functionality
that
we
have
in
the
pipeline
simulation
in
the
standalone
sea
island.
So
let's
run
this
simulation
now
you
get
this
loading
screen
where
we
show
that
the
simulation
is
running
and
then
you
get
the
output.
So
in
this
case
the
pipeline
simulation
completed
with
errors,
and
we
see
that
the
lint
test
job
needs
the
unit
test
job,
but
it
was
not
added
to
the
pipeline.
A
So
so
now
we
have
these
results
here.
If
we
click
away,
if
we
click
back
into
the
syntax
linking
we
see
that
everything
is
okay,
but
if
we
go
back
to
our
simulation
results,
we
see
that
there's
a
problem.
So,
let's
see
what's
going
on
in
the
edit
tab
in
this
configuration,
we
see
that
the
unit
test
job
it
doesn't
run
for
the
main
branch,
which
is
our
default
branch.