►
From YouTube: TT310: Demoing GitLab (Leadership Flow)
Description
This is a sample customer demo for TT300.
For more on Tanuki Tech, see here: https://about.gitlab.com/handbook/marketing/revenue-marketing/sdr/tanuki-tech/
For more on the speaker, see here: https://www.linkedin.com/in/christopher-wang-0835b226/
A
A
Do
you
see
my
screen
all
right,
great
yeah,
so
this
is
get
lab
and
specifically
this
is
get
lab
running,
get
lab
itself.
So
here
we
have
all
the
get
lab
source
code
and
you
can
see
all
of
our
sem
capabilities
here,
so
anything
that
you
have
in
a
github
or
a
bit
bucket.
We
have
the
exact
same
functionality
here,
and
so
this
is
your
complete
versioning
system.
A
A
A
So
we
make
the
barrier
to
entry
for
contributing
to
our
project
low
someone
who,
without
a
technical
background,
they
can
still
make
changes
here
all
through
the
web
id
without
needing
to
know
all
the
get
cli
commands.
So
if
I
wanted
to
change
something
here
and
new
text,
then
it's
very
easy
to
do
so.
A
So
that's
the
sem
side
of
things:
let's
actually
take
a
look
at
some
of
our
features
surrounding
workflow,
so
a
discrete
unit
of
work
in
gitlab
is
called
an
issue
and
here's
a
sample
issue.
So
this
is
the
add
a
chart
to
one
of
our
views
and
one
of
the
things
that
we
are
really
really
great
and
one
of
the
things
that
differentiates
us
from
many
of
the
other
tools
out.
There
is
because
gitlab
is
an
all-in-one
solution.
A
A
It
also
has
functionality
for
security,
for
tests
and
for
devops,
and
so
all
of
these
teams,
once
they're
consolidated
onto
gitlab
himself,
you
have
more
collaboration
across
your
organization
allowing
for
better
products
and
for
just
like
better
quality
work
and
I'll
show
you
what
I
mean
so
here's
the
discrete
unit
of
work
someone's
describing
what
they
need
to
do.
There's
proposals
and
things
like
that,
but
oversee
you
can
see.
People
are
collaborating
on
this
issue
itself,
and
so
this
could
be
someone
from
test.
This
could
be
someone
from
a
different
engineering
team.
A
This
could
be
someone
from
security
and
one
of
the
unique
things
that
we
have
about
get
lab
is
because
there's
so
many
different
teams
using
it.
We
have
higher
quality
collaboration
across
our
enterprise.
So,
ultimately
speaking,
this
creates
higher
quality
work
over
here
on
the
right.
We
have
some
of
the
different
functionalities
that
we
have
built
into
issues.
As
you
can
see,
you
can
assign
an
epic
or
milestone
other
things
that
you
could
do
from
an
accountability.
A
A
So
if
this
is
a
really
important
issue,
then
we
can
give
it
a
higher
weight
health
status
and
we
have
other
functionality
like
locking
issues
in
case
this
of
something
that
you
know,
people,
it's
just
another
control
that
we
have
built
into
this.
So
this
is
the
issue
view
and
milestones.
A
It's
basically
a
group
of
issues.
So
if
I
have
20
issues
that
are
surrounding
you
know,
one
part
of
my
website
are,
if
you
know
I'm
trying
to
it's
just
a
way
of
grouping
issues
together
and
so
on
the
bottom.
You
can
see
all
of
these
issues
that
have
to
do
with
this
grouping
over
here.
A
We
have
aggregated
all
of
our
issues
for
a
specific
release,
so
you
can
see
all
of
the
get
lab
13.1
issues
here
and
one
of
the
things
that
we
give
you
is
a
burn
down
chart.
So
a
lot
of
times
management's
not
entirely
sure
when
you
know
our
release
is
going
to
be
due,
but
just
by
showing
this
burn
down
chart
we
actually
have
a
really
great
gauge
of
when
works.
A
Here's
our
epics
view
it's
not
working
right
now,
but
this
is
just
another
way
of
grouping
issues
all
right.
So
now
that
we've
talked
about
issues,
let's
talk
about
how
our
developers
solve
these
issues
from
a
gitlab
perspective.
So
what
we
do
is
we
have.
This
thing
called
a
merge
request
and
what
our
merge
request
is:
is
the
ability
for
developers
to
change
code
and
ultimately
solve
issues,
so
it
could
be
creating
this
new
button.
A
It
could
be,
you
know,
adding
in
a
new
chart,
and
so
this
is
the
description
for
the
change
that
they're
trying
to
make
and
once
again
people
are
collaborating
on
this
right.
So
the
value
of
gitlab
and
one
of
the
one
of
the
really
great
differentiators
for
gitlab
itself
is
the
ability
for
so
many
different
teams
to
use
the
same
tool.
So
we
can
see
that
people
are
going
back
and
forth.
Some
of
these
people
could
be
from
the
test
team.
A
Some
of
these
people
could
be
from
a
security
team
and
all
of
this
communication
and
collaboration
ultimately
creates
higher
quality
work
over
here.
If
I
go
in
the
changes
section,
we
can
see
all
of
the
individual
changes
that
this
engineer
is
trying
to
make
all
the
green
text
is
the
text
that's
trying
to
be
added
we're
trying
to
swap
out
this
red
text
and
that's
fundamentally
what
this
merge
request
is.
A
So
one
thing
I'd
like
to
point
out:
is
this
pipelines
view
this
is
one
of
the
really
great
differentiators
for
gitlab.
We
allow
you
to
have
ci
automatically
built
in
so
no
one
had
to
go
in
and
click
a
button.
All
of
these
ci
jobs
got
triggered
automatically
and,
as
you
can
see,
there's
many
different
jobs
that
we're
running.
So
the
first
stage
is
to
prepare
artifacts,
then
we're
going
to
build
container
images,
and
then
we
have
this
great
test
section.
A
A
In
this
view,
if
you
don't
want
certain
of
these
items
or
if
you
want
additional
items,
it's
completely
something
that
you
can
tailor
to
your
own
specific
organization,
and
if
you
go
into
here,
you
can
see
that
literally
all
we
have
to
do
is
modify
some
of
the
stages
that
are
here
and
define
what
these
stages
do.
So
this
is
the
gitlab
ci
dot
yaml
file,
it's
a
file,
that's
in
our
repo
itself,
and
this
controls
all
the
ci
for
this
specific
project
itself.
A
Great.
Now
that
we
have
a
understanding
of
issues
how
to
solve
issues,
how
we
can
group
issues
together,
our
ci,
let's
talk
about
some
of
the
management
and
security
functionality
that
we
bring
the
table
as
well.
So
we
have,
we
give
you
a
lot
of
metadata
as
part
of
gitlab,
and
this
is
the
issues
dashboard.
A
As
you
can
see,
the
number
of
issues
that
are
being
created
is
just
going
up
in
time,
so
you
know
as
a
leader
in
my
organization.
This
indicates
to
me:
hey,
maybe
it's
time
to
start
thinking
about
hiring
new
engineers,
or
does
this
mean
that
the
quality
of
our
products
decreasing
right?
So
these
are
things
that
really
matter
for
me
in
terms
of
making
business
decisions
for
my
organization,
so
we
can
group
these
charts
many
different
ways.
This
is
by
priority.
A
You
can
also
see
that
these
are
bugs
created
by
severity.
You
can
customize
these
charts,
but
it's
just
giving
you
me
insights
so
that
I
can
make
sure
that,
as
a
leader
that
you
know,
I'm
putting
my
chips
into
the
best
possible
place
all
right.
Let's
talk
about
the
security
side
of
things,
so
this
is
a
huge
differentiator
for
git
lab.
A
We
have
security
testing,
that's
built
into
the
ci
process
itself,
so
as
opposed
to
having
to
hire
security
engineers,
you
can
just
have
security
testing,
that's
built
in,
and
one
of
the
things
that's
really
cool
about.
This
is
that
we
scan
your
applications
and
then
a
security
engineer
can
get
all
sorts
of
insights
management
can
come
in
and
I
have
visibility
in
my
application
at
any
given
point
in
time
through
kit
lab
itself.
So
for
this
repo
that
we're
taking
a
look
at,
you
can
see
the
number
of
vulnerabilities
that
we
have.
A
A
I
need
it
all
right.
So
now,
let's
talk
about
dependencies,
so
a
lot
of
times
your
dependencies
go
out
of
date
and
we
scan
all
of
your
dependencies
for
you
as
part
of
the
ci
process.
If
that's
something
that
you
enable-
and
you
can
see-
here's
all
of
the
vulnerabilities
for
some
of
the
dependencies
that
I
have
and
once
again
you
can
see
where
these
dependencies
came
into
my
project
with
the
location
field.
So
the
real
value
of
this
is
that
we
can
prevent
our
developers
from
spending
time
unnecessarily.
A
A
Where's.
The
where
the
security
tests
run
well,
they
run
in
our
ci
itself,
and
so
this
is
a
view
that
I
already
showed.
But
just
to
reiterate,
you
know
our
security
tests
they're
actually
built
into
this
test
phase,
and
this
is
something
that
you
can
configure
for
your
own
enterprise
as
well,
so
we're
testing,
sasdas
and
many
other
different
things
as
well
all
through
our
ci
process,
ultimately
giving
our
developers
real-time
feedback.
A
So
I
know
that
there's
a
lot
of
things
to
talk
about
what
do
you
think
about
some
of
the
things
that
we
shared
today.
A
Great
yeah,
I'm
not
entirely
sure
what
the
answer
is.
As
for
you
know,
kubernetes
configuration
is.
Is
that
something
that's
important
for
your
organization?
A
Great
I'd,
love
to
schedule
some
more
time
with
one
of
our
dedicated
essays,
and
we
can
talk
through
some
of
these
use
cases
that
we're
talking
about
that
you
just
mentioned.
Would
you
be
interested
in
that
you
would
great
okay
yeah,
let's
just
take
it
from
there.
Thanks.