►
From YouTube: Pipeline Authoring 3-year Vision mock-ups
Description
Nadia from Verify:Pipeline Authoring talks about the 3-year vision for the GitLab CI builder. These are aspirational mock-ups that set the direction and will evolve and change over time.
A
This
is
nadia
from
verify
pipeline
authoring
and
today,
I'd
like
to
show
you
some
of
the
inspirational
mockups
that
I've
been
working
on
for
our
three-year
vision,
so
these
mock-ups
or
wireframes
they're,
just
to
give
us
a
general
idea
for
the
direction
we're
thinking
about
for
the
features
we'd
like
to
implement
for
the
problems
that
we
want
to
focus
on
further
and
so
on.
So
this
is
not
an
accurate
representation
of
the
future
set
that
we're
committing
to
or
of
the
user
experience
that
we
really
want
to
create.
A
Maybe
it
will
look
and
work
very
different,
but
either
way
here
what
you're
looking
at
is
the
ci
homepage,
which
would
be
your
first
time
experience
within
gitlab
ci.
So,
even
if
you
are
completely
new
to
ci
you've
never
used
ci
before
you
will
be
able
to
read
a
very
quick
tutorial
here.
You
can
just
expand
this
little
welcome,
alert
and
understand
better
how
gitliffci
works
and
what
it
can
do
for
you.
Then
you
can
browse
the
templates.
A
We
would
recommend
templates
based
on
your
project
type,
so
with
minimal
customization
you
can
just
get
started.
You
would
be
able
to
easily
import
your
ci
from
all
of
the
top
ci
tools
if
you're
using
some
other
tool,
we
will
really
try
to
offer
documentation
for
that.
A
If
you
don't
feel
comfortable
playing
around
with
ci
in
your
main
project,
you
can
just
whip
up
a
test
project,
that's
closest
to
the
type
of
project
that
you
have,
so
you
can
play
around
with
things
break
things
share
it
with
your
team
before
you
actually
work
on
ci
in
your
in
your
main
project
and
as
we're
also
planning
to
offer
more
courses
and
generally
more
resources
to
developers
to
learn
about
ci.
They
can
also
appear
on
this
page,
so
this
page
would
always
be
available
to
you.
A
This
will
kind
of
be
the
home
page
where
all
of
the
newest
templates
would
appear
all
of
the
newest
resources
would
appear
here,
and
this
is
probably
the
place
you
would
go
if
you
want
to
create
a
new
pipeline
configuration
as
well.
So
let's
say
you
decide
to
get
started,
you
choose
one
of
the
projects
or
you
create
a
new
popular
from
scratch.
A
Then
you
get
to
the
ci
builder,
so
for
the
ci
builder,
where
we
can
leverage
the
visual
builder
with
the
flexibility
of
the
editor.
So
here
in
the
visual
builder,
you
would
be
able
to
define
all
of
the
main
things
for
your
pipeline,
like
the
jobs,
the
stages,
the
connections
between
the
jobs,
whatever
feels
natural
and
intuitive
in
the
visual
builder,
we
can
have
it
here
and
all
of
the
more
advanced
settings
can
appear
in
the
sidebar.
Where
you,
you
would
be
able
to
define
literally
everything.
A
So
here
you
have
the
job
selected,
so
all
of
the
settings
for
the
job
would
appear
here
and
if
you
feel
more
comfortable
with
editing
the
ymlo
file,
you
can
also
do
that.
So
we
would
have
embedded
linting
here
automatic,
fixed
suggestions
that
you
can
just
apply
in
one
click,
so
that
comes
in
quite
handy
for
those
who
are
used
to
managing
their
ci
configuration
in
a
yellow
file.
A
You
would
also
be
able
to
browse
templates
here,
so
you
can
apply
full
pipeline
templates
or
you
can
browse
the
job
modules
and
just
insert
specific
jobs
into
your
pipeline.
And,
of
course,
as
you
do
that,
as
you
update
anything
in
the
sidebar
like
in
the
editor
or
in
the
settings,
it
would
get
reflected
in
the
visual
builder
as
necessary
as
well,
and
vice
versa.
A
You
would
also
be
able
to
read
documentation
here
within
the
context
of
the
ui,
because
we
understand
that
configuring,
your
ci,
can
get
quite
complex
and
it
can
be
very
useful
to
have
the
documentation
right
within
the
context.
So
you
don't
have
to
leave
the
ci
builder
to
complete
your
configuration
literally.
Everything
will
be
here
in
one
place
so
yeah.
These
are
just
some
of
the
ideas
that
I
have
around
the
pipeline
authoring
experience.
Please
let
me
know
if
you
have
any
other
ideas
for
how
to
improve
this.
A
As
I
said,
this
user
experience
is
very
visionary,
we're
not
necessarily
going
to
have
like
a
sidebar
and
everything
the
sidebar,
I'm
open
to
all
kinds
of
ideas,
and
maybe
you
have
some
suggestions
for
automation
that
we
could
do
or
for
how
to
surface
analytics
within
the
context
of
the
ci
builder.
These
are
all
the
things
that
we're
thinking
about
and
generally
any
other
feedback
on.
This
direction
is
welcome
as
well.
Thank
you
so
much
and
have
a
great
day,
bye.