►
From YouTube: Example GitLab Demo (SDR Enablement)
Description
Here is an example demo to be used as an example for demoing GitLab. The specific features that we talk about are SCM, planning, CI, and security.
Speaker: Christopher Wang
LinkedIn: https://www.linkedin.com/in/christopher-wang-0835b226/
A
Again,
this
is
Chris.
Wang
I
have
an
example,
demo
that
you
can
use
for
Google
classroom,
and
the
goal
of
this
is
to
show
you
what
we're
looking
for,
and
oh
so,
to
give
you
a
really
simple
template
that
you
can
use
for
your
own
demo,
so
we're
hoping
that
this
will
take
about
an
hour
to
an
hour
and
a
half
of
your
time.
So
if
you
have
any
questions
with
this,
let
me
know,
and
with
that
I'm
just
gonna
dive
into
exactly
how
I
demo.
A
If
this
were
a
customer
presentation,
everyone,
my
name
is
Chris
Wang
I'm,
a
Solutions
Architect
here
at
gitlab,
and
now
that
I've
talked
through
some
of
now
that
I've
heard
some
of
your
use
cases
and
some
of
the
things
that
you're
trying
to
do
in
your
organization.
I
really
feel
like
it
lab
can
help
you
with
a
lot
of
these
initiatives
that
you
have.
A
So
over
here
is
the
gate
lab
project.
One
of
the
things
that
you
can
see
about
it
is
that
we
can
go
back
and
see
what
our
code
looks
like
at
any
given
point
in
time.
So,
if
I
check
click
on
this
history
section,
you
can
see
all
the
changes
that
are
happening
and,
as
you
can
see,
this
is
an
extremely
popular
project.
We
have
maybe
10
to
15
different
changes
that
are
happening
every
hour.
A
We
can
also
descend
into
what
each
change
is
right,
so
we
can
see
that
about
an
hour
ago,
one
of
my
colleagues
Nick.
He
actually
pushed
this
specific
change.
So
that's
really
great,
but
on
top
of
it,
one
of
the
things
that's
kind
of
unique
about
gitlab
is
that
we
also
have
versioning
for
each
specific
file.
So
if
we
go
to
a
file
such
as
this,
I
can
actually
see
the
history
of
this
file
and
how
it's
changed
in
time.
A
Another
thing
I
like
to
show
off
is
just
our
web
IDE,
and
so
what
I
mean
by
this
is
that,
if
someone's
not
technical,
they
can
come
in
and
make
changes
to
this
repository
without
having
to
understand
all
the
command
line.
Things
and
one
of
the
things
that
we
really
believe
here
as
part
of
gitlab,
is
that
everyone
should
be
able
to
contribute,
and
we
make
this
easy
by
lowering
the
barrier
to
entry
for
our
tools,
and
this
is
a
great
example
of
this.
A
So
someone
who's
new
doesn't
fully
understand,
get
can
come
in
and
he
can
actually
make
new
changes
right
over
here
and
if
he
has
to
adequate
promotion.
So
you
can
just
commit
right
to
the
repository.
So
once
again,
he
can
do
everything
for
the
web
browser.
He
doesn't
have
to
learn
the
command-line
tools,
ultimately
having
a
quicker
on
ramping
time
and
easing
the
ability
for
him
to
contribute
to
our
projects.
A
Now
that
we've
talked
about
source
control
management,
let's
talk
about
some
of
our
planning
functionalities.
So,
if
you're,
using
JIRA
or
something
like
this,
one
of
the
things
I
like
to
say
is
that
we
have
a
lot
of
the
functionality
over
here,
but
it's
all
integrated
together.
You
know
they
get
a
platform
itself
over
here.
You
can
see
all
the
work
items
that
are
coming
in
once
again,
because
this
is
a
very
large
project.
A
We
have
over
30,000
open
issues
and
that's
why
we
give
you
a
lot
of
really
great
ways
to
organize
these
issues
then
make
sense
of
everything
over
here.
You
can
see
that
you
can
create
different
issue.
Ports
so
get
labs,
a
very
big
organization.
We
have
a
front-end
team
with
a
back-end
team.
We
have
multiple
security
teams,
we
have
multiple
test
teams,
and
so
each
of
our
teams
generally
has
its
own
board.
But
you
can
organize
this.
However,
you
want
you,
can
have
each
team
habits
board.
You
can
organize.
A
You
can
have
each
project
habits
board
and
we
really
make
this
just
a
really
flexible
way
for
you
to
organize
your
information
over
here.
If
you're
a
manager
coming
in,
you
can
see
exactly
what's
needed
in
terms
of
your
project
and,
what's
remaining
so
as
these
tickets,
it's
closed,
everything's,
going
to
end
up
in
the
closed
column,
and
that's
when
we
know
when
we're
getting
closer
to
a
release.
A
Another
view
that
we
have
that's
really
great
is
that
we
can
have
milestones,
and
so
what
a
milestone
is
is
it's
basically
a
group
of
issues
so
over
here
you
can
see
that
this
10.1
milestone
includes
all
of
the
69
issues
of
version
10.0
of
gitlab
and,
if
I'm,
the
descendant
of
this.
This
is
a
closed
milestone,
because
this
release
has
already
happened.
A
You
can
see
all
the
issues
that
have
already
happened,
and
one
of
the
things
that's
really
great
here
is
that
we
give
you
a
burn
down
chart
now,
because
this
is
already
a
closed
milestone.
You
can
see
that
this
is
a
flat
line,
but
you
know
if
this
were
an
ongoing
project.
You
can
see
the
number
of
outstanding
issues
decrease
in
time.
A
Now
that
we've
talked
about
some
of
our
functionality
surrounding
issues.
Let's
talk
about
CI
and
how
everything
fits
together.
So
one
of
the
things
I
like
to
say
about
CI
is
we
really
are
a
complete
solution
and
because
everything's
integrated
together,
we
can
save
you
time
with
out
of
box
solution
for
getting
everything
up
and
running.
A
So
this
is
all
the
merge
requests
that
are
coming
into
our
project.
As
you
can
see
once
again,
this
is
where
collaboration
happens.
So
all
of
what
one
of
the
benefits
of
git
lab
is
because
so
many
different
teams
have
functionality
around
it,
so
many
different
people
can
actually
see
what's
happening
and
also
be
able
to
dialogue
and
the
changes
that
are
happening
to
your
project
during
the
merge
request
process.
So
here's
a
specific
merge
request.
What
I
basically
mean
by
this
is
look
at
all
the
collaboration
that's
happening.
A
Typically
in
solutions
such
as
you
know,
a
traditional
SCM
solution,
most
of
your
developers
will
be
on
it.
Sometimes
your
operations,
people
will
be
on
it.
Your
security
engineers
probably
have
their
own
tool,
but
the
benefit
of
having
one
integrated
solution
that
spans
the
entire
DevOps
lifecycle
is
that
everyone
can
see
what's
going
on
and
everyone
can
collaborate
together.
So
that's
one
of
the
really
great
benefits
of
something
like
git
lab.
A
We
also
integrate
our
CI
into
our
merge
request
view,
and
so,
as
you
can
see,
once
a
merge
request
comes
in
then
this
entire
pipeline
gets
triggered,
and
so
that's
obviously
the
test
that
we're
running
like.
More
importantly,
that's
a
lot
of
the
security
functionality
that
we
have
built
indicate
lab,
and
so
this
is
the
idea
of
what
we
call
shifting
left
with
git
lab.
We
have
the
ability
to
actually
find
out
about
security
vulnerabilities
before
they're
introduced
through
our
CI
process
itself.
A
If
I
were
to
sum
everything
up,
because
git
lab
is
an
integrated
solution,
there
are
a
lot
of
added
benefits
and
one
of
the
most
major
ones
of
those
is
because
all
of
our
different
teams
are
using
the
same
tool.
We've
really
enhanced
collaboration
make
everything
we
decrease
silos
in
our
organization.
So
that's
my
quick
demo
and
get
lab.
Let
me
know
if
you
have
any
questions.
Thank
you.