►
From YouTube: CI/CD Seeing is Believing Webcast
Description
In this webinar Parker Ennis - Senior Marketing Product Manager at GitLab - provides an overview of the benefits of built-in CI/CD as a part of a complete DevOps platform explaining how GitLab stands out from other solutions.
A
A
B
As
she
said,
my
name
is
parker,
we'll
get
right
into
it
here
about
40-ish
minutes
of
content
and
then
time
for
q
a
she
mentioned,
and
I'm
really
really
excited
that
you're
here
and
now
that
you
took
some
time
out
of
your
day
to
to
come
and
join
this
webinar.
So
why
seeing
is
believable.
This
will
be
a
mixture
of
walking
through
some
key
features
and
some
capabilities,
a
mix
of
technical
and
solution-based
content
to
help
you
think
about.
B
Cic
did
ci
cd
different,
we'll
have
limited
time,
of
course,
so
I'll
keep
it
high
level,
but
we
will
be
walking
through
some
things.
I'll
show
you
some
screenshots
and
tell
you
as
well
to
show
you
how
we
do
it
at
gitlab
and,
more
importantly,
on
how
we're
different
and
why
we're
different,
so
we'll
get
right
into
it
near
the
agenda.
B
B
B
The
most
important
part
is
in
the
bottom
right,
my
co-workers,
izzy
and
leo
wanted
to
say
hi.
So
I
had
to
put
them
in
here
to
show
you
who
they
are,
but
I've
been
working
lab
since
january,
and
I
spent
the
last
four
to
five
years
before
that
working
on
jenkins
and
it
was
a
cloud
b.
So
ci
and
devops
is
a
passion.
It's
close
to
my
heart
and
I
love
to
connect.
B
I
love
to
expand
my
network,
so
please
do
feel
free
to
reach
out
and
connect
further
on
linkedin
or
any
other
social
you
can
see
in
the
bottom
left-hand
corner.
There
is
a
link
that
says
my
user
window
and
just
a
quick
note,
any
of
the
orange
links
that
you
see
throughout
the
presentation
on
these
slides
when
we
share
them
at
the
end
you'll
be
able
to
click
those
links
and
go
and
get
more
information
about
the
content
that
is
on
that
specific
slide,
so
feel
free
to
click
that
link.
B
So
let's
get
right
to
it,
you
may
have
heard
of
something
called
the
tool
chain
tax
and,
if
you
haven't
this
slide,
may
look
familiar
to
you
because
of
what
you're
doing
today,
the
organization
or
what
you've
done
in
the
past
right
I'd
be
willing
to
bet.
This
is
something
that
that
that
you
recognize
and
over
the
course
of
your
career,
the
bottom
line
is
software.
Development
is
not
easy.
There's
a
lot
of
moving
parts
it
never
has
been,
and
it's
shaping
quicker
than
it
ever
has
before.
B
You've
probably
heard
that
too,
you
gotta
have
resources
designed
you've,
got
resources
to
build
and
maintain
integrations
gotta
manage
your
upgrades.
Now
you
may
even
need
to
get
a
disaster
recovery
set
up
and
implement
high
availability.
These
are
all
not
easy,
and,
and
these
things
can
be
brittle
and
fail
when
you've
gotta,
shut
them
up
and
configure
them
and
maintain
them.
B
Now
you
may
have
silo
teams
right
and
then,
when
you've
got
these
complex,
spider,
webs
and
tools,
the
chill
chain
only
serves
to
reinforce
these
silos
that
we're
trying
to
break
down
in
the
name
of
devops
right.
That's
it's
something.
We
talk
about
all
the
time,
bridging
the
gap
between
dev
and
knox,
breaking
down
these
barriers
now,
instead,
instead
of
teams
being
able
to
collaborate
together
their
different
tools
with
them
in
these
different
workspaces,
this
is
a
problem.
It's
it's
a
it's
a
problem
in
our
space.
B
I
also
like
to
say,
with
a
little
bit
of
perception:
is
reality
right?
I
think
this
holds
true
in
software
as
well.
You
can
look
at
these
challenges
on
the
left
and
for
exactly
what
they
are,
or
you
can
turn
them
into
opportunities
like
on
the
right
and
and
finally,
as
we
see,
we
help
organizations
do
this
every
single
day.
At
the
end
of
the
day,
the
goal
is
to
produce
positive
business
outcomes.
It's
not
going
to
talk
about
now.
B
Why
get
left
and
give
you
an
advantage,
and
but
first
I
want
to
talk
about
who
we
are
and
set
the
stage
about
get
lab
as
a
company,
and
it's
something
I
like
to
call
the
gitlab
advantage
we'll
be
covering
a
few
things
in
the
in
a
couple
slides
later,
but
let's
set
the
stage
with
with
a
little
company
information
right
now
we're
most
widely
known
for
our
complete
devops
platform
delivered
as
a
single
application.
But
what
does
that
mean
right
now?
B
It
means
you
get
everything
you
need
to
deliver
more
value
to
commercial.
Your
customers,
faster
with
gitlab
in
one
place
right
from
end
to
end
from
idea
to
production
from
the
very
inception
of
a
problem
identified
that
needs
solving.
However,
you
want
to
speak
to
it
or
slice
it
and
get
labs
getting
equipped
with
what
you
need
to
be
successful
in
a
single
application.
B
But
these
are
things
that
that
we
look
to
solve
for
you
and
help
you
solve
and
they're
crucial,
the
crucial
parts
of
devops,
but
the
bottom
line.
Gitlab,
we
are
open,
we
are
transparent
and
we
are
a
collaborative
community
building
software
together
and
it's
really
something
special
and
and
that's
what
we
pride
ourselves
on.
B
I
also
want
to
talk
about
the
get
lab
flow.
It's
something
that
we're
very
opinionated
about.
I
mean
I
wanna.
I
wanna
set
the
stage
and
walk
through
this
before
we
get
into
the
actual
meat
of
the
content,
because
I
think
it
will
be
a
helpful
contextuality
as
we
go
through
and
so
I'll
be
walking
you
through
these
steps
in
a
second,
so
you
can
just
kind
of
sit
back
and
relax
and
enjoy
the
flow
diagram
right
and
I'll
be
calling
out
some
points
here
as
we
go
along.
That
are
important.
B
So
first
thing
you
see
here
is
creating
an
issue
we'll
be
getting
into
what
a
gitlab
issue
is,
but
I'm
thinking
of
it
as
an
invitation
to
a
conversation
right
next
thing
we
do.
Is
we
create
a
mr,
and
this
is
where
we
start
the
community.
We
start
to
collaborate,
the
work's
actually
being
done
right
in
a
developer
flow,
and
this
is
where
the
development
makes
them
make
their
first
changes
in
any
one
right
from
there
we
start
leveraging
automation.
B
We
see,
I
might
communicate
running
automated
tests,
automated
bills,
we're
starting
an
embed
security
right.
We've
got
these
security
scans.
You
may
even
have
a
saving
instance
called
a
review
app
just
pop
up
ready
to
go
every
time.
You
make
a
commit
or
everybody
every
time
you
push
from
there,
you
may
have
a
peer
review.
B
You
may
get
some
approval
case
or
prove
some
changes
and
then,
when
you're
ready,
you'll
close
out
the
issue
you'll
make
sure
that
the
infrastructure
is
ready
to
go
in
your
cv,
file
right
right,
we'll
automate
the
release
side
of
the
deployments,
and
then
you
can
start
monitoring
around.
So
this
really
does
paint
a
good
picture
of
the
full
spectrum
within
the
end
and
the
cool
part
is
this
last
piece
boom?
We
do
it
all
again.
Continuous
everything
continues
to
keep
that
loop.
This
is
something
that's
very
unique.
B
The
first
section
we're
going
to
talk
about
is
collaboration.
I
mean
how
you
can
improve
it,
and
the
focus
here
is
going
to
be
on
git
lab
issues
and
and
what
we
call
merge
requests
collaboration
is
key
to
developing
great
applications,
and
I
think
it's
often
underestimated
in
our
industry
in
terms
of
value.
A
lot
of
times,
you've
got
non-programmers
that
are
thinking.
Programs
are
constantly
tapping
away
the
keyboards
on
code
right
like
the
like
the
cat
jet
just,
but
in
fact
you
know,
software
development
is
more
like
a
discussion.
B
I
mean
it's
more
collaborative
in
nature.
There
is
a
solitary
experience
and
that
being
said
for
a
lot
of
developers,
I
think
there's
important
aspects
of
collaboration
that
are
missing
the
opportunity
to
engage
with
other
stakeholders
is
one
of
them
right:
your
customers,
your
co-workers,
regardless
of
lines
of
business
or
role
or
groups,
the
entire
end-to-end
development
process.
You
know
they
need
to
be
able
to
engage,
and
regardless
of
how
agile
your
team
is,
you
might
still
be
working
without
the
needed
context
to
be
successful.
B
You
might
be
building
the
wrong
things
in
the
wrong
order,
and
it's
good
to
be
thinking
about
that.
So,
let's
do
it
now
we're
going
to
get
into
how
we
do
it
with
issues
and
words
requests.
But
first,
let's
talk
about
issues,
we're
going
to
be
using
a
common
example
throughout
the
presentation
here
today
and
continue
to
travel
now
so
that
the
theme
is
going
to
be
around
and
for
the
second
continuity,
that's
what
we're
going
to
be
using
as
we
go
along.
B
So
this
modify
home
page
that
you
see
will
be
familiar
as
we
continue
with
the
content,
and
the
objective
is
is
to
do
exactly
what
the
description
says
here
on
the
screen.
Right
modify
our
home
page
to
add
a
little
basic
sign
and
sign
up
form-
and
I
know
it's
not
quite
very
2020
to
have
travel
is
our
theme
because
travel
really
isn't
a
thing,
but
at
least
we
get
to
live
vicariously
through
this
for
for
about
30
minutes
or
so
and
so
to
need
to
travel
with
our
travel
company.
B
So
the
first
thing
we
do
is
we
open
a
gitlab
issue?
You
know,
thinking
about
software,
don't
know
is
a
conversation
like
I
mentioned
before.
An
issue
is
that
invitation
to
a
conversation
and
the
benefits
of
collaboration
start
at
the
point
of
making
the
gitlab
issue
right
by
making
this
issue
you're
starting
to
get
your
ideas
out
there.
This
allows
you
to
start
collaborating
in
other
stakeholders
and
start
to
get
engaged
and
have
a
say
early
in
the
process.
B
B
You
also
notice
that
there's
a
design
section
with
the
sample
illustration
design
management
is
something
that's
weaved
into
this
workflow
moved
in
as
a
capability
with
our
issues,
and
so
we've
got
this
invitation,
and
from
here
we
can
start
thinking
about
actually
doing
the
work,
and
we
do
this
in
what's
called
a
merge
request,
and
so,
let's,
let's
move
on
to
what
an
mr
or
emerge
request
is,
and
so
now
that
we
have
this
invitation
to
our
conversation
issue.
We
get
to
create
this
merge
request
directly
in
gitlab.
B
B
Why
create
an
empty
arm,
mr
or
why
should
I
collaborate
in
new
york
before
the
work
starts
when
I
can
collaborate
in
an
issue
and
those
are
great
questions
and
the
answer
is
because
merge
requests
provide
value
in
a
different
way
when
you're
collaborating
and
communicating
as
close
to
the
code
as
possible.
Your
communication
is
more
effective
and
collaboration
is
more
efficient.
B
You
can
make
suggestions,
comments,
etc
in
real
time,
and
it's
essentially
like
hey.
We
started
this
conversation
now,
let's
create
a
shared
workspace
right
and
so,
for
instance,
in
our
example,
we
can
start
collaborating
with
the
ux
team
and
the
product
manager,
the
product
manager
and
talk
about.
How
are
we
going
to
design
and
implement
this
basic
sign-in
performance
as
we
move
along?
B
B
B
What
you
started
with
you
know
with
the
commit
in
the
very
first
minute,
you've
shared
that
work
publicly,
and
so,
if
you
would
like
to
to
use
the
traditional
club,
you
can
certainly
retroactively
associate
mars
with
that
with
an
issue,
and
you
can
point
at
that
discussion
towards
the
relevant
work.
That's
already
happening,
but
we're
very
opinionated
about
the
gitlab
flow,
and
I
wanted
to
make
sure
I
highlighted
I'm
just
starting
the
collaboration
earlier
and
then
starting
anymore.
B
You
know,
while
the
work
struck
me
before
the
work
has
actually
been
done.
It
is
really
really
cool
and
then
just
a
few
other
things
about
this
screenshot
here.
Obviously,
you've
got
your
nav
bars
on
the
left
and
the
right
you
can
assign
who
you
like
in
the
top
right
hand
corner
you
can
plan.
You
got
these
capabilities
over
here
time.
B
B
B
You
know
there's
going
to
be
several
times
throughout
this
presentation,
where
I
kind
of
heart
them
a
few
things,
and
I
want
to
make
sure
I
I
drill
them,
but
this
merge
request
is
directly
tied
to
your
issue
and
it
can
also
close
out
your
issue
once
this
merge
once
it's
merged
and
honestly.
This
is
something
that's
been
extremely
valuable
for
me
in
my
day
to
day
and
something
I
didn't
even
realize
I
needed
until
I
had
it.
B
So
there's
a
lot
of
really
cool
stuff
like
this
and
issues,
but
the
bottom
line
is
you
know
these
capabilities
make
it
easier
to
manage
a
discussion.
They
make
it
easier
to
keep
the
flow
of
the
conversation
moving.
You
can
discuss
these
changes
with
team
members.
You
you
know
you're,
not
just
working
with
the
code.
You
saw,
you
can
add
other
artifacts
like
like
the
design
management
right,
ui,
screenshots,
etc.
You
can
work
on
your
code,
your
feature
branch.
Your
way
you
can
iterate
on
your
work
in
small
chunks,.
B
And
this
is
just
gonna,
be
a
quick
slide,
but
also
wanted
to
quickly
show
how
we
do
it.
As
far
as
a
web
ide-
and
you
know,
most
developers
have
really
strong
feelings
about
ids
and
encoders
right
and
we
work
with
them
all,
but
sometimes
you
just
want
something
lightweight
simple:
that's
always
there
and
just
works.
We
have
that
too,
and
so,
if
you're
used
to
seeing
things
like
this
and
more
comfortable
with
this
environment,
you
have
that
option.
B
I
just
wanted
to
point
out
here
that
you
have
multiple
ways
to
commit
review
changes
and
speaking
of
reviews
code
changes
are
really
really
easy
in
good
lab.
You
can
come,
you
can
leave
comments
on
each
line.
We
leave
multiple
comments.
Per
line.
You've
got
code
suggestions
that
can
be
applied
in
batches.
These
are
all
really
really
useful
features
all
instead
of
emailing
someone
with
like
12
changes.
C
B
It
allows
authors
to
easily
request
a
review
as
well
as
see
the
status
of
reviews
in
your
merchandise,
so,
like
you,
can
simply
select
one
or
more
users,
assign
them
and
they'll
get
a
notification
and
to
request
or
a
notification
request
to
review
submerged
requests.
This
makes
it
easy
to
find
out
determine
relevant
roles.
B
B
C
B
Cool,
so
this
is
just
a
little
recap
of
that
first
section,
so
we've
got
our
example.
Issue
modify
home
page.
In
our
example,
merge
request,
open
for
modify
home
page
in
draft
form,
and
we've
talked
about
why
they're
valuable,
what's
different
in
these
workflows
and
why
code,
changes
and
reviews
are
easy.
So,
let's
recap
that
value
of
collaborating
and
initiating
work
earlier
in
gitlab.
B
B
B
And
so,
let's
get
to
the
next
section
as
I
like
to
call
automate
everything.
So
now
what
we've
got
these
we've
got?
This
collaboration
started
what
if
there
was
no
need
to
write
your
pipeline
from
scratch
instead
of
starting
from
zero,
we
can
put
you
on
the
road
with
a
car
and
get
put
the
keys
in
your
hand,
and
you
can
drive
it
wherever
you
want.
B
What
is
it
autodevops
is
a
set
of
predefined,
customizable
and
extensible
ci
cd
templates,
and
it's
pretty
unique.
We
put
years
of
experience
in
best
practice
practices
in
gitlab
that
went
into
this,
and
it
still
does
you
know
we're
continuously
putting
that
experience
and
those
best
practices
into
this
feature.
This
capability,
the
areas
highlighted,
are
some
pieces
that
will
be
covered
in
some
faster
today.
B
B
You
see
on
the
left-hand
side
here
the
nav
bar.
We
were
in
the
issue
section
right
above
merge
requests,
and
now
you
can
see
that
we're
under
ci
cd
and
settings-
and
this
is
where
you
configure
auto
devops.
This
is
where
you
start
kicking
off.
The
automation
start
letting
it
do
the
hard
work
for
you
for
our
example
of
this
tanuki
travel
modified
home
page
and
we're
back
in
the
gitlab
ui,
and
all
you
have
to
do-
is
click
one
check
box
here
and
set
your
deployment
strategy.
B
B
Here
in
the
bottom
left-hand
corner,
I
encourage
you
to
check
out
the
docs
on
how
to
devops
to
really
see
all
that
it
can
do
and
all
that
you
can
customize
it
to
do,
because
there's
no
way,
I
could
possibly
cover
that
here,
but
I
did
want
to
introduce
the
concept
start.
Getting
you
think
about
what
auto
devops
can
do,
how
much
manual
work.
Are
you
doing
compared
to
what
you
could
let
the
automation
do
for
you.
B
And
to
continue
with
our
example,
here
is
what
we've
done
with
autodevops
for
the
tanuki
travel
example,
and
we
have
customized
autodevops
here
a
little
bit
for
our
sample,
ci
cd
pipeline
and
so
we've
saved
our
changes
in
the
previous
screen.
In
this
build
phase
that
you
see
in
the
red
box,
all
the
way
to
the
left
is
kicked
off
and
once
that
finishes
in
the
pipeline,
auto
dev,
auto
devops
takes
over
and
kicks
off
the
rest
of
what
you
see
here
in
the
pipeline
illustration
automatically
from
left
to
right.
B
So
let's
dig
into
a
little
bit
of
what's
happening.
You
see
the
test
section
right
typical
for
for
seeing
a
pipeline
view,
but
we've
got
all
our
automated
test
frame
right
from
code
quality
container
scanning
license
scanning
et
cetera,
and
we've
got
a
couple
customized
jobs
here
as
well.
For
example,
the
deploy
testing
was
added
for
this
purpose
for
the
example,
as
well
as
the
functional
test
and
and
those
wouldn't
necessarily
be
in
the
vanilla
or
or
the
predefined
basic
ci
cd
template
for
auto
devops.
B
B
Today,
right,
you've
got
multiple
interfaces,
multiple
tools,
multiple
places,
that
you
have
to
go
to
retrieve,
find
and
manage
these
kinds
of
things,
and
so
damn
pipeline's
done
now
what
right
we've
configured
it
we've
got
our
pipeline.
It's
running
great,
we're
all
happy
rainbows
and
unicorns,
but
you
can
see
these
results
right.
We're
back
in
the
mr
now
draft
modified
home
page
everything's
connected
you're
in
this
one
single
application
in
one
location,
you're,
not
switching
context.
B
You
don't
have
to
log
into
these
several
applications,
like
I
mentioned,
to
find
what
you
need,
and
you
can
also
see
some
of
the
results
on
this
screen
that
mimic
that
more
detailed
pipeline
view
in
the
last
last
slide
right.
You've
got
everything
from
code
quality
says
no
changes
to
code
quality
great.
We
want
to
know
that
you've
got
a
security
standing.
It's
detected
84
potential
vulnerabilities
great.
B
We
definitely
want
to
know
that
right,
license
compliance,
etc,
accessibility,
scanning
and
notice
that
we
still
have
our
draft
or
our
mr
and
draft
form,
but
these
pipelines
run.
We've
got
our
results.
It's
all
easy
to
find
right
here
in
one
place,
and
that's
really
really
the
value
of
autodevops
really
letting
the
automation
do
the
work
for
you,
and
so
why?
B
Because
you
can
essentially
accomplish
this.
What
you
see
here
in
the
bottom,
with
a
single
commit
right.
You
know,
as
I
said
before,
getting
cicd
set
up,
especially
for
the
first
time
and
running
your
first
job
successfully
is
not
an
easy
thing
to
do,
but
it's
crucial,
and
so
you
know
think
about
it.
What
that
example
would
have
been
like
without
having
auto
devops,
how
long
it
would
have
taken
to
walk
through
set
up
and
do
everything
that
was
in
that
pipeline
view.
B
At
the
end
of
the
day,
we're
we're
replacing
otherwise
manual
work.
You
know
we're
making
it
easy
to
get
started.
We're
breaking
down
some
of
those
barriers,
as
I
mentioned
in
the
beginning
of
the
conversation
to
adoption
and
onboarding
and
and
one
of
the
biggest
part,
is
it's
repeatable
and
it's
customizable
and
there's
a
lot
of
value
in
that
and
to
me
it
makes
it
seem
like
devops
magic.
B
Next
section
we're
going
to
talk
about
is,
is
previewing
changes
seamlessly
and
the
focus
here
is
going
to
be
review
apps.
So,
let's
think
about
our
tanuki
travel
example.
Again,
we've
got
our
first
spring
pipeline.
We've
been
collaborating
excellent
code
changes
have
been
committing.
So
how
do
we
preview
these
changes?
Then?
You
know
when
we're
moving
fast
things
change
fast
and
we
want
to
know
what
state
our
application
is
in
and
and
we
want
to
find
that
information
easily
and
quickly.
B
So
these
images
should
look
familiar
again
right
from
auto
devops.
Let's
say
you
needed
to
make
a
last
minute
change
to
your
app
to
our
application.
After
maybe
a
team
member
or
colleague
committed
some
changes
and
you
wanted
to
make
sure
to
preview
them
and
see
what
changed
before
circulating
this
out
wider
in
the
organization.
B
Here,
you
can
see
how
we've
automatically
created
a
review,
or
instance,
or
review
of
the
application
called
review
out
there
in
the
pipeline
and
then
deployed
that
app
using
kubernetes,
so
we
can
validate
in
real
time
and
obviously
the
bottom
right
is
now
another.
Look
at
that,
mr,
where
I
wanted
to
highlight
hey,
we
can
see
that
the
pipeline
has
been
done
once
it's
completed,
that
that
job
that
deploys
up
is
done,
and
then
we
see
the
button
pop
up
to
actually
click
it
and
some
cool.
B
I
like
to
think
about
review
apps
as
a
staging
environment
for
every
you
know
for
every.
Mr,
I
think
that's
a
really
cool
way
to
look
at
it,
and
so
once
this
python
finishes,
we
can
click
that
button
called
view
app
and
you
can
check
out
these
changes
and
you
can
verify
them
and
see
that
that's
what
we
want
and
for
our
basic
example.
This
is
exactly
what
we
expected.
B
And
so
I
think
reviews
can
really
help
transform
the
way
that
you
work.
You
get
a
staging
advice
from
every
mr,
it's
it's
minimizing
the
guest
work
and
helps
you
work
more
efficiently
without
waiting
on
others
to
review
and
evaluate
where
you're
at
and
where
your
application,
what
state
it's
in.
It's
a
time
saver,
it's
going
to
help
you
utilize
the
power
of
kubernetes
without
that
learning
curve,
because
it's
steep
and
it's
automated,
it's
integrated
into
your
workflow
and
get
completely
fully
integrated
and
a
cool
thing
about
review.
B
Apps
is
it
also
helps
to
make
sure
you
keep
your
applications
secure,
while
they're
running
in
production
with
something
called
dynamic,
application,
security
testing
and
that's
a
great
transition,
because
that's
in
the
security
room
to
our
next
section,
which
will
be
about
embedding
security
into
your
workflow,
something
that
I
really
really
like.
We're
going
to
focus
on
shifting
security
left
also
a
little
bit
right
and
then
we're
going
to
talk
a
little
bit
about
dast,
as
I
mentioned
so.
B
You
probably
recognize
this
diagram
again
similar
to
that
flow
illustration
that
I
showed
in
the
very
beginning
of
the
presentation,
and
so
I
wanted
to
show
this
a
different
way
with
the
abstech
test,
to
express
more
clearly
that
there's
a
key
to
gitlab's
approach.
This
is
scanning
the
code.
At
the
point
of
code
commit
before
the
code.
B
B
And
then
not
going
to
spend
too
much
time
on
this
slide,
but
just
to
reiterate
that
security
scanners
run
on
every
commit
right.
We've
looked
at
these
pipeline
screenshots
a
little
bit
today,
but
these
are
things
that
you
can
also
customize
as
a
part
of
auto
devops
right.
If
you're
going
to
run
these
scanners
on
every
commit
as
part
of
your
ci
to
get
that
early
detection
of
vulnerabilities,
it's
good
to
be
able
to
customize
that
to
your
needs
because
you
may
have
different
requirements.
B
B
B
What
I
want
to
get
across
here
is
that
security
testing
does
not
stop
once
the
code
has
been
shipped.
Das
requires
a
functioning
application
in
order
to
actually
assess
the
app's
behavior
for
any
vulnerabilities.
That
may
you
know,
come
up
or
manifest
while
they
actually
is
that,
while
the
app
is
actually
running
in
production
right,
it's
it's
it's
in
a
production
environment.
B
B
You
can
use
the
outside
best
against
yours
if
you
will
and
when
you
think
about
static
application,
security,
testing
or
sas
it's
kind
of
going
from
the
inside
out
right
or
dashed
or
dynamic
application
security
testing
is
going
from
the
outside
in
and
so-
and
I
can't
reiterate
this
point
enough
that
all
of
this
is
on
the
merge
request
screen
and
in
one
place
and
you're,
not
context
switching,
and
so
this
is
really
useful
for
for
for
you
as
a
developer
or
your
teams
to
fix
these
problems
fast.
You
you
can
see
here.
B
B
And
then
I
also
wanted
to
mention
the
security
dashboard
so
having
one
tool
around
which
you
can
collaborate
and
help
get
kind
of
dev,
sec
and
ops.
All
on
the
same
page
is
awesome.
Once
the
developers
code
is
merged
into
the
main
branch.
This
security
dashboard
can
show
any
unresolved
vulnerabilities
here.
So
this
can
be
seen
at
the
project
level.
The
group
group
of
projects
across
your
entire
instance.
B
B
And
so
just
a
plug
for
for
really
the
wide
breadth
and
depth
of
security
capabilities
that
we
have
here,
but
beyond
dust
you
know,
there's
you
can
get
lab
ultimate
out
of
the
box.
You
know,
we've
got
the
ability
to
enable
all
of
these
scanners
with
one
click
with
auto
devops,
to
bring
it
back
to
another
key
capability
that
we
talked
about,
or
you
can
customize
that
pipeline
to
include
the
thirds
third-party
scanners
in
your
yaml
file
right.
B
You
have
the
freedom
and
the
flexibility
to
do
that
as
well,
and
we
did
just
add
a
mobile
scanning
tool,
which
was
a
cool
contribution
from
one
of
our
from
one
of
our
customers.
So
you
know
every
scan
type
finds
a
little
something
different
right,
and
so
it's
really
really
unique
that
only
you
know.
Gitlab
can
provide
all
of
these
fans
and
deliver
them
to
you,
I'm
as
you're
iterating
as
the
developers
writing
code
with
no
added
licenses
and
no
no
integration,
no
maintenance,
overhead.
B
And
this
is
just
a
recap:
this
is
just
a
recap
of
the
security
advantage
to
wrap
it
up
in
a
nice.
Little
bow
for
the
holiday
season,
right
and
and
from
my
idea
to
production
is
how
we
need
to
think
about
security,
not
just
integrated
security.
We
wanted
to
embed
it
and
I
think
one
of
the
advantages
with
security
get
levels.
It
is
more
effective
and
more
valued
as
a
part
of
this
complete
devops
platform.
B
A
lot
because
of
how
these
features
are
these
capabilities
that
you've
seen
at
a
high
level
today
they're
connected
and
then
also
you
need
to
shift,
left
and
shift
right
right
and
we've
got
to
make
sure
that
we're
testing
for
vulnerabilities
in
production
for
our
running
app
and
also
before
proactively,
and
so
I
like
to
think
of
it
as
weaving
depth.
You
know
weaving
security
into
your
devops
lifecycle,
right,
making
sure
it's
not
an
afterthought
and
that
you're
thinking
about
this
kind
of
thing
at
the
inception
of
an
idea
or
problem
that
you're
solving.
B
And
then
we
will
close
it
out
here.
Hopefully,
audio
has
been
okay
for
the
latter
part
of
the
presentation.
I
apologize
for
that,
but
don't
take
it
from
me.
Okay,
I'm
really
happy
that
you
spent
some
time
with
me
and-
and
let
me
talk
about
these
things,
because
they're
really
really
cool
and
really
awesome,
but
these
are
customers
that
have
the
same
problems
that
you
may
have.
They
have
the
budget
behind
the
problems
to
solve
that
you
have
and
they
may
have
had
challenges
that
seemed
impossible.
B
B
And
then,
finally,
if
if
you
only
remember
three
things
from
this
presentation,
okay,
I
want
you
to
remember
that
gitlab
can
help
you
increase
collaboration
right
using
mrs
and
gitlab
issues.
I
want
you
to
remember
that
you
can
automate
everything
and
you
can
automate
ci
cd
and
get
started
easier
with
auto
desktops,
and
I
want
you
to
remember
that
you've
got
to
embed
security
into
your
apps.
B
Thank
you.
Thank
you.
Thank
you
for
listening
again,
sorry
for
the
audio
issues
in
the
beginning.
Hopefully
the
the
second
half
was
a
little
bit
better,
but
but
here
you
know,
start
a
trial
right.
The
part
of
the
reason
that
seeing
is
believing
is
because
we
truly
believe
that
if
you
can
get
your
hands
on
this
and
and
see
what
gitlab
can
do
for
you,
that
you
will
be
a
believer
and
so
start
a
trial
see
for
yourself.
B
We've
got
a
really
good
ebook
here,
single
on
on
the
benefits
of
ci
cd
built
in
as
a
part
of
a
single
application,
and
then,
if
you're,
more
technical
or,
if
you're,
really
curious
about
some
of
these
capabilities
that
are
beyond
the
high
level
stuff
that
we
talked
about
today,
check
out
gitlab
for
complexity.
I
see
a
youtube
deep
dive
by
some
of
my
colleagues
and
we
have
plenty
of
really
really
awesome
resources
and,
of
course,
come
back
and
check
out
this
content
and
click
on
the
links.
B
A
B
Firstly,
we
handle
issues
within
our
own
software,
but
I
was
curious
if
there
is
an
api
of
sorts
that
we
could
use
to
trigger
an
issue
to
be
created
within
git
lab
and
even
a
robust
api
to
do
a
lot
of
what
you
showed
us.
Secondly,
I
was
curious
if
git
lab
is
able
to
handle
all
languages
of
code,
we
use
cold
fusion
primarily,
so
I
will
for
a
few
of
these
defer
to
a
colleague,
but
some
of
this
I
can
answer
there
is
an
api
of
sorts.
B
We
do
have
integrations
with
some
something
like
jira
issues,
for
instance,
so
we
can't
integrate
with
that
and
there
are
api
of
sorts
to
use
that
you
can
trigger.
I
will
defer
to
some
of
these
other
pieces
for
this
question
and
get
back
to
you
on
some
and
to
make
sure
that
I'm
going
to
be
technically
accurate
and
we
do
support
multi-language
for
code,
so
you
don't
have
to
worry
about
that
any
language.
Any
platform
next
question
is
what
areas
of
security
spend.
B
B
I
have
an
answer
to
that
from
one
of
my
club
colleagues
here
and
yes,
so
we
do
have
a
slack
notification
service
that
allows
you
to
send
events,
I'm
going
to
add
a
link
here
and
type
it
into
that
and
type
it
into
your
answer.
Adela
k.
I
hope
I
did
not
miss
your
name
too
much,
but
there's
a
link
that
I
just
sent
you
there
in
the
chat
and
and
we
do
have
pipeline
status
changes
and
they
are
available
in
those
list
of
notifications
with
the
slack
integration.
B
And
it
looks
like
you
have
quick
questions
there,
but
it
doesn't
look
like
the
rest
of
your
comment
got
in.
So,
if
you'd
like
to
retype
that
one
with
the
question
we'll
be
happy
to
look
at
that,
but
it
may,
it
may
have
not
made
its
way
into
the
chat
and
then
marco
soldat.
Thank
you
for
your
question.
You
say
we
are
actively
using
gitlab.com
already
with
our
own
jenkins
or
cicd.
Could
you
provide
a
video
or
webinar
on
how
we
can
integrate
with
our
kubernetes
cluster?
B
B
B
B
Okay,
here
is
a
we
thank
you
for
for
typing
those
back
in.
Where
can
I
get
a
great
get
started
doc
tutorial,
which
can
help
me
learn
by
doing
awesome
question
we
have
a
bunch
of
those
we
will.
I
am
happy
to
send
you.
We
can
send
you
multiple
resources,
whether
it
depends
on
whether
you
like
to
to
watch
and
learn
or
maybe
read
and
learn.
We
have
quite
a
few
different
things.
We
can
send
you
today.
B
B
Cool
so
yeah,
we
have
a
look
at
it.
It
may
take
a
couple
days
or
a
few
days,
because
we
have
a
little
work
to
do
on
our
side
to
get
that
information
out
to
you,
but
we
will
definitely
be
sharing
the
the
sessions
recording
link
and
and
then
I
will
publish
a
version
of
the
slice
to
share
with
you
as
well.
B
You
couldn't
find
courses
in
pluralsight
or
linkedin
learning
with
get
lab
ci
cd.
Where
can
I
find
that
I
have
a
git
lab
course
for
universities,
or
was
that
asking
if
we
have
a
gitlab
course
for
university
students
juan
guillermo?
If
you
want
to
clarify
that
for
me,
we
can.
We
can
get
back
to
you
and
we
do
have
some
learning
resources
that
we
can
send
you
there
as
well
and
then
tammy
to
echo
zaywoo.
Will
everyone
get
the
watch
and
learn
link?
B
Questions,
for
example,
just
give
up
have
a
course
for
university
students.
You
know
I,
I
don't
think
we
have
a
specific
course
for
university
students,
although
I
will
have
to
double
check
on
that.
For
you
to
be
sure
we
do
have
something
really
cool
called
learn
it
gitlab,
which
is
like
a
a
linear
or
a
sequential
learning
and
training
for
for
gitlab.
So
that
may
be
something
that's
applicable
here,
but
that's
a
great
question
juan.
B
I
will
make
sure
that
we
don't
have
anything
specified
for
university
students,
but
I'll
check
on
that
and
follow
up
with
you
and
then
we
did
just
have
one
more
come
in,
can
gitlab
be
used
to
orchestrate
and
deploy
ms
ssis
ssas
and
ssrs
packages.
I
have
a
colleague
that
probably
knows
more
about
this
on
my
on
the
call,
so
I
will
defer
to
him
and
get
back
to
you
on
that
grace
because
I
do
not
know
off
offhand
and
that
looks
like
the
live
questions.
Andre
did.
A
B
Yeah
yeah,
okay,
so
we
do
have
a
good
answer
for
that.
So
gitlab
you
can
use,
you
can
build
containers,
you
can
script
it
and
it
can
be
done
pretty
easily
with
gitlab
cicd
and
we
also
have
in
a
built-in
container
repository,
and
so
yes,
we
we
can
help
with
that
and
it
does
have
a
built-in
content
repository.
So
good
question,
I'm
glad
you
caught
that.
I
missed
that
one.
C
B
C
B
A
B
And
then
barry,
I
see
you
just
had
a
question
coming,
I'm
on
silver
tear
or
security
functions.
Can
I
can
I
do.
I
will
send
you
a
link
with
our
with
some
some
key
value
about
those
tiers
of
security,
rather
than
kind
of
just
going
boom
boom
boom
down
list,
but
we'll
get
you
we'll
give
you
some
links
with
what's
included
in
each
in
each
tier,
in
that
realm.
A
Yeah,
if
we
didn't
get
to
your
question,
I'm
sure
we'll
get
to
this
after
the
webcast
as
well.
This
will
be
double
checking
on
those.
So
that
thing
thanks
parker
for
very
informative
session.
That's
all
we
wanted
to
cover
in
today,
as
we
mentioned,
recording,
will
be
shared
with
you
by
email.
So,
thanks
again,
bye-bye
thanks.