►
From YouTube: GitLab 16.4 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
Let's
go
hi
everyone.
This
is
davidovitz
I'm
here
with
Saint
John
Park,
and
this
is
a
pipeline.
Authoring16.4
kick
off
the
video
I'm
gonna
go
ahead
and
share.
As
always,
we
have
a
planning
issue
and
underneath
the
pipeline
authoring
group
getting
issue
number
one
or
two
we'll
start
with
the
goals
of
the
Milestone.
A
This
is
something
that
I've
explained
several
times
several
videos
and
we
are
doing
some
restructuring
of
component
making
sure
that
they
will
be
very
similar
to
template
it
that
will
allow
user
to
easily
migrate
from
component
to
template
and
then
leverage
the
catalog.
So
this
is
the
entire
Epic
and
the
third
priority
is
about
the
input
interpolation.
Okay,
so
I
also
discussed
this.
In
several
several
of
my
videos,
we
have
a
full
epic
about
input
enhancement,
but
this
time,
what
we
really
want
to
to
implement
is
the
ability
to
support
variables
in
input.
A
Once
we
do
that,
I
believe
this
will
be
the
right
time
to
move
inputs
from
beta
to
GA,
because
it
means
that
users
could
use
inputs
instead
of
variables
anywhere
everywhere
in
any
template,
and
so
hopefully
we'll
be
able
to
complete
that
in
time.
Another
front-end
related
issue
that
actually
is
ready
and
I'm
hoping
we'll
be
able
to
implement.
That
is
to
add
the
missing
information
on
the
on
the
downstream
job.
A
So
today,
when
you're,
looking
at
the
mini
graph
on
a
typical
pipeline,
you
can
see
all
the
jobs,
but
in
a
downstream
pipeline,
when
you
click
on
a
downstreet
pipeline,
it
will
actually
take
you
to
the
downstream
pipeline
and
it's
very
inconvenient,
because
users
like
to
interact
with
the
with
the
mini
graph
and
so
in
this.
In
this
Milestone,
we
are
hoping
to
have
the
ability
to
show
all
the
jobs
that
are
understood
inside
and
or
underneath
a
downstream
pipeline
in
the
mini
graph.
A
B
Thanks,
though,
let
me
share
my
screen
again
so
I
still
mentioned
ux
also
going
to
focus
on
the
cicd
catalog
for
sure
in
this
Milestone,
but
this
Milestone
is
a
little
bit
special,
because
I
am
going
to
just
focus
on
this
issue
only
for
now,
so
that
we
can
have
a
bigger
Vision
in
terms
of
the
user
flow
of
our
product,
based
on
the
understanding
of
the
user's
real
context
when
they
start
to
author,
their
philipsia
yaml
file
when
they
start
to
edit
their
yaml
file,
and
then
probably
that's
the
moment
that
they
want
to
start
looking
into
the
CI
components
catalog.
B
B
So
we'll
see
like
what
kind
of
outcome
that
we
could
come
up
with
these
issue
and
in
the
meantime,
there
is
one
active,
ux
research
efforts
going
on
so
I'm
not
going
to
share
too
much
details.
But
it's
about
the
picd
catalog
for
the
self-managed
customers.
Only
and
so
far
we
completed
four
interviews
with
the
customer,
and
then
we
like
to
just
see
like
the
research
Insight,
came
up
from
this
research
and
then
decided
to
move
on
on
This
research,
or
maybe
we
can
just
stop
this
research,
so
this
will
be
finalizing
16.4
as
well.
A
No
I
think
this
would
be
like
a
really
important
effort,
also
for
the
for
the
public,
catalog
or
the
instance
white
catalog,
which
would
like
to
deliver
for
in
the
self-managed
customer
and
we'll
see
how
it
will
how
it
will
evolve.
D.
A
Yeah
I
think
this
is
it
I
hope
everyone
find
this
recording
useful.
If
there
is
any
questions
you
can
reach
out
to
me
soon
June
or
send
a
slack
message
to
the
channel.
Thank
you.
Thank
you.