►
From YouTube: Variables improvements GitLab CI
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
everybody,
my
name,
is
kovitz
and
I'm
here
to
share
with
you
some
of
the
work
that
the
team
had
been
walked
on
for
the
past
three
to
four
iteration
I'm:
happy
to
say
that
we
were
able
to
get
all
of
those
issues
that
I'm
going
to
share
share
with
you
out
of
the
door
and
ready
in
time
for
15.7,
so
without
further
Ado.
Let
me
share
my
screen
and
yeah
I
want
to
start
by
like
recapping.
A
What
is
the
issues
that
we've
implemented
and
so
three
of
the
most
top
wanted
feature
and
the
first
one
is
specify
variables
when
we're
trying
a
manual
job.
You
can
see
pretty
component
feature
and
the
second
one
is
using
a
dollar
character.
You
know
special
character
in
build
variable,
which
is
also,
as
you
can
see,
a
lot
of
users
reacted
with
different
icons
and
the
last
one
is
set
a
predefined
list
of
value
of
CI
environment,
variable
and
surface
them
in
the
on
Pipeline
to
H4,
as
you
can
see,
also
really
top
wanted
features.
A
So
I'm
gonna
show
you
how
each
it
looks
like
behave
and
what
is
the?
What
is
the
benefit?
The
user
will
get
and
yeah,
let's
start
with
specifying
a
variable
when
recline
a
manual
job
the
the
problem
that
users
experience
is
that
when
they,
when
they
run
a
manual
job,
we
were
able
to
allow
them
to
input
variables
in
the
first
one.
But
if
they
would
like
to
redrive
that
manual
job,
they
there
wasn't
an
option
for
the
user
to
update
those
values.
A
So
the
first
variable
that
you
enter
when
you
first
run
a
manual
job.
Those
will
be
the
only
variable
that
the
user
could
inject
to
a
job.
Now,
as
you
can
probably
guess,
many
users
wanted
to
update
those
variables
because
sometimes
they
want
to
run
the
same
job
with
different
variables.
Sometimes
it
was
just
like
a
typo
and
there
wasn't
an
option
to
do
that.
So
now,
when
go
to
a
job,
which
is
a
manual
job,
we
go
to
the
job
page
and.
A
With
this
way
to
input
viable
and
I
know
that
I
have
a
variable
that
I
called
it
my
valve
and
let's
input
it
as
test
one,
and
then
I
can
trigger
this
manual
lecture
now.
This
was
the
only
time
users
were
able
to
inject
a
variable
into
a
manual
job.
Now,
the
the
pipe
the
job
will
run
and
you'll
be
able
to
see
that
this
variable
will
get
printed
and
there
wasn't
an
option.
Yes,
this
job
is
successful.
You
can
see
this
is
my
Val
last
one.
A
So
now
what
we've
added
we've
added
this
drop
down,
as
you
can
see
previously
before
we've
implemented
this
change.
Users
were
only
able
to
run
it
again,
but
now,
with
this
drop
down,
users
can
either
run
it
again
or
update
a
cicd
variable
and
I
can
click
on
this
button
and
then
I'll
be
redirected
to
the
same
page
and
I
can
I
can
add
different
variable
value
and
run
this
job
again
and
obviously
it
will
print
the
variable
with
the
new
application.
A
A
Now,
the
dollar
character
of
any
special
kind
of
character
is
very
common
and
in
in
secrets,
and
the
problem
is
that
when,
before
we
introduce
this
feature,
whenever
someone
used
the
dollar
sign
in
a
value
it,
it
referred
to
as
valuable
expansion,
so
a
variable
that
is
actually
calling
a
variable,
and
but
since
we've
introduced
a
new
type
of
variable,
that
is
called
the
row
variable
now.
Users
are
able
to
set
the
variable
to
be
a
row
variable
meaning
do
not
expand
this
variable
when
I'm
using
the
dollar
sign
I'm,
not
calling
another.
A
Another
variable
just
use
the
the
character,
as
is,
and
let's
see
how
it
looks
like,
and
so
you
can
see
here
in
this
section-
I've
defined
two
jobs
so
two
variables,
one
with
the
value
of
your
job
ID,
which
is
a
predefined
variable
and
I've
added,
like
the
dollar
sign
and
one
with
another
predefined
variable,
which
is
CI
underscore
job
name.
I
can.
Actually
you
can
actually
call
it
the
same
one?
A
Okay,
so
we
can
understand
the
the
difference:
okay,
so
I'm
I'm,
adding
the
same
value
but
in
the
job
underscore
ID,
I'm,
sorry,
I'm,
adding
the
flag,
the
flag
expand
tool
which
is
like
the
new,
the
new
flag
that
we've
added
and
then
the
job
underscore
ID
underscore
too
I'm.
Adding
the
expand,
Force
meaning
do
not
expand
this
variable
Now
by
default.
The
expand
these
two,
so
this
is
actually
and
like
I.
A
Can
I
can
comment
this
this
line
and
will
be
the
same,
but
basically
by
default
when
you're
using
a
dollar
sign,
it
will
be
explained,
and
you
need
to
explicitly
mention
in
your
CI
configuration
that
you
do
not
want
to
expand
the
variable
and
take
the
value,
as
is
now.
A
Okay,
so
you
can
see
that
I'm
the
time
echoing
the
two
variables
that
that
I
have
defined
and
one
of
them
I
call
the
job
ID
and
the
job
underscore
and
CI
underscore
Joe
Biden.
So
this
is
the
job
ID,
so
it
actually
the
valuable
and
took
the
value
of
the
variable
of
the
predefined
variable
and
the
second
one
actually
took
the
variable,
as
is
so
did
not
expand.
This
variable
did
not
expand
this
value
in
literally
use
the
dollar
sign,
as
is-
and
this
is
as
I
mentioned.
A
This
is
quite
common
when
using
the
dollar
sign
in
on
your
value,
and
we
allow
users
to
set
it
as
you
could.
So,
as
you
saw
in
the
in
the
pipeline
configuration,
but
also
there
is
an
option
to
do
it
in
the
UI,
which
is
more
common,
I
would
say
so.
Whenever
you
go
and
Define
your
variable
today,
there
is
another
flag
which
is
expanded.
A
Let's
add
it.
As
you
can
see,
there
is
like
a
new
checkbox
and
if
I'm
like
using
a
value
and
I'm,
adding
the
dollar
sign,
you'll
be
pumped
with
with
this
warning
saying,
value
might
contain
valuable
reference
because
we
are
referring
to
another
variable
and
if
I'm
unchecking
this,
then
it
means
that
it
will
use
this
value
and,
as
is,
and
if
I'm
unchecking
it.
It
will
actually
try
to
call
this
variable
if
it
exists
Okay.
So
we've
allowed
users
to
configure
it
through
both
ways
to
yaml
and
through
the
UI.
A
A
Pipeline
okay,
so
you
can
see
that
by
default,
I
was
pumped
with
the
name
name
of
the
variable
type.
Okay,
the
name
of
the
variable
and
the
value
now
up
until
today,
users
could
only
set
one
value
so
like
this,
and
this
was
was
supported.
What
we've
added
we've
added
the
option
for
user
to
configure
and
predefined
list,
and
it
will
be
show
display
as
a
drop
down
box
and
users
could
actually
choose
which
variables
they
would
like
to
sell
it
now.
A
This
is
very
handy
because
normally
the
person
that
is
running
the
pipeline
is
not
the
same
person
that
is
configuring
the
pipeline.
So
they
don't
know
what
is
the
value
that
they
need
to
add
to
the
to
the
predefined?
Let's
do
the
predefined
variable
in
case
there
are
multiple
options.
There
is
like
one
option,
then
it's
not
a
problem,
but
normally
when
the
different
parameters
that
you
need
to
configure
to
the
same
and
to
the
same,
to
the
same
variable,
then
it's
very
hard
for
them
to
know.
Okay,
what
is
the
value?
A
Usually,
what
users
have
been
doing?
They
use
the
manipulate
the
the
description
and
in
the
description
they
wrote.
What
are
the
options
or
maybe
in
the
comments,
but
then
users
would
need
to
go
to
the
pipeline
configuration
and
see
and
look
for
the
definition
of
the
of
the
of
the
variable
and
then
seeing
the
comment:
what
are
the
available
and
what
are
the
available
values?
So
now
it's
very
easy
straight
and
forward.
They
can
actually
see
there
is
a
drop
down
and
they
can
see
what
are
the
options
the
way
to
configure.
A
The
name
then,
the
default
value
that
will
be
presented
by
default
when
you
first
click
on
one
pipeline,
it
is
staging
and
then
you
can
specify
the
options
and
you
can
specify
more
and
more
options
and
obviously
also
the
description
which
is
similar
to
the
way
we've
defined.
A
single
and
a
single
variable.
The
way
to
define
a
single
predefined
variable
is
those
three
lines
which
was
already
available
for
users
and
we've
added
this
option
and
to
allow
users
to
specify
multiple
options
and
then
select
the
options
that
they
would
like
to
to
choose.