►
From YouTube: GitLab13.8 Kickoff - Verify:Pipeline Authoring
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
So
to
begin
with
the
goals
of
the
milestone,
it's
quite
similar
to
the
goals
of
the
previous
milestone,
which
were
to
work
toward
creating
our
first
class
authoring
experience
as
we
described
in
our
clear
vision,
and
to
do
that.
We
want
to
complete
the
work
on
building
a
dedicated
authoring
area
and
the
mvc,
the
mvc
epic,
and
to
finalize
the
work
as
a
part
of
it
to
finalize
the
work
of
the
static
visual
builder,
and
we
have
actually
two
implementation
issues
which
are
blockers.
A
A
Basically,
we
want
to
allow
every
users
that
create
the
gitlab
ci
yaml
file
to
be
able
to
visualize
how
this
pipeline
will
look
like
even
before,
hitting
the
commit
button
and
go
to
the
view
to
the
pipeline
view
and
that's
the
that's
the
walk,
and
this
issue
actually
blocks
this
wall.
It
appears
that
we
found
a
bug
that
every
pipeline
configuration
with
an
include
that
use.
The
include
keyword
will
fail.
It
appears
we
are
seeing
some
sort
of
an
error
message
and
we
don't
want
to
release
it
without
this
functionality.
A
The
second
issue,
as
I
mentioned
it,
is
blocking
the
our
authoring
area
mvc
and
also
just
as
a
reminder.
The
authoring
area
is
an
epic
where
we
are
going
to
include
all
the
relevant
features
and
that
are
required
in
order
to
configure,
configure
or
update
your
in
your
pipeline
configuration,
it
will
involve
linting
the
static
representation,
editing
functionality
and
more
and
this
issue.
A
It
appears
to
be
a
minor
issue,
but
it
is
a
blocker,
and
the
idea
here
is
that
we
are
missing
some
sort
of
a
confirmation
to
the
user
once
the
user
will
click
the
commit
button
similar
to
what
we
have
today.
Whenever
a
user
hit
the
commit
button,
when
updating
the
gitlab
ci
yaml,
they
will
receive
some
sort
of
a
notification.
Your
changes
have
been
successfully
committed
without
this
functionality
or
this
feature.
A
What
may
end
up
is
that
user
will
continues,
hitting
the
commit
button,
thinking
that
it
is
not
working.
So
I
do
see
users
that
are
hitting
it
over
over
over
and
over
again,
and
probably
think
that
is
something
wrong.
There
is
some
sort
of
a
bug,
so
this
kind
of
small
issue
is
actually
a
big
blocker
for
the
entire
nvc
and
hopefully,
once
we'll
complete
those
two
issues
we'll
be
able
to
release
the
pipeline
editor
alongside
the
visual,
the
visualization
functionality.
A
A
B
Figuring
out
how
to
show
immediate
pipeline
status
feedback
in
pipeline
editor,
the
problem
that
we're
trying
to
solve
is
reducing
the
contact,
switching
as
you're
authoring
your
pipeline.
So
currently,
when
you're
creating
your
pipeline-
and
you
run
your
pipeline,
you
need
to
go
to
the
pipeline
page
to
see
the
status
of
the
pipeline.
Did
it
run
what's
happening
with
it?
We
show
a
little
bit
of
status
indicator
inside
the
single
file
editor,
but
it's
not
very
noticeable,
so
we
want
to
solve
that
problem
in
the
new
pipeline
editor.
B
Another
issue
that
I
will
be
working
on
is
the
improved
experience
for
using
ci
cd
templates.
So
currently
it's
not
easy
to
browse
cicd
templates
and
it's
not
easy
to
figure
out
what
those
templates
do
and
how
to
use
them.
So
I
will
be
iterating
on
the
latest
designs
and
doing
solution,
validation
for
those
designs.
B
We
want
to
offer
additional
information
about
each
template.
Make
the
templates
easier
to
browse,
make
it
possible
to
preview
the
templates
and
make
it
easier
to
use
the
templates
in
various
ways,
so
we
want
to
make
it
possible
to
use
the
templates
in
external
editor
if
you're,
using
an
editor
like
vs
code,
for
example,
you
will
be
able
to
copy
the
template,
you
will
be
able
to
use
the
template
in
the
pipeline
editor
and
we're
also
looking
into
offering
alternative
ways
to
use
the
template.
B
B
And
overall
I
will
be
looking
into
various
different
improvements
to
the
pipeline
editor
for
its
second
iteration.
We
already
have
the
second
iteration
epic,
and
there
are
lots
of
issues
there
that
need
to
be
updated
with
the
latest
designs.
So,
if
you're
curious
about
it
and
want
to
follow
the
work
that
we're
doing
for
the
pipeline,
editor
ux
feel
free
to
check
out
those
issues
and
comment.