►
From YouTube: CI interpolation
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
I
just
want
to
emphasize
why
I
believe
this
is
something
that
really
can
change
the
way
all
of
you
are
constructing
pipelines
and
basically
I
assume
that
most
of
you
are
using
some
sort
of
a
CI
yaml
template
that
gets
included
into
your
pipeline
and
usually
the
way
to
pass
in
parameters
into
the
pipeline
is
done
to
variables.
And,
however,
we
know
that
variables
were
not
designed,
for
that
were
not
meant
for
that.
This
is
not
the
purpose
of
of
the
variables
and
because
variables
by
the
by
Design,
they
have
some
flows.
A
If
you
use
this
use
them
as
a
way
as
a
method
to
pass
inputs
variables
when
are
being
declared,
usually
declared
as
the
top
level
keyword
variable,
which
means
that
then
they
are
affecting
your
Empire.
Your
entire
pipeline,
so
every
variable
you
add,
actually
add
more
complexity,
because
this
variable
automatically
gets
added
to
any
file
or
any
job
that
you
include
any
template
that
you
include
and,
and
sometimes
you
have
some
conflicts
with
templates,
sometimes
templates
override
each
other.
So
and
and
even
every
time
that
you
had
a
job
to
your
pipeline.
A
You
need
to
take
into
consideration.
Okay,
what
are
the
global,
the
global
variables
that
I've
defined
in
my
top
level,
keyword
that
will
get
added
now
to
those
to
those
jobs
and
should
I
override
them
in
in
some
way
will
they
affect
my
pipeline
and
I?
Think
that,
with
input,
we
are
kind
of
like
a
eliminate
this.
A
This
problem,
and
we
also
added
a
few
more
things
that
I
believe
are
super
valuable,
a
super,
valuable
and
so
to
begin,
with,
the
way
to
declare
inputs
usually
is
being
done
on
the
pipe
on
the
pipeline
configuration
that
you
are
adding
that
you
are
including.
So
if
you
have
some
sort
of
a
template
of
a
yaml
that
is
being
included,
you
start
with
the
spec
input
and
which
is
the
reserve
keyword
for
declaring
inputs
and
then
you're
writing
the
inputs
that
you
want
to
use
now.
A
The
thing
is,
though,
those
inputs
are
only
scope
to
that
temp
to
that
file
to
that
yaml
file.
They
will
never
go
leaked
outside
of
that,
so
they
will
not
affect
any
any
pipeline
that
you
are
adding.
It
will
just
apply
to
to
this
template
and
the
jobs
that
you
are
defining,
so
you
are
defining
your
inputs
and
then
here
you
start
to
Define
your
your
pipeline
configuration.
So
this
is
like
a
this
is
a
job.
This
is
a
deploy
job.
A
It
has
a
stage
it
has
a
simple
script,
and
but
basically
a
this
script
is
using
the
inputs
that
we've
declared
in
here
and
another
interesting
thing
that
we've
added
or
important
thing
that
we
have
added
is
that
you
can
have
like
mandatory
and
optional
inputs.
So,
by
default,
any
inputs
that
you
will
use
that
you
will
add
into
your
to
your
template
will
become
mandatory
unless
you
define
a
default
input.
Okay,
so
if
you
default
value,
so
if
you
define
a
default
value,
this
is
not
big.
This.
This
input
became
optional.
A
You
don't
need
you,
don't
have
to
declare
it
and
you
can
also
Define
like
an
empty
input
if
you
want
so
in
empty
default.
If
you
want
so
I
think
this
is
like
the
the
the
second,
the
second
value
that
you
have,
which
declaring
a
mandatory
and
optional
inputs,
which
you
cannot
do
invaluable.
So
you
always
need
to
know
invariable,
which
variable
you
have
to
use,
and
here,
if
you
are
not
using
the
monitor,
input
will
immediately
stop
the
pipeline.
A
The
pipeline
will
not
run
we
say:
okay,
we
are
missing
those
inputs,
the
third
one,
the
third
value,
as
I
mentioned,
you
can
define
a
default
and
a
different
value
for
an
input
and
the
it's
a
common
ask
for
more
users
to
Define
and
default
value
for
variables.
So
now
you
can
do
that
with
inputs
and
I.
Think.
Lastly,
which
is
also
an
important
value
that
inputs
can
be
used
anywhere
in
your
pipeline,
configuration
unlike
variables
with
variables,
only
support,
specific
value
for
key
and
I
think
we
have
maybe
approximately
I,
don't
know.
A
I
didn't
count,
maybe
like
about
100
issues
about
supporting
more
and
more
valuables
in
different
areas
in
in
the
pipeline
configuration.
But
here
with
inputs,
you
can
basically
add
any
inputs
that
you
want
anywhere
in
your
pipeline
configuration
which
obviously
make
it
easier
for
you
to
customize
and
templatize
your
your
templates
now
I'm.
Sorry,
the
way
to
use
those
inputs-
and
this
pipeline
is
when
you
go
to
your
gitlab
ciml
file,
and
you
do
an
an
include
of
a
of
a
file
you
can
do.
A
Any
include
you
can
do
include
the
local
include,
template
and
basically
any
file
that
you're,
including
and
when
you're,
including
it
you
are
declaring
the
input
that
will
get
used
for
that
specific
input.
So
those
are
the
values
that
actually
will
go
and
propagate
or
will
be
replaced
when
the
pipeline
is
being
run.
So
obviously,
you
can
even
use
the
same
include
over
and
over
again
with
different
inputs,
and
with
that
let's
go,
do
a
simple,
a
simple
example.
So
if,
if
I'm
taking
the
same
the
same.
A
The
same
example
and
I
mean
the
web.
Id
and
I
have
those
two
files,
my
template
and
and
the
include
of
my
template
with
those
inputs.
Let's
say
that
I
want
to
use
I
want
to
add
something
to
my
pipeline.
Okay,
let's
say
that
I
want
to
use
I
want
to
add
the
environment.
Keyword
and
I
want
all
that
environment
to
declare
a
name
and
I
also
want
to
declare
a
URL
Okay
so
and
I
want
to
obviously
use
inputs
for
that.
A
A
Let's
use
the
website.
We
already
have
like
an
input
here:
let's
use
the
input
of
the
website,
which
is
the
one
that
is
here
and
then
we
are
using
this
value.
So
basically,
what
I
need
to
do
in
order
to
run
that
now,
I've
added
an
environment
if
I'll
try
to
run
it
like
this?
Basically,
so
if
I
try
to
run
it
like
this,
and
basically
the
pipeline
will
fail
and
say:
okay,
hey,
you
are
missing,
like
an
environment
as
an
input.
A
A
A
A
Yeah
I
think
that's
it.
Hopefully
you
find
this
recording
useful
and
the
inputs
useful,
and
if
you
have
any
feedback,
we've
created
a
dedicated
issue
to
capture
feedback,
so
try
it
out
basically-
and
we
are
including
you
encouraging
you
to
go
to
your
pipeline-
start,
try
to
replace
some
of
the
variables
with
inputs,
and
let
us
know
what
you
think.