►
From YouTube: Simplify DevOps - Deliver more value with fewer headaches using an end-to-end DevOps platform
Description
Simplify DevOps - Deliver more value with fewer headaches using an end-to-end DevOps platform
DevOps tools shouldn’t create more problems than they solve. As DevOps initiatives mature, brittle toolchains built from point solutions break down, increasing cost, reducing visibility, and creating friction instead of value. As industry analysts have come to agree, the answer to the "toolchain tax" is a DevOps platform.
Learn how a complete DevOps platform deployed as a single application eliminates integration bottlenecks, enables end-to-end transparency, and allows businesses to deliver higher quality, more secure software more efficiently.
Get in touch with Sales: http://bit.ly/2IygR7z
A
All
right,
thank
you
for
that
and
hi
everyone,
and
thank
you
for
joining.
My
name
is
cormac
foster
as
you've
heard
a
couple
of
times
now,
so
I'm
I'm
really
excited
today
to
show
you
a
bit
of
what
makes
git
lab's
single
application
approach
to
delivering
the
devops
platform
special
over
the
last
25
years,
or
so.
I
have
worked
for
a
lot
of
technology
companies
and
that
approach
is
exactly
why
I'm
here
right
now.
A
I
will
try
to
keep
the
slide
presentation
fairly
short,
then
head
into
the
product
itself,
so
you
can
see
how
that
shakes
out
in
the
real
world
and
again,
please
ask
questions
throughout
I'll,
try
to
reserve
some
time
at
the
end
for
it.
If
we
don't
get
to
them,
we
will
follow
back
up
with
you
with
an
answer.
So
let's
get
going
so
first,
let's
talk
about
the
problem
for
those
of
you
who
answered
five
or
more
or
potentially
the
folks
who
answered.
A
I
don't
know
this
will
probably
look
familiar,
but
when
you
see
most
devops
visualizations
in
a
textbook
or
marketing
copy,
it's
usually
represented
as
kind
of
a
left
to
right
diagram
of
stages
or
an
infinity
diagram,
which
we
have
and
you'll
see
that
in
a
second
too,
and
that
is
the
right
way
to
think
about
the
process.
I
think,
but
it's
a
not
necessarily
the
right
way
to
think
about
what
the
tools
actually
look
like.
They
often
look
a
lot
more
like
this.
A
So
in
this
image
you
have
multiple
tools
to
support
all
of
those
things.
We
just
ask
you
about.
You,
know,
project
planning
and
creating
the
code
and
testing
it
ci
and
deployment
and
security
and
monitoring
and
everything
you
need
to
do
to
take
that
idea
and
turn
it
into
software
in
the
hands
of
users.
A
They
all
need
to
function.
That's
the
first
thing:
all
these
things
need
to
be
kept
running
and
they
need
to
communicate.
Ideally,
any
one
of
those
tools
should
be
able
to
communicate
with
any
other
tool
so
that
you
can
have
a
steady
flow
of
information,
but
at
the
very
least,
they
need
to
be
able
to
connect
to
the
tools
that
they
would
sit
next
to
in
that
end-to-end
diagram
and
that
and
that's
something
that
you're
going
to
need
to
potentially
build,
or
at
least
maintain
yourself.
So
that's.
A
The
first
problem
you
encounter
is
just
the
overall
cost
of
this
integration
complexity.
So
you
need
to
not
only
you
know,
design
and
build
and
maintain
the
integrations.
Potentially
you
need
to
manage
upgrades.
You
may
need
to
establish
high
availability
and
disaster
recovery
for
each
one
of
those
with
a
separate
plan.
A
So
the
second
problem
that
comes
up
from
all
of
that
is
time,
even
if
you
have
all
the
money
in
the
world
you're
losing
time
and
it's
time
from
people
who
may
not
do
this
as
part
of
their
core
job.
In
many
cases
they
may
be
developers
or
operations,
folks
who,
who
really
could
be
doing
something
more
productive
and
more
fun
and
something
that
they
were
actually
hired
to
do.
So.
That's
that's!
A
A
A
So
what
that
means
is
that
people
working
in
other
tools
may
not
have
the
full
picture
of
a
story
which
means
that
you
have
emails
going
back
and
forth
and
slack
messages
and
a
bunch
of
stuff
that
should
be
happening
within
your
tools
that
isn't
happening
within
your
tools
and
that's
that's
a
big
problem,
an
even
bigger
problem.
If
you
work
in
a
an
industry
where
compliance-
and
you
know,
regulations
generally-
are
a
big
thing.
A
So
25
years
ago,
when
I
was
fresh-faced
and
new,
I
was
working
at
a
company
called
cnet.com
editorial
company
they're
still
around,
and
we
built
our
own
content
management
and
publishing
and
caching
system.
And
we
did
that
because
at
that
point
everyone
was
just
using
static,
html
files
where
our
design
and
our
presentation
logic
and
our
content
were
in
in
one
document
and
that
was
really
lousy
for
doing
things
like
syndicating
content
to
partners
or
changing
your
design
on
the
fly
or
all
the
things
that
we
wanted
to
do
to
be
competitive.
A
So
we
built
our
own
system
and
it
was
a
competitive
advantage
for
us,
but
we
also
became
an
infrastructure
company
and
that
took
a
lot
of
resources.
So,
a
few
years
later
we
actually
sold
that
system
to
a
software
vendor
that
then
sold
it
as
a
product
and
we
became
we
made
some
money
on
the
sale
which
was
great,
and
then
we
became
customers
of
that
product.
A
So
we
didn't
have
to
maintain
that
anymore
and
we
could
focus
on
our
business
now
these
days,
no
one
is
going
to
build
that
system
themselves
in
the
publishing
industry,
because
they're
just
too
many
good,
solid
platforms
out
there
and
that's.
What's
that's
what
I
think
personally
is
happening
with
the
devops
industry
right
now.
The
platforms
are,
you
know,
are
well
I'll,
just
speak
to
us.
Our
single
app
platform
is
mature
enough
so
that
you
don't
have
to
do
all
of
that.
A
So
these
problems
that
you're
experiencing,
if
you're,
experiencing
those
problems,
if
you're
in
the
five
plus
category
those
are
only
going
to
get
worse
because
we
are
broadening
the
concept
of
what
a
devops
team
is
so
security
and
business
teams
are
critical
to
software
development.
There's
stakeholders
in
this
kind
of
software
value
chain,
but
traditionally
they've
been
left
on
the
outside
they're
things
that
have
happened
before
the
process
to
the
left,
or
in
this
case
above
and
after
the
process.
A
So
integrating
those
folks
into
the
system
is
going
to
be.
Those
are
going
to
be
additional
points
of
integration,
additional
visibility,
problems
you're
going
to
have,
if
it
isn't
already
built
in
there
to
start
with
and
a
lot
of
these
tools,
especially
some
of
the
open
source
ones,
are
legacy's.
You
know
an
easy
word
to
throw
around
and
I
don't
know
I
try
to
avoid
it.
A
A
Gartner
recently
coined
the
term
value
stream
delivery
platform
or
vsdp
to
describe
that
sort
of
system,
something
that
provides
everything
you
need
to
create.
Deliver
visualize
manage
all
of
your
value
in
that
sdlc
and
get
it
out
to
the
people
who
need
it.
So
we
will
send
each
of
you
a
link
to
a
free
copy
of
the
report
after
this
session.
A
And
finally,
I
think
it's
important
to
note
that,
while
we
want
to
give
you
everything,
you
need
to
run
devops
in
one
place,
we
don't
want
to
tell
you
where
that
place
should
be.
If
you
want
to
run
it
on
your
cloud
or
our
cloud
or
on-prem
behind
a
firewall,
you
know
on
a
raspberry
pi,
that's
entirely
up
to
you.
A
We
run
the
same
software
in
every
location,
so
you
get
a
few
more
admin
features
if
you're
running
a
self-managed
instance
versus
kind
of
the
multi-tenant,
hosted
instance
that
we
provide
on
gitlab.com,
but
the
core
software
is
the
same.
So
your
user
experience
is
the
same
you're
not
going
to
have
any
surprises
and
again
you
should
be
able
to
run
your
company
and
your
development.
Your
way,
we
have
customer
stories
on
the
website
at
the
url
at
the
bottom
of
every
page,
but
I'll
just
quickly
call
it
three
outcomes
directly
related
to
that
platform
approach.
A
Without
friction,
they
could
just
light
that
up
glimpse,
got
rid
of
20
different
tools
and
replaced
them
with
gitlab
good
news
for
those
of
you
using
five
or
more
and
then
finally,
goldman
sachs
went
from
a
bi-weekly
build
and
release
cadence
to
merging
and
testing
more
than
1
000
builds
per
day,
and
that
kind
of
velocity
brings
a
bunch
of
other
benefits
which
we'll
talk
about
later.
So
there
are
real
world
benefits
to
this.
Now,
let's
look
at
why,
but
I
encourage
you
to
check
out
that
page.
A
So
like
those
tools
and
that
frankenstack
in
the
beginning,
you
know
gitlab
also
has
dashboards
and
metrics
and
role
specific
interfaces.
You
know
your
security
team
won't
be
using
the
same
interfaces
as
your
product
managers
most
of
the
time,
but
they
will
want
to
see
data
from
those
tools
from
those
other
interfaces
in
other
areas
of
the
business.
A
Unlike
those
other
tools
in
the
the
stack
earlier,
all
of
ours
share
a
common
data
store
and
a
common
ux,
so
everything's
stored
in
the
same
place,
and
it's
all
one
application,
so
you
can
connect
from
anywhere
in
the
app
to
anywhere
else
in
just
a
few
clicks
as
I'll
show
you
and
since
gitlab
is
also
where
you
do
your
work,
it's
where
the
code
lives
and
where
the
code
changes
live.
That
means
that
you
cannot,
just
you
know,
view
the
work
top
down
but
contribute
to
it
so
quickly.
A
A
A
We
have
a
report
that
reaches
across
issues
which
would
normally
be
something
like
a
project
management
system,
and
then
your
code
commits
that
might
be
in
your
source
code
management
system
and
then
your
deploys,
which
could
come
from
a
third
system
that
you
use
for.
You,
know
cd
to
give
you
this
kind
of
detailed
but
well-rounded
stat
about
your
team.
So
we
pull
that
all
together
again
automatically
without
needing
to
build
those
integrations
and
then
here
we're
taking
a
lot
of
that
same
information.
A
A
But
what's
neat
about
this,
is
that
they
receive
that
information
about
vulnerabilities
as
soon
as
those
are
introduced.
As
soon
as
the
code
is
committed,
we're
running
security
tests
and
the
results
of
those
security
tests
are
going
to
the
to
the
folks
in
the
security
department
through
this
dashboard
they're
also
getting
surfaced
as
we'll
see
in
the
demo
back
to
the
the
person
who
introduced
them.
A
So
they
can
learn
from
that
and
make
changes
as
well,
and
then
it's
really
easy,
as
we'll
see
again
in
the
demo
to
trace
these
back
to
the
precise
commit
where
they
were
created.
So
you
don't
have
to
spend
a
week
kind
of
untangling
spaghetti
code
built
on
top
of
other
code,
and
you
can
just
you
know,
quickly,
figure
out
what
the
root
cause
was
undo,
that
and
and
and
get
going
again
with.
You
know
before
it
gets
complicated.
A
And
with
that
enough
slides,
let's
see
how
this
actually
works
in
real
life,
so
I'm
going
to
switch
over
to
gitlab.com
right
now,
as
I
switch
the
share
and
I
will
be
pulling
from
live
projects
that
we
use
to
run
our
business
so
at
gitlab
everyone
uses
the
product,
including
my
organization,
marketing.
So
what
you're
going
to
see
is
a
system
that
really
can
be
used
by
a
cross-functional
team
in
a
production
setting.
So
if
I
can
use
it,
you
can
use
it.
A
Screen
there,
okay,
great,
so
to
show
you
the
value
of
a
single
devops
platform,
I'd
like
to
show
you
a
few
different
experiences
from
different
types
of
users
as
they
work
within
a
single
system.
So
to
start
with,
let's
say
I
am
a
cmo
or
I
manage
a
you
know,
product
development
and
I
want
an
overview
of
how
multiple
projects
are
progressing
toward
quarterly
goals
or
monthly
goals,
or
in
this
case,
what
we're
showing
here.
This
is
the
quarterly
map,
but
I
could
just
as
easily
you
know
break
that
down
by
by
months
or
weeks.
A
A
So
here
you
can
see,
there's
a
use
case
go
to
market
overview
within
that
the
continuous
delivery
use
case
go
to
market.
I
can
see
here
that
that
is
58
complete
now.
That
may
be
all
I
need,
in
which
case
I
can
look
at
it.
I
can
open
this
up
and
say:
58
complete,
looks
like
it's
on
track
and
I
can
go
about
my
business
or,
if
I
want
to
know
more,
I
can
just
click
in
get
more
information.
I
can
look
at
sub
epics.
A
I
can
look
at
the
projects
that
are
sitting
within
this.
I
can
look
at
individual
issues
that
might
be
sitting
within
this
and
again.
That
may
be
all
I
need,
but
let's
say
I
want
to
dive
deeper
into
that.
I
can
then
go
into
one
of
them
in
this
case
I'll
go
into
the
use
case.
Gtm
overview,
epic-
and
this
is
this-
is
a
view
of
the
epic
which
contains
sub
epics
as
well
again,
these
could
be
whatever
you
want.
A
They
could
be
products
or
projects
or
any
initiatives
that
you
would
want
to
create
at
a
high
level.
That
would
be
used
to
organize
other
work.
So
here
I
can
look
and
see
that
here
in
my
vcnc
version,
control
and
collaboration
use
case,
there's
one
issue
that
needs
my
attention,
so
I
can
open
that
up
see.
A
What's
going
on
see
that
that
issue
is
in
the
resource
page
and
it's
in
solution,
demos,
okay,
so
from
there
in
just
a
couple
of
clicks,
I've
gotten
into
a
detailed
say,
project
or
initiative,
and
I
can
see
that
there's
something
going
on
now.
If
I
go
into
the
issue
itself
that
that
had
the
notification,
what
I'm
looking
at
here
is.
A
I
can
see
pretty
quickly
that
there's
a
due
date
of
may
8th,
so
somebody
slipped
a
due
date
or
someone
forgot
to
close
this
out
or
something
happened,
and
I
need
to
know
the
context
behind
that.
So
I
know
whether
this
is
just
something:
that's
an
oversight
where
I
can
remove
that
due
date
or
if
I
you
know,
somebody's
in
trouble.
So
what
I
can
do
here
is
all
of
that
collaboration
that
happened
around
this
is
in
one
document
it's
in
this
issue,
so
I
can
look
down.
A
I
can
see
that
there
was
a
bunch
of
collaboration.
I
can
see
that
ultimately,
this
was
closed
seven
months
ago,
so
it
was
closed
on
time.
It
looks
like
someone
just
forgot
to
to
update
the
due
date,
but
I
can
also
see
that
there
was
a
code
change
or
a
merge
request.
What
we
call
the
merge
request
is
the
code
change
in
the
workspace
around
that
that
is
attached
to
that.
So
that's
a
merge
request
right
here
and
I
can
see
that
that
was
actually
committed.
A
The
pipeline
passed
and
this
code
was
and
this
code
was
pushed
live.
So
I
can
then
click
into
that
merge
request
and
in
one
spot
I
can
see
here
are
all
the
code
changes
that
were
made
to
all
the
files
that
were
changed.
So
if
I
really
wanted
to
dig
in
from
with
that
context,
I
had
and
say:
okay,
what
was
changed.
You
know
here's
the
copy
that
was
there,
here's
what
it
was
changed
to
all
the
way
down.
A
A
So
I
can
then
say:
I
see
that
a
problem
happened
here
during
this,
commit
I'm
going
to
roll
that
back
and
then
again
the
overview
there
is
collaboration
as
well.
So
this
is
collaboration
that
happened
in
the
workspace
itself,
so
that
is
always
going
to
be
tied
back
to
the
issue
that
spawned
it
as
well.
So
with
just
a
couple
of
clicks,
I
can
go
from
this
into
the
actual
code
changes
and
when
I
talk
about
actionability,
that's
that's
what
I
meant
so
there's
visibility.
There's
you
know
having
a
power
bi
dashboard.
A
That
tells
you
whether
things
are
on
track,
but
that's
not
necessarily
connected
to
anything
and
usually
the
output
of
that
is.
I
need
to
send
an
email
to
someone
to
say
what's
the
problem
with
this
or
make
this
happen,
but
what
we
have
here
is
the
ability
to
just
drive
all
the
way
into
the
work.
Should
I
choose
to
go
all
the
way
into
the
work,
and
then
I
can
unblock
things
myself.
I
can
assign
this
to
someone
new.
I
can
make
a
comment.
A
I
can
approve
a
code,
a
code
change
and,
if
you're
in
a
you,
know
a
smaller
company,
perhaps
where
you're
wearing
multiple
hats.
This
is
what
you
do
on
your
you
know
your
daily
job.
You
don't
want
to
be
context.
Switching
you
know,
and
and
looking
at
high
level
reporting
here
and
then
trying
to
you
know,
search
through
files
to
find
out
where
that
change
was
made
and
then
going
into
a
third
system
to
tell
someone
that
they
need
to
go.
Take
a
look
at
this.
A
You
want
to
be
able
to
do
that
all
in
one
place.
So
that's
what
we
mean
when
we
say
actionability.
One
other
thing.
I'd
like
to
point
out
when
you
look
at
an
issue
over
here,
we
have
something
called
labels,
so
labels
are
really
neat.
I'm
a
big
fan
of
labels,
because
they're
super
flexible
and
super
powerful
a
label
is
a
customizable
attribute
that
get
lab
users
can
apply
to
issues,
but
also
to
merge,
requests
that
code
change.
We
just
saw
in
that
workspace
or
to
epics,
so
you
can
define
whatever
classification
you
want.
A
So,
let's
just
say,
we
go
to
marketing
status,
so
you
can
see
here
their
marketing
status,
work
in
progress
plan,
design
review
now
these
are
mutually
exclusive.
So
if
I
mark
this
as
marketing
status
review,
it's
going
to
remove
the
marketing
status
plan
label,
one
of
the
great
things
that
you
can
do
with
something
like
this
is:
you
can
model
a
custom
workflow.
A
So
let's
say
I'm
back
at
cnet
and
we
have
an
editorial
workflow
where
I'm
going
to
create
a
document
and
then
I'm
I'm
going
so
we'll
have
a
writing
stage
or
a
spec
stage,
a
writing
stage,
a
copy
edit,
an
edit
a
copy
edit
and
a
design
stage,
and
then
we'll
have
something
some
kind
of
publishing
stage
final
review,
or
something
like
that.
I
can
create
these
very
simply
as
as
these
scoped
labels
here
and
when
a
document
moves
from
one
stage
to
another.
A
A
So
insights
allows
you
to
track
anything.
You
can
label
in
issues.
So
this
is
a
live
dashboard
that
we
use
in
the
strategic
marketing
department
in
which
product
marketing
sits.
So
here
we're
looking
at
the
volume
of
requests
coming
into
strategic
marketing
by
by
status,
you
know:
are
these
new?
Are
they
in
the
triage
state?
Have
they
already
been
assigned?
Are
they
done?
We
have
a
number
of
things.
We're
tracking
here
again.
Is
this
for
competitive
intelligence?
Is
this
something
that
goes
to
the
tech
marketing
team?
A
Is
this
something
that
goes
to
product
marketing
now
within
product
marketing?
We've
also
created
our
own
reports,
where
we
can
look
at
different
labels.
So
labels,
like
you,
know,
what's
open
and
closed.
Are
these?
Are
these
going
to
be
external?
Facing
are
they
internal
facing
projects?
We're
working
on?
Is
it's
something
else
so
again
anything
you
can
label.
There
are
a
ton
of
different
things.
We
can
look
at
with
labels
here.
Who
are
we
doing
this?
For?
Are
we
doing
it
for
sales,
we're
doing
it
for
public
relations?
A
Whatever
this
means
to
you,
you
can
label,
and
once
you
can
label
it,
you
can
visualize
it,
because
it's
all
one
system
and
again
labels
can
be
applied
not
just
to
issues
but
to
merge,
requests
and
epochs.
So
you
can
search
across
different
kinds
of
work
and
different
categorizations
of
work
and
get
to
where
you
need
to
get
to
so
labels
are
great.
A
I
am
again
a
huge
fan,
but
I
also
wanted
to
show
you
something
called
value
stream
analytics
because
we
don't
want
you
to
have
to
write
something
custom
to
start
tracking,
your
productivity,
so
because
we
are
a
single,
a
single
application
for
everything
you're
doing
and
because
the
work
is
actually
happening
here
in
gitlab
value
stream.
Analytics
just
runs
as
soon
as
you
start
pushing
issues
and
merge
requests
and
and
code
through
the
system.
A
This
is
going
to
start
tracking
that
information,
so
let's
just
assume,
for
instance,
that
I
am
something
like
I'm
a
development
manager
and
I
want
to
be
able
to
identify
blockages
in
the
delivery
of
value
to
to
my
end
users,
and
then
I
want
to
do
something
about
that.
So
I
can
see
here.
You
know
how
many
commits
I'm
doing
over
the
last
30
days,
how
many
deploys
we're
doing
deployment
frequency
total
number
of
deploys
and
how
many
new
issues
are
coming
in.
So
that's
great
at
a
top
level.
A
So
what
we've
done
here
is
created
a
default
set
of
steps
that
we
feel
reflects
a
large
portion
of
the
software
development
life
cycle
for
most
of
our
customers,
and
this
is
what
you
get
out
of
the
box.
So
I
can
see
that
you
know
in
this
case
it's
taking
me
less
than
a
minute
to
create
an
issue
great
that
might
sit
with
someone
in
the
planning
stage
where
an
issue
is
being
worked
on
or
revised
for
a
day,
and
then
it
takes
three
minutes
to
make
some
of
these
code
changes.
A
So
these
code
changes
here
since
we're
dealing
with
the
public
website.
A
lot
of
these
are
probably
just
copy
copy,
edits,
small
changes
that
sort
of
thing
it
goes
through
a
testing
process,
but
you
know
look
at
this
18
hours.
Things
are
sitting
in
review
for
18
hours,
and
some
of
these
are
very
small
code
changes
that
only
took
three
minutes
to
make.
So
you
could
probably
review
these
very
quickly.
So
you
know
overall,
it's
taking
me.
You
know
a
couple
of
days
to
get
these
changes
out
which
doesn't
sound
so
bad.
A
But
if
I
could
assign
a
few
more
people
to
review
code,
then
I
could
potentially
start
delivering
that
you
know
four
or
five
or
six
times
as
fast,
because
at
least
after
the
issue
is
live
and
people
start
coding,
because
the
vast
majority
of
my
time
is
being
spent
there.
Now
since
we're
connected
again,
I
can
look
at
something
so
this,
for
instance,
this
has
been
in
there
for
four
days,
so
one
of
the
contributing
one
of
the
contributing
merge
requests,
I
can
jump
in
there.
I
can
look
around.
A
I
can
see
what
the
changes
were.
I
can
comment
on
these.
You
know,
so
I
could
for
instance,
say
you
know.
Why
are
we
doing
this
and
I
could
you
know,
make
a
suggestion
instead,
where
I
suggest
something
else,
and
then
I
could
start
a
review
from
that,
and
someone
could
accept
that
or
reject
that,
or
I
could
push
it
along
or
do
whatever
it
is.
A
I
need
to
do
and
all
of
that
again
from
what
would
otherwise
be
an
analysis,
only
tool
and
another,
and
you
know
that
required
in
in
integration,
underneath
it
to
actually
get
that
information
into
one
place.
So
not
only
can
I
see
it,
but
I
can
do
something
with
it
and
then
finally
I'll
skip
to
a
project
that
has
less
information,
but
I
have
I
have
greater
permissions
on
this
particular
one.
A
If
this
doesn't
work
for
you,
you
can
hide
the
stage
you
can
just
make
it
disappear.
I
won't
do
that
now,
because
other
people
are
still
using
this
project,
but
I
could
I
could
get
rid
of
any
of
these
that
I
don't
like
or
that
don't
match
what
I'm
doing.
I
can
also
add
a
stage,
so
I
could
call
this.
Let's
say
from
issue
created.
A
To
issue
label
added-
and
let's
say
I
wanted
to
call
this
category
categorization
fine,
you
know
characterization,
and
I
could
add
that
as
a
stage,
if
it
really
mattered
to
me,
though,
how
long
does
an
issue
sit
in
a
queue
before
someone
says?
Oh
that's
what
this
is,
they
do
their
triage
and
they
assign
a
label
to
it
and
that
would
show
up
there
and
I
could
order
that
stage.
A
However,
I
wanted
so
while
we
do
want
to
give
you
tools
out
of
the
box,
we
don't
want
to
constrain
you
to
using
those
tools
if
they
aren't
going
to
fit
for
what
you
do.
The
same
way
that
we
want
to
give
you
a
devops
platform,
but
we
don't
want
to
tell
you
what
you
know
where
you
want
to
run
that
because
it's
your
business,
it's
not
ours.
So
we'll
give
you
a
place
to
get
started,
but
we
want
you
to
be
able
to
build
on
that,
and
then
we
were
talking
about.
A
Mrs
earlier
one
last
thing
I
want
to
show
you
the
emerge
request
again
your
changes,
your
pipelines
that
have
run
the
different
commits
and
then
any
collaboration
that
happens
there.
If
I
say
you
know,
this
is
a
great
idea.
It's
a
bad
idea.
I'm
going
to
upvote
this
or
down
vote
this.
I
can
do
all
of
that
sort
of
stuff
and
again
I
can
label
it
just
like
I
could
with
an
issue,
but
what's
what's?
A
I
think
the
best
part
of
this
to
me
is
that
we
showed
you
the
interface
that
might
be
the
kind
of
go-to
interface
for
someone
who's
a
product
manager
of
cmo.
This
is
probably
the
go-to
interface
in
most
cases,
for
a
developer,
because
developers
are
committing
code
all
day
and
they're
interacting
they're,
either
reviewing
other
people's
code,
as
we
just
saw
or
other
folks
are
reviewing
their
code
and
they
need
to
collaborate
that
explain
what
they
did
accept.
Some
changes
make
some
new
changes.
A
You
know
static
application
scanning
where
we're
looking
for
standard
vulnerabilities
in
the
code,
dynamic
application
stan
scanning,
where
we
will
actually
automatically
create
what
we
call
a
review
app
where
we
we
set
up
a
we
set
up
a
running
instance
of
your
application,
so
that
we
can
then
test
from
the
outside
against
that
and
all
of
those
results.
So
all
the
results
of
that,
so
the
scans
run
every
time
you
commit
code
and
all
of
those
results,
wind
back
in
the
same
system
in
the
interface
that
you're
already
using.
A
A
A
All
these
things
that
normally
would
take
forever
to
unpack,
because
they're
going
to
get
pushed
along
and
people
are
going
to
build
on
top
of
that
code
until
security
finally
looks
at
the
output
and
says,
wait,
there's
a
problem,
and
then
that
could
take
anywhere
from
hours
to
weeks
to
figure
out
and
you
might
have
to
undo
a
whole
lot
of
work,
one
fi,
and
so
I
as
a
developer,
I
can
make
this
fix
right
now
before
it
goes.
Any
farther
makes
me
a
better
developer.
A
I
learn
so
I
won't
do
that
again,
but
it
also
saves
all
that
time
and
money
and
then,
finally,
if
you're
audited,
this
is
wonderful.
I
don't
know
how
many
of
you
have
been
audited
before,
but
I've
worked
at
companies
that
have
been
audited
and
it's
a
terrible
experience
for
everyone,
including
the
auditors.
You
know
the
auditors
show
up
spend
two
weeks
trying
to
figure
out
what
you
do.
A
The
discussion
that
created
the
merger
that
ultimately
led
to
the
merge
request
you
can
see
every
code
commit,
you
can
see
the
impact
of
every
one
of
those
you
can
see
all
the
vulnerabilities
that
were
exposed.
You
can
see
how
they
were
fixed
and
if
they
weren't
fixed,
you
can
see
why
and
you
can
see
who
signed
off
on
it
and
what
that
means,
and
if
I'm
an
auditor
this
just
made
my
day
and
I
can
move
on
to
do
something
else
very
quickly
and
everybody
wins
so
again.
A
These
are
just
examples
of
how
visibility
and
actionability
really
work
well,
with
a
single
app
devops
platform,
there's
a
ton
more
that
we
can
do.
There
are
some
great
demos
we
have
out
there
on
things
called
auto
devops,
where
you
can
spin
up
your
entire
devops
process
just
kind
of
out
of
the
box.
It's
essentially
push
button,
devops,
there's
a
lot
more.
We
could
talk
about
and
we'd
be
happy
to,
but
now
I
will
stop
the
share
and
be
happy
to
take
any
questions.
B
B
A
So,
yes,
absolutely
so
thank
you
for
asking
that
actually,
because
we
do
have
a
a
platform
deployed
as
a
single
app,
but
this
is
not
one
of
those.
I
won't
name
companies,
but
back
in
the
90s
there
were
several
companies
that
would
sell
kind
of
platforms
as
lifestyles
where
you
would
have
to
adopt
everything,
and
then
they
would.
You
know
you
buy
the
software
for
half
a
million
dollars
and
they'd
sell
you
a
million
dollars
of
teaching
you
how
to
turn
it
on
and
you'd
have
to
rip
and
replace
everything.
A
A
If
there's
a
long-term
coexistence
kind
of
thing,
we
we
actually
in
the
last
few
months,
we've
come
out
with
several
new
integrations
with
jira,
and
we
want
our
users
to
be
happy
to
be
able
to
view
gitlab
issues,
for
instance
inside
of
jira
and
the
results
of
those
security
scans
inside
of
jira
and
the
kinds
of
things
that
would
otherwise
take
again
a
lot
of
integration
effort
on
your
part,
and
then
we
have
some
folks
who
say
that
you
know
whatever
whatever
tool.
That
is
is
something
that
you
know.
A
I
I
like
the
value
of
this
this
platform,
but
you
know
for
the
foreseeable
future
or
for
these
projects.
I
don't
want
to
to
move
off
of
that.
Yet
and
and
that's
something
as
well.
We
see
a
lot
of
those
kind
of
hybrid
environments
where
new
projects
might
be
entirely
on
gitlab
and
others
might
have.
You
know
a
different
kind
of
architecture
behind
them,
and
we
can
absolutely
do
that.
B
Awesome
I'm
going
to
just
keep
moving
along
and
if
anyone
else
has
questions,
please
feel
free
to
go
ahead
and
continue
to
add
those
to
q
a
and
we
will
get
to
as
many
of
them
as
we
can
next
question,
we
are
trying
to
initialize
our
first
repo.
Can
you
offer
some
recommendations
on
how
to
handle
secrets
for
kubernetes.
A
I
am
I
so
yes,
I
am
not
the
right
person
to
talk
about
secrets
management.
We
have
a
whole
ops
and
get
ops
team
that
that
does
that,
but
we
can
follow
up
with
the
the
right
person
for
that
there's.
There's
a
fellow
on
the
marketing
team
named
william
chia,
who,
who
does
a
lot
with
that?
But
we
have.
We
have
a
number
of
folks
from
our
solutions:
architects,
to
to
product
marketing
to
the
actual
product
managers
themselves.
You
can
get
better
answers
than
I
can.
B
Awesome
appreciate
that
answer,
and
I
have
made
a
note
for
the
individual
that
asked
that
question
and
we
will
get
an
answer
to
you
and
direct
you
to
william
next
question.
Do
you
have
the
chance
to
view
a
side-by-side
view
of
the
changes
instead
of
interweaved?
Can
you
comment
on
a
peer
review
in
line
with
the
code
to
ask
questions.
A
Yes
and
yes,
so
we
actually
offer
as
well
a
web
ide
that
you
know
people
the
developers,
love
their
ides
and
their
editors
and
and
are
very
wedded
to
them.
But
sometimes
you
just
want
something
that
you
know
will
always
be
there
and
will
run,
and
so
our
web
ide
is
great,
particularly
if
you're
making
you
know
some
people
will
spend
their
whole
day
in
there.
A
A
B
A
So,
yes
again,
there
are
other
folks
who
probably
have
a
better
answer
to
that,
but
we
do
have
a
professional
services
arm.
We
do
not
want
to
be.
We
are
not
a
services
company
in
the
way
that
some
other
folks
are
where
you
know
the
product
exists
to
sell
you
the
services,
but
we
do
have
professional
services
to
help
with
things
we
also
have.
A
You
know:
customer
success,
managers
and
solutions,
architects,
who
can
show
you
those
sorts
of
things,
and
we
have
a
number
of
partners
at
various
levels
who
do
various
who
who
build
on
top
of
gitlab
in
different
ways.
So
there
are
probably
a
number
of
ways
to
answer
that
question
and
we
can
put
you
in
touch
with
someone
who
can
answer
that
more
accurately
in
terms
of
what
makes
most
sense
for
your
situation.
A
B
B
I've
actually
sent
the
link
to
that
recording
in
the
slide
deck
over
for
that
question,
so
because
we're
kind
of
running
up
against
time.
I'd
like
to
get
to
the
last
two
questions
here
before
we
close
next
question:
is
this
a
hosted
solution,
or
is
it
only
on
cloud
for
government
work?
There
are
certain
programs.
We
are
not
allowed
to
use
cloud
for
anything.
It
has
to
be
hosted
on
site.
Do
you
have
options.
A
Absolutely
you
have
options
and
we
have
a
number
of
government
clients.
You
can
run
this
in
just
about
any
cloud,
so
you
can
run
in
just
about
any
cloud
and
again
you
can
run
it
in
our
cloud
as
well.
For
you,
it
sounds
like
that
would
not
be
an
option,
but
we
have,
I
believe,
hundreds
of
thousands
of
self-managed
instances
running
right
now,
so
you
can
absolutely
run
this
on-prem.
A
Oh,
that
is
a
you
know
what
I
so
value
stream
analytics
exists
at
all
levels
of
the
product
and,
to
be
honest
I
will.
I
will
confirm
that
I
will
confirm
that
right
right
after
this
and
get
right
back
to
you
very,
very
good
question.
I
I
but
I
don't
want
to-
I
think
I
know
the
answer,
but
I
don't
want
to
be
wrong,
so
there
may
have
been
a
move
lately,
so
I
will
check
that.
B
That
is
totally
fair,
awesome.
Well,
thank
you.
Everyone
for
joining
today.
If
there
was
a
question
that
cormac
was
not
able
to
get
to,
I
have
taken
notes
here
and
we
will
reach
out
directly
to
you
with
specific
answers
for
those.
So
we
really
appreciate
the
questions
we
appreciate
everyone
being
here
today,
just
a
reminder.
This
was
recorded
and
this
will
go
out
to
everyone
on
today's
call
in
the
next
few
days.