►
From YouTube: GitLab 12.5 Kickoff - Verify: Continuous Integration
Description
A
Hey
everyone:
my
name
is
Jason
Linney
and
I'm.
The
product
manager
for
continuous
integration
here
I
get
that
I
want
to
talk
a
little
bit
about
some
of
the
exciting
things
that
we
have
upcoming
in
our
12.5.
Milestone
first
step
is
that
we're
adding
support
for
defining
the
FCI
EML
outside
of
the
repository?
A
You
already
have
the
ability
to
move
it
around
within
the
repository,
but
this
will
allow
you
to
point
to
it
internal
project
at
an
arbitrary
URL,
and
this
will
enable
a
lot
of
different
use
cases
where
the
configuration
is
held
outside
a
good
example
of
this
is
open
source
projects,
maybe
where
you're
building
using
git
lab
CI.
But
you
don't
want
to
change
the
project
that
you're
building
and
you
can't
or
you
can't
insert
a
div
IMO
into
the
project.
A
Another
use
case
is
actually
the
second
issue
here
about
protecting
it
live
CIL
from
changing
by
developers.
This
is
a
feature
that
we've
had
requested
for
some
time
and
we're
going
to
be
implementing
it
using
the
same
approach
so
protecting
a
gate
lab
CA
a
opportunity
by
developers
will
be
doable
by
moving
it
into
a
different
project
with
a
different
set
of
permissions
users
numbers,
and
that
will
make
it
possible
to
do
this
in
a
pretty
natural
and
easy
way.
A
We're
also
adding
the
ability
to
keep
the
latest
artifact
for
every
job
and
what
this
does
is
it
makes
it
so
that
you're
always
guaranteed
to
have
the
latest
artifact
for
the
jobs
that
run
in
your
pipelines.
What
you
can
do
with
this,
then
is
set
a
very
aggressive
exploration
policy
on
artifacts,
so
that
you're
not
using
up
much
disk
space
on
an
ongoing
basis,
but
still
always
confident
that
you've
got.
You
know
the
latest
artifacts
that
you've
built
and
it's
it's
gonna,
be
a
good
way
to
just
make
that
a
lot
easier.
A
It
was
always
difficult
to
tune
the
trying
to
keep
the
latest
and
trying
to
have
a
good
expression
policy,
and
this
will
make
that
much
much
simpler.
We're
also
adding
cross
build
cross
project.
Artifact
dependencies
and
what
this
means
is
that
you'll
be
able
to
say
that
a
job
in
the
current
pipeline
that's
running,
has
dependency
on
artifacts
from
another
project,
another
ref,
the
last
successful
a
version
of
this
job,
for
example.
A
We're
also
adding
the
ability
is
the
commit
Shah
in
the
cache
key,
and
this
is
going
to
make
it
a
lot
easier
to
cache
things
and
only
invalidate
the
cache.
If
the
file
has
changed,
it's
a
little
tricky
to
do
that
today,
it's
a
little
bit
more
difficult
than
it
needs
to
be,
and
this
is
popular
change
that
we've
actually
been
able
to
come
up
with
a
solution.
A
We're
also
finishing
up
triggering
a
pipeline
when
you're
another
project
is
rebuilt.
This
is
an
ee
feature
where
you
can
set
a
project
to
automatically
trigger
itself
when
the
master
branch
on
another
project
is
built
for
certain
use
cases
where
this
is
handy.
If
you've
got
microservices,
not
in
a
modern
repo
situation
to
spread
out
amongst
a
bunch
of
different
projects,
then
this
kind
of
thing
can
be
useful.
A
If
you
have
complex
networks
of
dependencies,
then
it
can
also
be
useful,
but
there's
our
MVC
of
this
feature
and
yeah
also
looking
forward
to
getting
that
whenever
we're
improving
the
way
that
we
show
variables
in
the
project
view
that
were
inherited
right
now,
it
can
be
a
little
confusing
if
you're,
looking
at
the.
If
you're
looking
at
a
project
view
of
variables,
you
can
only
see
the
list
of
things
that,
were
you
know,
configured
in
the
current
environment.
A
We're
going
to
be
adding
this
section
here,
which
will
just
show
the
keys,
but
you
can
be
aware
then,
where
these
are
coming
from
and
if
you
click
on
this,
for
example,
it'll
take
you
to
where
that
that's
actually
defined.
If
you
have
permissions
to
see
that
and
that's
a
nice
quality
of
life
improvement
there
and
then
finally,
simplifying
includes
by
flattening
the
before
script
script
and
after
script.
A
This
is
a
pretty
technical
item,
but
it's
just
gonna
make
it
a
lot
easier
to
do
includes
in
a
more
coherent
and
powerful
way
by
flattening
these
arrays
at
the
moment,
they're
sort
of
baked
into
arrays,
arrays,
yeah,
disassemble
them
and
sometimes
depending
on
how
your
script
works.
It's
not
not
quite
possible
to
do
that,
but
yeah
this
will
make
things
merge,
able
and
easy
to
use.
A
So
that's
it
for
the
release
hopefully
saw
something
in
there
that
you're
excited
about
yeah
we'd
love
to
hear
your
feedback
on
what
we're
delivering
feel
free
to
jump
into.
The
issues
feel
free
to
reach
out
to
me
directly.
I
would
love
to
hear
from
you
thanks
and
we'll
be
in
touch
when
we
actually
deliver
this
stuff
back
to
you
soon.