►
From YouTube: The GitLab Journey and CI Use Case
Description
By watching this session, you will understand:
1) The Continuous Integration use case
2) The value of GitLab CI
3) How to create a Command of the Message mantra for CI
Learn more at https://about.gitlab.com/handbook/marketing/product-marketing/usecase-gtm/ci/.
A
Welcome
to
today's
sales
enablement
level,
up
webcast
series
pleased
to
have
Parker,
Ennis
and
William
Chia
from
the
product
marketing
team.
Today,
as
a
follow-up
from
the
session
and
sales
kickoff
about
the
get
lab
customer
journey
and
use
cases,
Khan
Jeremiah
talked
about
Parker
and
William.
We're
going
to
talk
specifically
today
about
the
gitlab
journey
and
the
CI
use
case
so
without
further
ado,
I'm
gonna
post
today's
Google
notes
doc
in
the
slack
I'm
in
the
zoom
channel
here
and
we'll
kick
it
off
to
you,
Parker
and
William.
Thank.
B
You
David
thanks
everybody
for
being
here
today:
I'm
fairly
new
and
joined
middle
of
January
and
I'll,
be
covering
the
CI
area
for
gitlab
and
I'm
really
happy
to
be
here
so
feel
free
to
reach
out.
If
you'd
like
to
coffee
chat,
talk
more
about
this
after
the
session
and
William
is
here
as
well.
I'm
sure
you're
familiar
with
him
who's,
worn
that
every
hat
I
think
you
can
to
the
product
and
marketing
area
here,
so
really
grateful
to
have
him
on
the
line
and
will
lead
on
him
for
things.
B
B
The
CI
use
cases
specifically
go
into
the
overview,
what
we're
working
on
there
and
go
through
the
pager
and
take
the
handbook
first
mentality
in
the
spirit
of
gitlab
and
then
make
sure
that
you
understand
the
resources
available
to
you
and
have
some
time
for
Q&A
in
the
end
and
the
other
big
piece
we'd
like
to
do
a
mantra
workshop,
you
familiar
with
the
command
of
the
message.
So
we'll
do
a
sample
of
that
together
as
a
group,
so
we'll
go
ahead
and
get
started,
and
that
will
let
my
screen
sharing.
C
B
B
So
this
use
case
go
to
marketers
is
gonna,
be
really
really
useful.
This
is
the
overall
page
and
that's
linked
in
the
issue
and
the
note
stock
and
we're
trying
to
match
capabilities
and
in
the
market
to
the
buyers
journey
and
your
selling
emotions.
So
I
won't
go
through
this
in
detail,
but
it
is
a
really
really
good
resource
for
you
to
come
and
check
out
and
we're
actively
working
on
this
and
iterating
in
small
chunks.
This
is
also
a
good
piece
of
this
page
right
here.
B
The
the
Bill
of
Materials
and
you'll
see
these
sections
up
top
CIC,
SCM,
CD,
etc,
and
then
all
of
the
materials
that
are
going
to
eventually
come
from
this
use
case,
work
that
we're
doing
and
so
right
now,
I
believe
it's
SCM,
CI
and
then
simplify
DevOps,
so
that
are
the
first.
We
were
working
on
this
quarter
and
then
more
will
come.
B
So
if
you
want
to
get
to
the
individual
page
which
I'm
about
to
jump
into
for
continuous
integration,
you'd
come
up
here
and
you
click
the
CI
calm
and
that
be
the
easiest
way
to
get
there
and
so
CI.
Alright,
let's
start
with.
Let's
start
with
the
basics,
your
you've
probably
heard
CIC
ICD
DevOps.
You
know
these
are
household
names
now
today,
and
so
it's
unlikely
that
you're
going
to
hear
DevOps
without
hearing
CIN
CD,
together
or
soon
after
and
essentially
what
it
is,
is
exactly
what
it
sounds
like
right.
B
Teams
and
developers
are
collaborating,
checking
in
and
pushing
code
on
a
regular
frequent
basis
and
they
need
a
way
to
store,
modify
and
track
those
changes
to
the
code
base
and
when
they
do
this,
they
want
to
be
able
to
make
small,
incremental
changes
and
know,
what's
gonna
happen
and
run
tests
and
have
built
pipelines
and
have
things
that
go
on
in
the
background
to
make
sure
they're
validating
the
code
they're
checking
in
before
it
gets
to
production.
This
helps
them
to
move
faster.
B
This
helps
them
to
catch
errors
before
they
may
intensify,
is
something
larger,
so
it
really
really
does
streamline
the
workflow
and
make
them
more
efficient,
so
development
teams.
When
we
talk
about
digital
transformations-
and
we
talk
about
trying
to
you
know-
every
company
is
a
software
company
right.
B
This
is
something
that
is
gonna,
be
adopted
fairly
early
on
in
the
process
and
something
that's
gonna,
be
very
important
for
companies,
another
going
digital
transformation
to
start
and
to
start
being
an
or
start
to
get
on
that
journey,
to
deliver
software
better
and
faster
and
then
I
think
another
good
piece
here.
This
is
a
just
a
very
brief
overview.
A
B
C
B
B
Obviously
your
software
developer,
we
call
the
person
with
Sasha
and
I
think
that's
a
very,
very
important
one.
These
are
the
problem
solvers
the
critical
thinkers.
These
are
the
people
that
are
typically
hands-on
with
a
CI
tool
and
writing
code
daily
that
they
want
to
turn
into
lovable
features
writing
valuable
value
to
their
customers.
B
So
very
often
you're
you
encounter
a
software
developer
and
in
the
beginning
of
the
cycle
or
when
you're
trying
to
get
your
foot
in
the
door
to
talk
to
someone
about
CI
and
in
these
personas
in
the
development
world
also
know
this
stuff
very
well.
They've
likely
been
doing
it
for
years.
They've
got
tons
of
experience
in
multiple
programming.
Languages,
they've
probably
had
their
hands
on
a
lot
of
these
other
DevOps
tools
or
even
CI
tools.
B
They've
got
a
deep
understanding
of
the
whole
tool
chain,
their
organization,
and
you
know,
they're
gonna,
look
after
that
suffer
deliver
lunch,
sack
we'll
make
sure
the
tools
are
operating.
The
infrastructure
is
there
and
directly
support
those
development
teams
and
the
leads
and
the
developer
personas
that
talked
about
just
a
second
ago
and
they're.
Also
gonna
have
a
mixture
of
it'll
be
fixed
code,
they're
gonna
be
technical,
but
I
think
if
they
they
want
to
help
build
test
to
release
that
code
into
production,
and
then
buyer
personas
will
be
doing
some
more
work
on
this.
B
So
this
is
certainly
it's
in
an
MVC
form
down
here
for
you
and
something
to
take
into
account
is
that
CI
purchasing
may
not
always
or
I.
Think
in
a
lot
of
cases
won't
always
require
something,
locking
second
element
VP
or
buried
at
the
highest
level
or
more
often
than
not
I
think
you're
gonna
you're
gonna
hit
that
development
manager
level,
maybe
director
level,
which
is
here
and
John
Jeremias
without
some
some
good
new
work
on
the
buyer.
Personas,
so
keep
your
eyes
out
for
for
building
up
some
more
content
around
this.
D
B
In
a
bunch
of
you
know,
ladder
steps
on
the
ladder
you
look
to
to
get
CI
going
at
an
organization,
whether
it's
something
that's
bring
a
new
initiative
or
there's
something
that
is
going
to
be
thrown
more
resources,
that
typically,
you
can
install
the
CI
tool
or
get
a
CI
server
up
and
running
for
free.
Of
course,
the
overhead
or
server
cost
instructor
costs
and
in
you
know,
trickle
up
and
in
that
adoption
is
spread
a
lot
of
times
organically.
B
It's
not
through
an
official
initiative
and
you
may
not
have
to
get
approval
until
there's
a
need
for
that
right
and
it's
been
proved
proven
out
in
a
in
an
organization,
but
that's
a
big
benefit
to
be
able
to
start
something.
You
know
developers
and
these
people
that
are
very,
very
much
some
expertise
in
this
area
to
be
able
to
start
with
something
like
this
and
be
a
champion
and
grow
with
it
and
get
them
on
our
side.
B
D
Thank
you
for
this
information
is
a
very
helpful.
We
are
going
into
a
call
or
demo
tomorrow.
Your
challenge
is
that
the
organization's
already
embrace
CI
they're
doing
CI,
so
this
use
case
is
a
very
applicable
to
them,
but
sometimes
when
we
talk
through
the
use
case,
they
do
understand,
and
some
of
this
reference
point
from
persona
and
customer
are
very
helpful.
D
B
And
that's:
okay,
yeah!
That's
that's
a
great
information
and
thank
you
for
the
feedback.
I
think
that's
one
of
the
tougher
battles
we're
going
to
have
to
fight
just
to
be
frankly,
you
cherry
and
I
think
there's
gonna
have
to
be
a
balance
of
what
can
actually
be
a
rip
and
replace
in
a
situation
like
hey.
We
we're
already
doing
CI.
We
may
have
years
of
code
that
are
that
that's
custom.
B
We
may
be
using
other
tools
like
you
mentioned,
so
how
do
we
get
off
of
those
tools
or
how
do
we
move
and
be
able
to
be
in
a
place
to
adopt
get
live?
You
lead,
lap,
CI
and
I.
Think
it's
going
to
be
a
combined
approaches
that
you
know
we're
gonna
have
to
understand
exactly
what
they're
doing
from
a
technical
standpoint,
I
think
collaborating
with
your
essays
and
collaborating
with
the
product
side
of
the
house
here
to
get
lab,
which
I
know
they're
working
on
something
like
Jenkins
importer
and
some
more
technical
actual.
B
D
C
Yeah
I
would
I
would
just
say
that
the
way
to
think
about
this
page
in
this
collateral
is
where
you
are
at
in
the
sales
cycle.
So
once
you
get
to
a
conversation
where
they're
they're
already
bought
in
to
get
lab
and
they're
really
they're
excited,
and
they
want
to
move
to
it
and
now
they're
having
the
discussion
of
how
do
we
migrate
off
of
our
existing
tooling?
That's
that's
quite
a
bit
later
in
the
sales
cycle,
and
we
can
certainly
do
more
sales
enablement
on
that.
C
The
way
to
think
about
this
page
is
more
in
the
earlier
phase
and
then
discovery
when
you
are
going
into
a
customer
and
discovering
what
is
what
is
the
challenge
that
they
have
is
their
challenge
source
code
management?
Okay,
then
sell
them.
The
source
code
management
use
case
is
their
challenge.
Ci
okay,
then
use
the
CI
for
discovery,
and
this
is
where
understanding
the
capabilities
and
the
personas
and
how
to
how
to
craft
a
mantra
command
of
the
message
mantra
which,
if
we
have
time
we'll,
do
together
here
and
then,
if
you've
done.
C
All
of
that
then
you've
set
up
the
value
of
get
lab
CI
and
then,
when
it
comes
to
conversations
of
the
cost
of
what
it
takes
to
migrate,
it's
easier
to
justify
those
because
you've
set
up
the
value
in
your
discovery
phase,
so
think
of
this
more
as
a
discovery,
phase
asset
and
then
there's
other
collateral
and
capabilities.
You
know,
as
Parker
was
mentioning
our
we're
working
currently
now
on
a
Jenkins
importer,
but
that's
later
in
the
sales
cycle.
D
Yeah
we're
another
early
sales
cycle.
So
that's
why
I
want
to
focus
on
the
use
case.
Sometimes
you
know
the
prospects
like
to
drill
down
there
too
fast.
So
we
need
to
step
back
and
just
like
you
say,
ask
why
and
go
and
look
at
the
value
then
go
from
there.
It's
a
the
challenges
of
it.
You
know
in
the
discovery
call
or
early
on
it
came
to
go
down,
so
we
need
to
figure
approach
to
bring
bring
the
coin
back
to
the
original
question.
Why
yeah.
B
I
love
that
in
for
the
second
time,
I'm
going
to
keep
moving
a
little
bit,
let's
connect
after
this
on
slack
off
line
and
I
would
love
to
dig
into
that
more
with
you.
You
know
see
how
you
know.
Will
that
can
help,
and
you
just
you
know
you
use
each
other's
a
resource
there
to
help
okay
a
little
bit
quicker
through
this,
so
that
we
do
have
time
potentially
for
that
mantra
and
some
more
questions,
but
a
message
house.
B
The
links
are
available
on
this
page
and
then
use
case
capability
to
actually
have
any
more
open
that
I'm
working
on
right
now
for
this,
and
this
would
be
the
practical
application
of
what
is
CI
in
the
market
and
what
are
the
critical
capabilities
then
enable
CI
write?
Something
like
you
know:
how
easy
is
it
to
get
started?
How
we're
building
test
automation
included?
B
You
know,
what's
configuration
management,
look
like
all
these
high-level
concepts
and
very
important
concepts
CI?
What
do
they
mean
as
far
as
the
alot
of
features?
What
do
they
mean
as
far
as
our
competitors
features
and
how
many
these
people
be
doing
it
in
those
we're
going
in
and
talking
to
so,
you
know
8
to
12
of
these
critical
capabilities.
B
Hopefully
they're
useful
through
you
apply
to
value
return
on
investment,
our
features
and
capabilities
and
compare
that
to
the
market
to
get
kind
of
a
holistic
approach,
oldest
understanding
of
what
a
CI
capabilities
be
and
then
top
three
differentiators,
pretty
cool
you're
familiar
with
these
from
command
of
the
message,
which
shows
a
few
here,
the
one
I
think
I'd
like
to
highlight.
For
the
sake
of
time
is
the
third
one.
B
You
know,
rapid
innovation
and
I
think
there's
a
lot
of
strength
and
a
lot
of
power
in
the
fact
that
we're
we're
walking
the
talk
as
far
as
continuous
integration
every
day
it
get
laughs.
You
know
it's
not
just
a
big
part
of
the
single
application
is
not
just
a
big
part
of
get
lab
as
a
product.
It's
also
a
big
part
of
our
culture
and
what
we
do
and
how
we
work
every
day.
B
Competitive
comparison,
obviously
Jenkins
circle
CI
will
be
adding
some
more
they're
proof.
Appointments,
Kym
kinloch
did
a
really
good
job
here
on
throwing
out
some
information
and
quotes
and
real-life
examples
that
are
having
success
with
it
laughing
about
CI.
So
leverage
these
look
out
and
they
don't
take
a
long
time
to
look
at
but
they're,
very
powerful
and
and
they're
good
to
share
with
prospects
and
good
to
share
with
customers
and
they
span
different
types
of
get
lab.
B
You
know
tears
in
plants,
so
there's
a
good
mix
use
cases
their
blogs
pretty
self-explanatory,
but
some
really
big
names
here:
Jaguar
Land,
Rover,
Ticketmaster
goldman
sachs
right.
These
are
household
names,
they
carry
a
lot
of
weight
and
they
show
some
really
really
cool
metrics,
such
as
release
improvement.
B
You
know
cycle
times,
etc.
All
stuff.
That's
going
to
matter
to
those
personas
that
we
were
talking
about
earlier,
like
developers,
DevOps
engineers
and
a
boss
and
injures
two
case.
Studies
blogs,
obviously
some
more
references
as
an
SF
DC
report
here
that
was
added
to
see
where
for
referenceable,
verified
customers
from
the
verify
stage
so
check
that
out
in
salesforce
and
then
some
more
resources
that
we'll
be
building
out
demo,
videos,
integration,
videos,
overviews,
etc.
Some
good
content
here
that
I
think
is
very
useful.
B
C
Yeah
I
think
this
is
a
great
overview
of
the
page.
Definitely
as
an
action
from
this,
we
try
to
design
all
of
these
use
case
pages.
So
that's
a
one-stop
shop
for
you.
So
if
you
read
the
page,
this
is
this
is
kind
of
the
core
info
you
need
to
understand
and
to
work
with
your
customers
at
this
use
case
and
then
also
with
links
out
to
collateral
that
you
can
share
with
your
customers.
So
I
think.
If
you
give
me
the
screen
share
Parker,
we
will
go
over
to
the
doc.
B
C
This
is
the
part
of
the
show
where
you
get
to
participate
so
yeah.
What
we'll
do
is
just
kind
of
base
you
can.
You
can
open
up
the
page
for
reference
this
this
use
case
page
and
let's
go
through
and
just
build
kind
of
what
might
be
a
sample
mantra
and
there's
a
lot
of
ways.
We
can
go
with
this,
so
I'm
kind
of
curious
when,
when
you
all
are
chatting
with
your
customers
and
they
tend
to
have
a
CI
problem
where
they're
looking
at
new
new
CI
solutions.
C
C
C
D
Yeah,
what
are
getting
Anton
up
in
more
detail?
So
typically,
they
will
say
they
will
say
they
don't
have
our
ownership
to
the
CI
and,
and
it's
managed
by
different
groups
and
and
current
solution
is
not
up-to-date.
Just
use
example.
They
said
terminal
plugins
to
maintain
their
own
update
the
whole
pipelines
broken.
They
can
only
release
twice
a
year,
blah
blah
blah.
Oh
those
impact
their
business,
they're,
losing
customers
or
losing
market
share.
Let's.
C
Yeah,
let's
get
there
in
a
moment
and
we'll
work,
that's
really
good
stuff,
so
yeah,
so
their
pipeline
is
broken
their
solutions,
not
up-to-date.
It's
it's
difficult
to
maintain
because
there's
not
one
one
group
that
has
ownership.
So
so
what
are
the
negative
consequences
of
that
I
think
one
might
be
their
pipelines.
Their
pipelines
are
broken
right.
C
D
C
C
And
then
so
what
what
would
be
yeah
and
then
a
negative
consequence
would
be
hey
if
I
have
this,
if
I
have
more
downtime
and
might
miss
my
release
cycles,
then
you
know,
and
if
I
have
a
lot
more
maintenance,
then
I
have
more
operational
overhead.
So
have
all
these
pain
points?
What's
the
ideal
state?
What
do
they
want
for
CI
if
they
could
wave
a
magic
wand
and
magically
tomorrow?
There's
all
their
CI
problems
would
be
solved
and
they
would
have
beautiful,
wonderful
working
CI?
What
would
that
look
like
and.
D
C
And
then
we
could
also
have
an
incorporated
level
of
workflow
to
help
us
manage
and
sure
some
of
our
guardrails
with
a
growing
number
of
developers
on
the
team.
So
this
would
be
like
you
know.
If
they
just
had
the
perfect
CI,
they
would
have,
you
know
easier,
easier.
Onboarding,
you
know
the
and
a
tighter,
tighter
workflow.
C
C
We've
time
to
market
recognized
customer
value,
yes,
I'll.
Let
someone
else
type
that
so
recognized
customer
value
today,
if
they're
builds,
are
going
slow
and
they
can
only
release
every
so
often
they're
not
getting
any
feedback,
but
if
they
could
build
daily
and
they
could
get
that
they
can
get
content
out
quickly
and
then
they
can
get
feedback
on
it
quickly.
They
can
recognize
what
their
customer
value
is.
They.
A
D
C
In
the
30
seconds,
I'll
just
say:
hey
here's
how
we
do
it.
We
have
a
world-class
solution
for
CI
and
then
how
do
we
do
it
better?
It's
part
of
a
single
application
and
then
actually
what
we
might
even
say
is
things
like
you
know.
We
have
scaleable
runners,
you
know-
and
you
know,
but
don't
take
our
word
for
it.
Look
at
Goldman,
Sachs.
C
What's
spelling
they
they're
building,
you
know
a
hundred
times
a
day.
Actually,
I
need
to
go.
Look
at
the
actual
use
case.
I
don't
want
to
misquote
it,
but
you
can
kind
of
see
how
you
could
do
this
mantra
where,
if
we
start
here,
if
I
immediately
get
on
the
phone
and
they're
like
great,
tell
me
the
technical
bits
and
bytes
of
how
I
migrated
you
thought
were
we
want
to
be.
We
want
to.
C
B
Well
put,
and
there
is
an
example
mantra
that
we
that
will
William
and
I
did
yesterday.
It's
LinkedIn
the
issue
and
in
that
doc
as
well,
so
we
expected
and
anticipated
that
Tom
might
be
miss
you
with
these
kind
of
things.
So
please
do
check
that
out.
Obviously,
we're
gonna
continue
getting
ready
on
this
and
make
it
better.
It's
still
in
the
early
stages,
and
you
also
feedback,
is
crucial
to
make
this
as
good
as
it
can
be.
So
you
know,
doors
always
open
for
feedback
and
I
appreciate
it.
Moving
here.