►
From YouTube: Continuous Integration Demo (SDR Enablement)
Description
Here is an example demo for GitLab CI. For use with SDR Technical Development (Google Classroom).
Speaker: Christopher Wang
LinkedIn: https://www.linkedin.com/in/christopher-wang-0835b226/
A
Hey
my
name's
Chris
Wang
I'm,
a
Solutions
Architect
here
at
get
lab,
and
today
we're
gonna
be
talking
about
our
CI,
so
diving
right
into
it.
We
believe
that
our
CI
integration
is
best
in
a
class,
and
so
what
we
mean
by
that
is
that
we
really
believe
that
this
is
when
they
unique
differentiators
that
we
have
as
a
product,
and
I'm
gonna
be
talking
about.
A
Why
today,
so
the
main
reason
why
our
CI
is
so
great
is
because
it's
completely
built
into
get
lab
itself,
so
you,
as
opposed
to
needing
multiple
tools
like
github
and
jenkins,
everything's,
all
integrated
together,
making
it
easier
for
you
save
you
time
and
money.
How
this
all
works
is
that,
as
you
can
see,
this
is
the
repository
for
it
lab
itself
and
there's
this
actual
file
that
we
keep
in
the
repository
called
the
git
lab
CI
mo
file,
and
this
is
basically
how
all
of
the
CI
a
works.
A
This
is
where
we
tell
the
jobs
what
to
run
when
to
run,
and
things
like
this,
and
so,
as
you
can
see
over
here.
This
is
when
we
specify
the
stages
that
we
want
to
run
for
our
CI
after
each
merge
request
comes
in,
as
you
can
see,
here's
all
the
merge
requests
that
come
in
this
is
when
developers
are
pushing
out
their
new
code
changes,
and
the
great
thing
is
that
all
of
the
CI
runs
in
the
background
right.
So
you
don't
need
a
developer
coming
off,
triggering
a
job
running
tests.
A
You
don't
need
to
go
into
Jenkins.
You
know
manually
launch
something
all
this
happens
automatically
and
that's
really
the
beauty
of
gitlab,
let's
descend
into
a
specific
merge
request,
as
you
can
see
that
this
is
a
merge
request
that
touches
many
different
groups
in
many
different
parts
and,
as
you
can
see
over
here
in
this
pipelines
view
all
of
these
pipelines
run
in
the
background
seamless,
and
so
we
have
many
different
stages
here
prepare
build.
But
the
main
thing
that
I
want
to
talk
about
here
is
this
test
stage.
A
A
Once
again,
you
don't
have
to
login
to
Jenkins
another
platform
to
trigger
a
job
everything's
automated,
ultimately,
saving
your
developers,
time
and
reducing
human
error,
and
the
great
thing
about
all
of
this
being
built
into
the
CI
platform
itself
is
that
in
your
merge
request
view
you
can
actually
see
the
results
of
everything
right
so
developers
when
they're
discussing
you
know
things
that
they
like
and
they
don't
like
and
they're
arguing
about
things.
They
can
actually
look
at
the
test,
results
and
reference
them,
and
so
that's
really.