►
From YouTube: GitLab for Deploys, Feature Flags and Error Tracking
Description
A brief introduction into the snowball of effect that comes from using GitLab as your complete DevOps Platform. It's delivered as a single application and can fundamentally impact how your Development, Operations, Security and Testing teams collaborate.
A
Hi
everyone,
my
name,
is
Tim
puffenbarger
and
I
am
a
Solutions
Architect
I
get
lab
and
I
wanted
to
provide
you
a
brief
introduction
to
the
the
snowball
effect
that
comes
when
you
use
get
lab
as
your
complete
devops
platform
and
how
that
can
fundamentally
change
the
way.
Your
development
operations,
security
and
testing
teams
interact
with
one
another.
What
you
have
before
you
right
now
is
the
merger
quest
page.
This
is
a
merged
change
and
you
can
see
the
brief
overview.
A
I
did
my
due
diligence
on
this
change.
You
can
see
that
the
merge
request
was
approved
by
a
handful
of
people.
I
had
the
testing
team
sign
off
on
it.
I
also
did
a
peer
review
from
one
of
my
fellow
developers
and
there
was
a
new
Duvall
nür
ability
that
was
introduced,
and
this
requires
the
the
security
team
to
sign
off
on
this
change
as
well.
A
You
can
see
that
there
are
no
changes
to
code
quality
and
that
security
scanning
detected
no
new
vulnerabilities,
but
there
was
a
new
license,
compliance
which
warranted
that
vulnerability
checked
for
the
security
engineering
team.
All
of
the
team,
including
myself,
we
recorded
our
time
over
here,
it's
attached
to
a
milestone,
but
once
that
sign-off
happened,
I
went
ahead
and
merge
this
into
our
master
branch,
which
is
great
and
subsequently
after
that
merge
into
master
occurred.
A
new
master
branch
pipeline
kicked
off
which
reran
some
oh,
my
and
eventually
deployed
this
back
into
production.
A
Unfortunately,
I
don't
have
access
to
deployed
protection,
or
maybe
fortunately
so
I
engaged
my
operations
team
and
they
deployed
this
into
our
production
level.
Environment
and
I
am
so
excited
to
be
able
to
show
this
change
to
you.
You
can
see
my
beautifully
blue
new
innocuous
button
and
that's
not
supposed
to
happen.
A
Okay,
so
the
users
are
experiencing
a
problem.
Let
me
go
ahead
and
back
hop.
Hop
back
into
gitlab
and
go
to
my
operations
feature
flags
page.
Fortunately,
this
button
was
protected
behind
a
feature
flag
which
gives
me
the
ability
to
quickly
disable
this
within
the
gate,
lab
user
interface.
So
the
users
no
longer
are
seeing
this
this
button,
and
now,
when
I
refresh
the
page,
you
no
longer
see
this
button,
which
is
great
but
I
need
to
do
some
investigative
work.
A
Get
lab
also
has
the
ability
to
receive
all
your
errors
of
the
the
running
application,
and
you
can
see
that
there
was
a
a
division
by
zero
error
that
took
place
41
seconds
ago.
So
let
me
go
ahead
and
click
on
this,
and
you
can
see
exactly
in
the
how
many
events
this
has
how
many
times
this
has
occurred,
the
number
of
users
that
have
been
impacted
as
well
as
exactly
where
in
the
code
this
was
problematic.
A
So
let
me
go
ahead
and
create
an
issue,
and
this
issue
now
can
be
created
by
the
operations
team
and
then
assigned
to
the
development
team
and
the
development
team.
Now
has
you
know
just
written
straight
from
the
code
base
where
this
error
is
occurring,
what
users
are
being
impacted
and
then
they
can
create
a
merge
request
and
get
that
process
started
all
over
again.