►
From YouTube: GitLab 14.2 Kickoff - Verify:Pipeline Authoring
A
A
This
iteration
will
be
will
be
light.
We
have
several
engineers
that
are
on
pto,
which
is
great,
and
this
is
why
I
want
to
focus
mainly
on
one
issue
which
contributes
to
a
to
this.
Epic
and
issue
is
issue
number
two,
and
but
let's
talk
a
little
bit
about
the
epic
before
we
dive
into
that
issue,
and
so,
as
you
can
read
from
the
header,
we
want
to
support
autocomplete
in
the
pipeline
editor.
I
think
it's
smaller
than
autocomplete
and
I'll
dive
into
that
in
a
second.
A
But
for
the
background
you
know
that
the
pipeline
editor
is
the
place
that
we
want
to
make
sure
all
of
use.
Our
users
are
going
when
they
write
a
pipeline
in
configuration.
This
is
why
we
want
to
make
sure
they
are
getting
the
most
out
of
it,
and
but
we
also
know
that
gitlab
ci
can
be
intimidating
and
there
are
a
lot
of
keywords.
There
are
a
lot
of
options
on
how
you
can
write
a
pipeline
and
it's
very
error.
Porn
and
the
job
to
be
done
for
this
epic,
is
is
the
following.
A
When
writing
a
ci
pipeline?
I
would
like
to
know
what
are
the
available
keywords,
so
I
can
use
the
one
I
need
and
when
using
a
keyword,
I
would
like
to
know
what
this
keyword
is
doing,
so
I
can
build
the
pipeline.
I
need
yeah
and
the
proposed
solution
for
that
is.
First
of
all,
as
I
mentioned,
we
want
to
provide
a
user
with
some
autocomplete
functionality
in
the
pipeline
editor
when
they
start
writing
their
pipeline,
and
it
will
provide
the
user
with
the
available
keyword.
A
This
way
the
user
can
read
and
understand
what
are
the
available
functionalities
that
they
can
use
for
that
keyword
and
there
is
like
a
proposed
design,
and
I
think
we
have
a
design
issue
where
we
are
discussing
several
designs
that
we
can
do,
but
just
like
to
explain
how
it
will
look.
So
if
I'm
in
the
pipeline,
though,
and
I
type
the
letter
s,
I
immediately
see
all
the
keywords
that
are
available
to
me.
A
That
starts
with
the
letter
s
I
can
see
in
the
description,
and
there
is
a
button
here
where
I
can
click
and
go
to
to
the
documentation,
to
read
more
and
up
until
today.
We've
run
two
spikes
issues,
one
from
front
and
one
from
back
end,
and
we
broken
it
down
into
several
implementation
issues.
A
And
but
we've
decided
that
the
first
thing
we'll
do-
and
this
is
where
I'm
going
to
talk
about
the
actual
issue-
is
to
walk
a
little
bit
about
on
the
back
end,
and
the
idea
here
is
to
leverage
a
schema
that
is
available
today.
So
if
you
use
the
pipeline
editor
in
in
dot
com,
you
may
occasionally
saw
that
there
is
some
sort
of
an
auto
complete
functionality
that
that
you
can
use,
and
but
there
are
a
lot
of
problems
using
that.
A
So
it's
here
in
in
in
github,
which
means
that
you
need
to
have
some
internet
access
from
your
gitlab
instance
to
that
schema
in
order
to
use
it,
which
means
that
if
you
are
a
self-managed
customer,
we
cannot
guarantee
that
it
will
work,
and
indeed
it
is
not
working
for
dot
com
user,
because
we
disable
the
feature
flag
for
so
for
self
managed
and-
and
also
this
schema
is
not
up
to
date
with
all
the
latest
keyword
that
we've
added
and-
and
so
in
this
issue-
and
this
is
the
foundation
of
this
whole
work
that
this
the
epic
described
is
first
of
all,
move
the
schema
from
the
scope.
A
So
all
of
this
will
be
something
that
we
can
build
upon
once
will
complete
this
issue
yeah
and
that's
basically
the
issue
and
I
think
the
main
goal
that
we
want
to
achieve
in
14.2
is:
I
promise
the
lights
I
like
television
and
I'm
going
to
pass
it
over
to
where
she
can
speak
about
the
scope
of
work
for
ux.
B
Okay,
so
14.2
is
going
to
be
a
very
exciting
milestone
for
ux.
I
think,
because
we've
spent
the
past
couple
milestones
doing
a
lot
of
research
where
we've
gathered
an
enormous
amount
of
insights
around
the
pipeline,
editor
around
the
pipeline
graph
and
the
cicd
templates.
B
So
the
main
two
areas
that
I
will
be
focusing
on
in
13.2
is
exploring
the
improvements
to
the
experience
around
using
csv
templates
for
ci
and
boarding
as
well
as
how
do
you
maintain
a
library
of
templates
as
an
enterprise?
So
I
will
be
looking
at
all
of
those
different
flows
and
the
other
focus
is
improving
the
job
dependencies
view
in
the
pipeline
graph.
B
So
we've
just
finished
solution,
validation
and
gathered
lots
of
great
insights,
so
we
will
need
to
clarify
the
proposals
and
prioritize
the
top
fixes
which,
right
now,
our
tentative
plan
is
to
address
these
three
issues.
So
first
we
want
to
make
sure
that
we
show
the
jobs
in
the
job
dependencies
view
in
the
correct
order.
So
we
actually
show
you
exactly
the
correct
order
of
the
jobs
in
your
pipeline
based
on
all
of
the
different
job
dependencies.
B
Another
one
is:
we
want
to
highlight
not
only
the
jobs
upstream,
the
jobs
that
the
job
depends
on
in
the
in
the
graph.
We
also
want
to
show
the
jobs
downstream,
so
that
would
allow
you
to
see
the
full
critical
path,
basically
in
your
pipeline
and
the
other
one
is
we
want
to
look
into.
How
can
we
show
the
job
dependency
links
in
the
graph
by
default
without
you
having
to
toggle
them
on
and
off,
which
was
our
fix
around
some
performance
concerns?
B
So
I
want
to
dive
a
little
bit
deeper
into
the
work
that
we're
doing
around
the
cicd
templates,
because
I
think
this
is
going
to
take
up
a
lot
of
time
in
14.2
so
currently
in
the
process
of
wrapping
up
visionary
mockups
design
for
ci
template
and
boarding
experience
so,
which
means
how
do
we
use
ci
templates,
say
icd
templates
in
gitlab
for
onboarding
someone
onto
ci
when
they're
creating
their
project
pipeline,
and
that
can
be
just
like
an
individual
developer,
creating
pipeline
for
their
project,
or
maybe
someone
who
is
working
on
a
bigger
team
and
they
have
a
central
team
managing
cic
templates
that
created
some
template
library
for
them
and
they
have
to
access
it
somehow.
B
B
So
it
will
be
a
great
way
to
facilitate
this
discussion,
because
ci
templates
are
a
critical
part
of
gitlab
cicd
experience,
so
we
will
be
making
lots
of
improvements
there
and
we're
also
working
kind
of
collaboratively
at
the
same
time,
with
some
of
the
engineers
at
gitlab
they're,
also
working
on
a
technical
proposal,
so
there
will
be
lots
of
collaboration
in
1492
on
that
and
yeah
aside
from
that,
we're
doing
some
more
work
around
onboarding
we'll
be
partnering
up
with
the
growth
team
around
creating
an
experience
for
guided
onboarding
in
the
pipeline
editor.
B
So
I
think
this
will
be
very
exciting
as
well,
and
if
you
want
you
can
check
out
other
issues.
There's
also
links
to
the
latest
research
that
we've
done.
If
you're
curious
about
the
insights
that
we've
created
yeah,
I
think
this
is
it
very
exciting,
milestone
ahead.