►
From YouTube: CI - Ease Of Configuration
Description
CI - Ease Of Configuration
Learn@GitLab - The ease of configuration with GitLab CI
Get in touch with Sales: http://bit.ly/2IygR7z
A
Hello,
my
name
is
a
second
bubble
and
I'm
going
to
talk
about
the
few
capabilities
that
make
Tim
walk
more
efficient
to
maximize
development
time
and
improve
team
productivity.
You
will
need
a
tool
that
will
allow
you
to
automate
everything
or
almost
everything
you
do.
In
addition,
this
tool
must
be
easy
enough
to
configure,
so
you
will
focus
most
of
your
time
on
developing
and
less
on
configuring.
A
A
Let
me
show
you
an
example
of
how
I
configure
my
build
and
test
automation
with
a
few
clicks
in
the
web
UI.
This
is
a
github
project.
I've
just
pushed
my
java
code
to
its
repository
now.
I
want
to
set
up
a
continuous
integration
pipeline
or
in
other
words,
I
wish
that,
for
each
code
commit
pushed
to
this
repository,
it
will
automatically
be
built
and
tested
I'm
lucky
because
in
grid
lab
I
have
to
do
nothing
to
set
it.
I
just
have
to
enable
it
via
the
web.
A
A
New
continuous
integration
pipeline
just
started.
It
will
build
and
test
my
code
and
even
push
it
to
the
container
registry,
so
it
will
be
ready
to
be
deployed
to
test
or
production
environments,
but
what,
if
I,
have
to
customize
the
configuration,
for
example
and
remove
some
automation
jobs?
How
can
I
make
this
customization
editing?
The
CI
configuration
is
done
in
the
ml
file.
This
file
is
part
of
your
repository
and
you
can
edit
it
with
any
editor
and
commit
the
changes
like
it
was
any
file
in
your
code.
A
A
A
A
In
case
I
have
to
use
passwords
or
secret
keys
in
my
jobs,
I
can
define
those
keys
as
parameters
via
the
web
UI
once
the
parameter
is
ended,
I
can
call
it
in
the
ml
file.
This
keeps
my
ml
file
secured,
as
we
have
just
seen
with
the
right
tool
that
does
the
hard
work
for
you.
Dev
teams
can
focus
on
their
applications
instead
of
configurations
thanks
for
watching
it.