►
From YouTube: GitLab 13.6 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
A
The
issue
number
one
make
it
possible
to
control
build
status
using
exit
code,
so,
as
you
probably
know,
any
any
job
that
have
the
exit
code
of
zero
in
in
in
gitlab,
it
means
that
the
pipeline
that
the
job
is
successful
and
the
pipeline
will
continue
to
earn
any
other
number.
Besides.
0
means
that
the
job
is
failing
and
most
likely
that
your
pipeline
will
stop
running.
A
This
issue
will
actually
help
you
map
it
differently
and
control
the
the
job
status
based
on
the
exit
code.
So,
for
instance,
if
we'll
take
a
look
at
this
example,
if
this
scape
will
return
zero,
one
or
two,
it
will
still
consider
as
the
job
was
still
considered.
A
success
and
the
job
in
the
pipeline
was
still
running
if
it
will
return
seven
or
fourteen,
and
it
means
that
it's
warning
eight
cancel
and
anything
else
is
failed.
A
So
this
issue
will
actually
help
our
users
that
have
scripts
that
generate
different
exit
code
and
there
are
plenty
of
those.
But
even
though,
if
the
exit
code
is
not
zero,
they
still
want
the
pipeline
to
continue
to
run,
and
they
want
this.
This
job.
To
be
successful
to
to
market
success,
so
this
issue
will
help
you
address
that,
and
it
is
a
very
popular
issue
as
you
can
see,
and
if
you
have
more
questions
you
can
lead
to
that
issue.
A
The
next
one
is
support.
Wildcard
when
specified
include
path
in
gitlab
ciaml,
and
it's
really
straightforward.
We
will
support
a
wildcard,
we'll
use.
The
include
word
to
the
path
of
your
yaml
file
and
the
next
one
is
allow
a
list
of
files
in
the
cia
include
and,
as
you
can
see
in
the
include,
even
though.
A
If
you
have
like
multiple
files
that
share
the
same
project,
we
still
need
to
list
them
in
this
way,
and
so
you
need
always
to
call
the
project
and
the
ref
and
the
file.
Although
they
are
the
same,
so
we
are
going
to
change
the
syntax
in
a
way
that
you
will
call
out
the
project
and,
for
instance,
the
left
only
one
time
and
the
file
will
accept
a
list
of
files.
A
I
hope
I
said
it
correctly,
and
we
do
that
when
we
use
the
needs,
keyword
and
needs
mean
that
a
certain
job
needs
a
certain
job
to
complete
in
order
to
run,
and
in
this
issue,
we've
introduced
a
need
to
refer
to
a
stage.
So
if
we
take
this
example,
for
instance,
my
job
needs
job
number,
one
job
number
two
and
job
number
three
to
one.
All
of
this
was
supported
up
until
today.
A
Next,
one
is
allow
configuration
overrides
for
for
the
rules
for
rule
syntax,
and
so
this
issue
actually
provide
the
ability
to
override
two
two
keys
variables
and
cache,
but
we've
decided
to
break
it
down
so
what
it
means.
It
means
that,
if
you've
configured
a
variable
in
your
in
your
workflow,
you
see
that
if
certain
conditions
are
met
in
a
job,
I
can
override
this
variable.
A
And
so
we've
introduced
the
new
keyword
override
overrides,
and
this
will
override
the
same
variable
that
I've
declared
here.
So
when
I'm
starting
this
pipeline,
my
val
actually
get
the
value
of
hello.
But
when
I'm
running
my
job
and
if
this
rule
is
true,
then
I'm
overriding.
Although
I'm
overriding
this
variable
that
I
defined
with
hello
too
and
in
the
second
iteration,
which
will
be
in
a
completely
different
issue,
we
will
allow
to
override
cache
as
well.
A
Validate
lint
in
the
editor
light
so
up
until
today,
in
order
to
validate
that
your
gitlab
ci
aml
configuration
is
correct.
You
either
need
to
copy
paste
it
to
to
the
ci
lint
or
try
to
hit
the
commit
button,
and
if
it
will,
if
it's
not
right,
then
it
will.
It
will
fail
and
in
this
issue
we'll
introduce
a
new
tab
next
to
your
edit.
So
you
can
edit
your
file
in
one
tab
and
then
just
simply
click
on
the
tab.