►
From YouTube: GitLab DevOps Platform 5 min Demo
Description
GitLab DevOps Platform 5 min Demo
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. Unlike DIY toolchains, a true DevOps platform let's teams iterate faster and innovate together. The goal is to remove complexity and risk providing everything you need to deliver higher quality, more secure software faster, with less risk and lower cost..
Get in touch with Sales: http://bit.ly/2IygR7z
A
A
Let's
take
a
closer
look
on
how
gitlab
helps
team
collaborate
iterate
and
deliver
results
that
serve
customers
and
business
needs.
Erin.
A
vp
of
app
development
notices,
a
downturn
on
subscriber
growth
concerned
with
the
impact
this
could
have
on
the
business
airing
communicates
this
to
the
team
by
uploading,
a
screenshot
of
the
traveling
metric
on
their
business
general
channel
from
this
very
same
channel.
They
can
automatically
trigger
the
creation
of
issues
in
gitlab.
A
In
this
case,
this
third
party
application
is
integrated
using
webhooks
configuration.
So,
as
we
can
see
here
by
sending
a
message
with
this
command
in
the
business
general
channel,
erin
created
an
issue
on
gitlab
cool
from
here.
The
team
can
take
it
and
start
collaborating
and
troubleshooting
this
issue
and
find
out
why
the
subscriber
metric
is
going
down.
Parker
uploads
the
screenshot
to
the
gitlab
issue
and
tags
delany,
the
dev
team
lead
who
will
use
gitlab
metrics
on
their
operations
under
operations.
A
Checking
this
way
some
standard
metrics,
such
as
cpu
memory
network
and
so
on,
everything
seems
fine,
so
delany
goes
back
to
the
issue
and
concludes
that
it's
not
the
infrastructure
fault
delaney
suggests
that
the
drop
in
subscribers
could
be
caused
by
recent
changes
to
the
application
front,
thus
reminding
parker
of
another
issue
about
navigation
problems
in
the
mobile
version
of
the
app
parker
links.
The
mobile
website
release
an
issue
to
the
subscriptions
metrics
one
and
bring
spacely
the
designer
into
the
conversation.
A
Linking
issues
helps
the
team
to
create
associations
between
them
while
troubleshooting
the
problem
presley
tries
the
website
on
different
window
sizes
and,
yes,
the
problem
is
in
the
front.
The
subscribe
button
is
unreachable
on
mobile
presley,
uses
the
issue
boards
and
gives
priority
to
the
mobile
website.
One
all
right
presley
works
on
the
design
using
figma
designers
can
upload
their
work
directly
to
gitlab
issues.
A
A
Discussion
about
the
design
happens
in
the
gitlab
issue
and
when
sasha
is
ready
to
code,
she
creates
a
merge
request
and
by
using
the
web
ide,
she
is
ready
to
start
adding
the
corresponding
lines
of
code
that
will
improve
the
website.
Responsiveness,
all
right.
The
changes
to
the
style
are
added
she's
ready
to
commit.
A
A
This
commit
triggers
our
continuous
integration
pipeline
where
the
code
sasha
just
added,
will
have
to
go
through
different
stages
where
security
scans
code,
quality
test
coverage
and
the
creation
of
a
review
environment
will
need
to
be
successful.
In
order
to
be
able
to
merge
the
changes
into
the
main
branch
delany,
as
the
team
lead
will
review
this
merge
request,
he
can
take
a
look
in
the
changes
that
were
made,
select,
multiple
lines
of
code
to
review
them
if
necessary,
and
all
right
going
back
to
the
main
page
of
the
merch
request.
A
Delany
wants
to
try
the
application
using
review
apps,
which
is
an
ephemeral
environment
that
gets
created
thanks
to
gitlab
kubernetes
integration.
This
environment
allow
us
to
try
the
application
here.
Delaney
can
click
around
and
try
the
responsiveness
of
the
website.
That
is
the
main
concern
and
fix
the
team
is
attempting
to
do.
A
It
looks
like
the
site
responds
well
to
different
window
sizes,
all
right
back
into
the
merch
request
page
here
we
see
that
code
owner's
rule
has
been
configured
requiring
approval
from
delaney.
If
any
changes
to
the
css
have
been
done,
we
can
also
notice
that
not
security
vulnerabilities
were
introduced
by
this
merge
request.
A
Delany
expands
the
view
for
a
full
report
and
everything
seems
compliant
and
okay.
All
right,
it
seems
we
are
ready
to
merge
clicking
on
merge,
will
start
our
production
pipeline
again
a
series
of
automated
steps
that,
when
successful,
will
deploy
our
application
to
production
environment,
we
are
confident
that
everything
will
work
out.
Nevertheless,
we
can
take
advantage
of
gitlab
metrics
and
see
with
our
own
eyes
how
our
new
deployment
is
doing
in
real
world.
A
We
can
configure
custom
monitoring
endpoints
using
gitlab
integration
with
prometheus
monitoring
key
metrics
of
the
app
such
as
requests
to
the
subscribe,
endpoint
monitoring.
This
endpoint
allow
us
to
see
that
the
subscriptions
are
back
on
the
rise.
That's
great,
the
team
has
solved
the
problem
and
the
business
metric
is
back
on
track.