►
From YouTube: GitLab 14.10 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
Nadia
is
going
to
talk
about
the
design
effort
that
we
are
doing,
but
in
addition,
we
are
doing
a
couple
of
poc
two
spikes
issue,
two
spike
issues
that
we
run
one
one
in
the
previous
duration
and
one
this
iteration
and
those
spikes
issue
really
help
us
uncover
some
of
the
gaps
and
help
us
refine
our
our
vision
and
and
better
understand
what
is
really
possible.
A
And
what
are
the
things
that
we
want
to
maybe
put
into
back
into
our
into
our
vision,
and
we
think
about
this,
this
entire
solution,
so
those
parts
really
help
us
shape
and
define
our
our
vision.
A
In
addition,
several
feature
enhancement
mainly
two
epics-
that
we
start
working
on
the
previous
iteration
and
we
plan
to
continue
this
iteration,
and
one
of
them
is
triggering
the
downstream
pipeline
from
the
pipeline
graph
and
the
other
one
is
to
add,
include
file
links
in
the
pipeline
editor
and
also
implement
some
high
voted
issues
and
some
bug
fixes.
A
A
A
So,
for
instance,
this
issue
actually
might
be
a
duplication
unless
we'll
find
like
hidden
traps
or
some
problems
that
we'll
find
on
the
way.
But
if
we
look
at
this
issue,
for
instance
in
this
issue,
users
would
like
to
use
variables
in
only
changes
path,
so
basically
only
changes
path
and
we
want
to
introduce
a
variable
in
the
path
and
this
variable
need
to
be
expand
on
the
rail
side
before
we
are
sending
the
walk
to
the
runner,
and
so-
and
you
can
see
this
is
a
very
high
popular
issue.
A
A
Together
by
solving
by
implementing
this,
this
issuing
expanding
the
variable
before
we
are
sending
the
work
to
the
to
the
runner.
In
addition,
there
are
those
two
epics
that
I've
mentioned
at
the
beginning.
One
of
them
is
to
retry
a
downstream
pipeline
for
the
pipeline
graph.
I
think
that
now
we
were
able
to
really
define
a
very
lean
mvc
to
implement
this.
A
This
solution,
and
we
really
really
work
on
the
problem
to
solve
here
so
basically
just
to
emphasize
what
is
the
problem
that
our
user
is
experiencing
basically
today,
when
users
need
to
retry
a
downstream
pipeline,
they
need
to
navigate
into
each
individual
downstream
pipeline
and
click
the
retry
button.
This
is
a
very
time
consuming
action.
A
Our
users
will
be
able
to
first
of
all
in
first
glance,
will
be
able
to
see
all
their
pipeline
all
their
downstream
pipeline,
their
statuses
and
form
that
place
without
going
anywhere
without
context.
Switching
they
would
be
able
to
simply
click
on
the
retire
button
and
retry
those
downstream
pipelines
from
a
single
place.
As
I
mentioned,
this
is
then
we
say
this
is
the
first
iteration
that
we
want
to
implement.
We
want
to
take
on
some
feedback
from
customers
before
going
into
like
further
completing
the
entire,
the
entire
epic,
the
second
one.
A
We
just
start
the
work
on
this
epic
in
this
iteration
and
we're
planning
to
continue
in
this
coming
iteration,
which
is
to
surface
the
include
filings
in
the
pipeline
editor.
Just
to
recap-
and
we
have
the
design
issue
here,
and
the
idea
is
to
surface
and
show
in
the
pipeline
in
the
pipeline
editor
the
files
that
are
being
included
in
on
your
pipeline
configuration.
A
One
of
them
is
to
allow
the
pipeline
to
to
trigger
whenever
the
draft
prefix
is
removed
from
the
title,
and
another
issue
is
about
the
usage
of
regular
expression
with
variables
in
rules
and,
lastly,
we
have
a
bug
that
we
want
to
solve
in
how
we
are
handling
a
parenchite
pipeline
and
with
variables
yeah.
That's
it
and
hope
you
find
this
useful
if
you
have
any
questions,
thoughts
or
feedback
feel
free
to
add
them
to
the
planning
issue.
Okay,
thank
you
and
bye-bye.
B
In
14.10
I'll
be
focusing
on
the
design
exploration
for
the
ci
cd
catalog
vision.
So
it's
a
really
big
effort
and
we're
working
together
as
a
team
to
go
to
the
discovery
process
and
uncover
as
many
questions
and
assumptions
as
possible
at
this
stage
and
then
validate
it.
So
to
learn
more
about
this
project,
you
can
check
out
this
epic
called
facility
catalog
ci
contribution
framework.
B
So
currently,
where
we
are
in
this
process,
is
right
now
we're
running
a
research
research
effort
to
better
understand
the
needs
around
ci,
cd,
catalogs
or
generally
safety
components
like
reusable
building
blocks
for
your
pipeline.
We're
trying
to
look
into
the
current
solutions
that
our
customers
are
using
to
help
us
inform
the
solutions
that
we're
working
on.
We
also
currently
have
the
engineers
working
on
a
spike
to
understand
what
is
possible
in
terms
of
implementation
and
all
of
us
all
of
this
information
feeds
into
the
design
exploration
that
we're
doing.
B
I
already
did
a
first
pass
on
the
ci
catalog
vision
in
14.9.
There
were
too
many
open
questions
and
unknowns,
and
we
were
having
to
adjust
our
direction
quite
a
bit.
Based
on
what
we've
learned
from
the
spike
issue
in
149,
so
in
14.10,
I
will
be
working
on
another
pass
on
the
cicd
component,
catalog
vision.
B
Now
now
that
we
have
a
bit
more
information
about
what
is
technically
feasible,
we
will
be
exploring
all
of
those
questions
in
more
detail
and
in
further
milestones,
we'll
be
doing
some
solution.
Validation
around
this.
So
in
this
design
issue,
if
you
scroll
down,
there's
multiple
threads
here
discussing
different
aspects
of
the
theistic
catalog,
such
as
the
component's
visibility.
How
should
it
work?
How
do
you
publish
and
publish
a
component
and
so
on
and
so
forth?
B
So
if
you
have
any
thoughts
on
this
feel
free
to
weigh
in
with
your
comments
or
questions,
we
would
certainly
love
to
hear
from
github
users,
as
well
as
the
members
of
other
gitlab
teams
on
this
matter,
and
my
other
focus
in
14.10
will
be
improving
the
usability
of
variables
very
excited
to
finally
start
working
on
this.
B
I
haven't
been
able
to
prioritize
it
in
the
past
milestones,
but
we
have
a
lot
of
very
interesting
problems
here
to
solve
so
one
is
to
allow
only
authorized
variables
to
define
to
be
defined
when
running
a
pipeline,
so
we
want
to
make
it
possible
for
our
users
to
run
pipelines
with
only
the
variables
that
have
been
approved
by
the
admin
of
the
project,
so
we're
exploring
different
solutions
here
and
in
14.10.
I
will
be
running
some
solution,
validation
and
another
interesting
problem
is
adding
another
type
of
variables
that
wouldn't
go
through.
B
Expansion
like
the
regular
variables
do
so.
Usually,
when
you
have
a
dollar
sign
in
your
variable,
the
variable
will
be
expanded
and
it's
processed
differently.
It's
not
necessarily
a
desired
behavior
or
expected
behavior.
If
you
have,
for
example,
a
password
with
a
dollar
sign
and
there's
some
other
characters
that
we
also
treat
differently,
that
doesn't
really
make
sense
to
treat
that
way
for
things
like
password,
secret
and
so
on.
B
So
we
have
a
whole
epic
of
different
related
issues,
and
I
will
be
working
on
diving
deeper
into
this
problem
space
and
exploring
how
we
could
solve
those
problems
in
a
holistic
way,
as
well
as
identifying
the
mvc
steps.
So
this
epic
was
created
quite
a
long
time
ago.
So
we
just
need
to
take
some
time
to
really
understand
the
problem
here.
B
So
yeah,
if
you
have
any
thoughts
on
these
problems,
feel
free
to
comment
in
the
issues
or
ping
ping
on
those
issues
or
you
can
also
reach
out
to
dove
and
yeah
most
exciting
issues
to
work
on
14.10.
Thank
you.