►
From YouTube: Product Walk Through - Pipeline Editor
A
Hey
everybody:
my
name
is
kenny
johnston.
I'm
a
director
of
product
here
at
gitlab,
I'm
going
to
be
doing
a
walkthrough.
I'm
super
excited
about
our
new
pipeline
editor
feature
that
the
pipeline
authoring
group
has
been
working
on.
I've
had
a
chance
to
see
a
couple
of
videos
and
interact
with
some
of
the
initial
designs
for
it,
but
I'm
gonna
try
it
out
and
walk
through
it
today,
so
I
haven't
done
too
much
prep,
so
I'm
just
gonna
start
sharing
my
screen
and
we'll
figure
this
out.
A
A
A
A
A
A
A
A
A
A
A
Unknown
key
environment,
I
misspelled
it.
Oh
that's
great
sounds
like
the
kind
of
things
that
you'd
commit
this
change
and
then
things
wouldn't
work
and
you'd
have
to
go
back
and
figure
out.
I
love
that
this
live
linter
is
awesome.
Okay,
I
think
I
have
everything
I
want.
Let's
see,
visualize
just
full
lint
output.
A
The
okay
I'll
put
something
here:
that's
not
an
actual
branch
name.
I
still
think
it's
okay,
that
might
be
interesting.
I
don't
know
how
much
validation
we
can
do
against.
That's,
not
just
linting.
That's
looking
to
see
that
there
are
artifacts
for
these
things,
but
if
master
wasn't
my
default
branch.
Can
I
put
default
here?
A
A
A
The
so
like
hover
over,
I
guess
what
I'm
trying
to
say
is
when
I
was
down
here.
I
didn't
see
that
there
was
this
notification,
because
I
was
down
here
and
this
my
window
was
actually
pretty
big.
So
maybe
it
would
be
good
to
have
it
pop
up
somewhere
around
where
your
community
changes
down
here
or
show
up.
A
A
A
A
Valid-
and
it's
not
like
the
repost
go
back
to
here,
because
I
can
go
back,
oh
see
what
happens
if
I
click
this,
that's
just
going
to
take
me
to
the
file
yeah.
I
think
you
know
all
these
signs
in
your
project
overview.
Page
point
me
to
like
edit
my
csd
config
click
on
this
file.
They
all
get
me
to
places
that
don't
end
in
the
new
editor,
so
it'd
be
great
to
think
about.
How
can
we
make
all
those
paths
get
me
to
the
editor,
but
I'll
go
back
to
the
editor
here
here.
A
A
A
A
A
Well,
didn't
need
this
one.
I
think
it's
right,
I'm
looking
at
the
docs.
Let's
try
that
again
so
again
when
I'm
here
it
would
be
cool.
If
I
could
see
well,
which
jobs
would
we
build
from
that
matrix
in
this
visualize,
because
otherwise,
I'm
now
back
to
my
old
pattern
of
looking
at
the
pipeline
and
seeing
that
it
got
yeah?
Okay,
here's
my
six
that
I
was
looking
for.
Okay,
I
think
that's
what
that's
what
I
wanted
to
highlight.
A
A
A
Okay,
so
the
other
interesting
thing
is,
I
know
this
is
probably
farther
ahead
is
when
visualizing
showcase
common
pipeline
types,
so
we
could
visualize
on
commits
on
branch
on
commits
on
default
and
on
mrs,
for
example,
so
that
way
it's
visualizing,
but,
like
I
have
some
logic
for
what
type
of
pipeline
to
run
like
these
deploy
ones,
don't
run
on
non-default
branch,
so
I
might
want
to
visualize
hey
here's.
What
your
pipeline
will
look
like
on
a
commit.
Here's.
What
your
pipeline
will
look
like
on
a
commit
on
your
default
branch.
A
A
A
Let
me
confirm
that,
let's
see
if
I
just
generated
it's
pipelines,
yeah
I
did
okay,
so
that's
nothing.
It
should
be
gray.
I
shouldn't
be
able
to
commit
changes.
If
I
haven't
edited
anything
here,
what
was
I
talking
about
the
test
shouldn't
be
running
because
I
thought
I
was
thinking
it's
only
on
march
request.
So
that's
nothing
like
now.
I'm
realizing,
I
probably
did
something
wrong
and
that
feedback
loop
is
not
as
fast
as
I
would
like
cool.
I
think
I'm
going
to
stop
here.
That's
some
great
feedback.
I'm
excited
about
this.