►
From YouTube: GitLab 15.9 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
Hi
everyone
this
is-
and
this
is
the
pipeline
authoring,
15.9
kickoff
video,
I'm
gonna,
go
ahead
and
share
my
screen.
You
can
see
the
planning
issue
and
issue
number
18,
one
underneath
the
public,
auto
group
and
we'll
start
with
the
goals
of
the
Milestone
and
the
goal
number
one
is
to
start
working
on
the
pipeline.
Court
catalog
phase,
one
which
will
include
introduce
spec
input
for
any
types
of
include
and
as
a
part
of
that
and
walk,
will
also
Force
mandatory
inputs
for
any
types
of
include.
Let's
go
ahead
and
explain
what
this
really
means.
A
So
in
order
to
allow
user
to
use
what
we
would
like
to
call
a
component
I
would
like
to
allow
user
to
declare
inputs
as
a
part
of
of
the
process
of
defining
or
using
a
component.
This
way
we
could
allow
user
for
easy
reusability
of
a
component,
so
you
can
include
the
same
component
over
and
over
again
with
with
different
inputs
and
the
way
that
it's
going
to
look
as
prerequisite
is.
A
We
will
support
all
types
of
include,
so
it
doesn't
matter
if
you're
using
a
local
local
configuration
file
project
remote
template
also
trigger
including
your
project,
meaning
the
parent
charge
pipeline
multi-posit
pipeline.
They
should
all
support
this
type
and
include,
and
when
you
include
you
included
with
the
inputs
that
you
would
like
to
use.
A
So
this
is
how
users
will
use
it
and
the
way
to
declare
It
Is
by
specifying
a
field
named
spec
input
and
spec
input
will
start
defining
the
different
inputs
that
you'd,
like
that
configuration
item
or
template,
or
basically
any
part
of
your
pipeline
configuration
that
you
can
include
you
could,
if
you
like,
to
Define
inputs
and
with
that
also
different
inputs,
as
I
mentioned
by
a
by
default,
all
inputs
are
required
and
if
you
already
Define
some
sort
of
a
default,
the
default
value
for
for
your
inputs,
then
it
means
that
it
is
optional.
A
So
when
you
are
including
it
with,
you,
don't
have
to
specify
it
and
the
way
to
to
create
your
configuration
is
using
this
this
bracket
and
basically
you
can
replace
any
any
key
in
your
pipeline
with
inputs
Dot,
and
this
is
the
inputs
that
you'll
use
so,
for
instance,
input.stage
will
use
this
stage,
and
if
you
include
the
file
with
different
stage,
then
it
will
replace
it
simply
replace
the
value
that
you've
defined
either
here
or
good,
with
with
the
value
that
you
you've
defined
yeah.
A
So
this
this
work
will
be
split
into
two
parts.
The
first
part
is
doing
the
interpolation
and
Declaration
of
spec
input.
The
second
part
which
will
probably
come
in
the
next
iteration,
will
be
the
usage
of
whip,
and
this
will
be
the
prerequisite
for
for
the
CI
catalog,
which
is
a
part
of
of
this
sub
epic.
So
we
have.
We
have
a
sub
epic,
and
this
is
the
Epic
and
in
this
epic,
you
can
dive
into
the
different
phases
that
we
are
working
on.
A
Now
we
are
starting
to
implement
phase
number
one
and
phase
number
two
is
discussion
on
the
blueprint,
so
we
are
doing
those
two
together
and
then
we'll
continue
with
phase
three
and
then
phase
four
okay
and
more
things
that
are
coming
is
the
ga
release
of
open
ID
connect.
It's
a
carryover
for
15
8..
We
I
think
we
are.
We
just
missed
the
in
the
lunch,
but
we
can
definitely
do
it
in
59.
A
we
have
some
ux
and
performance
enhancement,
and
one
thing
that
I
actually
want
to
call
out
is
that
work
that
we
are
doing
to
allow
user
to
withdrive
a
downstream
pipeline
using
a
retry
button
on
the
trigger
job.
So
it's
again
it's
a
part
of
a
bigger
epic
I
think
this
is
the
last
part
that
that
we've
left
to
work
on.
Basically,
we
are
going
to
add
the
retry
button
on
top
of
a
trigger
job
which
is
not
available
today
and
what
it
will
do.
A
It
will
actually
spin
out
a
completely
new
Downstream
pipeline,
unlike
recline,
a
downstream
pipeline,
which
will
retry
only
the
fail
and
cancel
job.
This
will
simply
recreate
a
downstream
pipeline,
as
you
can
see
a
really
top
wanted
feature
and
then
it's
a
feature
set.
It's
not
just
one
picture,
but
this
is
the
the
last
part
of
the
work
that
we
want
to
do.
A
And,
lastly,
we
will
have
time
we
will
start
working
on
this
epic,
which
is
to
expose
variable
in
gitlab
UI
and
there's
some
back-end
work
and
probably
going
to
more
depth
in
the
next
recording.
But
in
a
nutshell,
we
would
like
to
allow
users
to
view
the
value
of
of
the
variable
scope
per
job.
So
we
might
have
some
time
to
start
working
on
the
on
that
issue
and
that's
it
starting
the
next
iteration.