►
From YouTube: Salesforce Development with GitLab
Description
This video was recorded to share the capabilities available to people who want to use GitLab for Salesforce development. Mayank leads us a demo of the capabilities.
A
Yes,
okay,
so
I'm
gonna.
First
point
you
to
earn
a
lot
of
the
resources
are
to
get
informed
on
what
our
integration
and
the
work
looks
like
I'm
sure,
you've
already
seen
get
calm,
that's
50
X!
This
is
where
we
keep
most
of
our
demo
demo
projects
or
templates
for
CS
CD,
and
the
templates
for
the
prod
get
project
itself,
yep,
so
I'm,
starting
with
the
gate
lab
project.
This
basically
is
a
bone
file
structure
to
store
your
apex
coding
and
metadata
majority
of
this
project.
A
A
Those
are
metadata
changes,
so
that's
like
metadata
associated
with
all
the
change,
that's
associated
and
stored
in
your
org.
Now,
if
you
pull
that
org
down,
if
you
pull
that
data
down,
there's
some
CLI
commands,
you
can
run
I'll
show
you
that
in
shortly
you
pull
that
metadata
down
locally.
You
can
store
it
in
this
for
SAP
repo
and
that's
where
your
metadata
would
be
held.
A
In
that
that
directory,
you
can
package
it
with
Salesforce
as
well,
so
that's
basically
the
equivalent
of
like
building
a
binary
right,
but
instead
they
just
package
it
which
you
version
that
is
unlocked
and
you
can
push
it
up
into
Salesforce
and
you
can
merge
and
control
that
that
application
itself
right.
The
alternative
is,
if
you
don't
package
it,
that's
what
you
call
instead
of
if
you
do
packages
called
package
based
development.
A
If
you
don't
package,
it
that's
called
or
based
development,
and
that's
where
a
majority
of
the
users
are
doing
developing
is
that
bunch
of
these
orgs
they
propagate
changes
through
different
or,
if
there's
all
manual
processes.
What
we're
hoping
to
do
is
with
this
template
get
you
started,
get
that
metadata
and
to
get
so
at
least
that
is
being
version
controlled
and
from
there
you
can
automate
that
deployment
and
integration
and
testing
process
through
the
pipeline.
So
we.
A
A
A
If
you
wouldn't
mind,
while
I'm
talking
checking
that
you
have
access
to
the
settings
that
have
access
to
CS
CD,
then
you
can
validate
that
you
can
actually
much
come
pipeline
yourself
if
I
go
to
the
registry
within
the
for
SAP.
This
is
where
all
the
code
is
residing
in
this
example:
I'll
be
showcasing
project
project,
sorry
package
based
deployment,
and
so
here's
some
of
the
variables
you'll
need,
if
you're
doing
an
oral
base
for
package
based
right.
All
these
variables
are
already
preset
in
this
project
repository,
but
basically.
A
C
D
A
A
If
you
don't
already
have
an
account
with
a
playground
environment
or
have
a
dev
hub
already
pre-configured
and
kind
of
have
that
have
some
kind
of
background
knowledge
on
SFF
DX
to
get
these
values
as
well,
so
I'll
see
if
I
can't
clone
in
to
get
logged
up,
Tom
orange
and
you
guys
can
test
from
there.
But
thanks
for
checking
for
me,
you're.
A
A
Various
environment
off
URLs
on
my
sandbox,
which
is
effectively
kind
of
staging,
but
then
you've
got
production
and
then
there's
also
this
concept
of
scratch
or
works
they're,
basically,
ephemeral,
orgs
that
you
can
turn
a
deploy
tube
for
review,
apps,
functionally
right,
okay,
so
time
being
is
set.
Let's
just
go:
let's
just
go
to
the
repository
and
create
a.
A
To
the
pipeline
will
run
so
the
M
our
branch
pipe
line
is
a
bit
different
than
the
master
branch
pipe
line,
as
defined
in
the
CI,
CD
template,
and
so
it'll
do
some
preliminary
testing,
what
apex
sassed
some
secrets
asked
and
some
lightning
web
components.
So
just
do
some.
You
know
very
simple
testing
to
validate
that.
The
code
is
right,
the
links
correct
and
some
security
testing
as
well.
In
this
stage
it
basically
creates
an
ephemeral
environment.
This
is
what
they
call
scratch
towards
this
relatively
newest
Salesforce.
A
Now
many
people
are
using
it
today
about
many
customers
have
adopted
it
today,
however,
you're
seeing
a
bit
of
an
uptick
on
other
partners
that
I
should
develop
for
sales
forces
marketplace
or
app
exchange
they're,
actually
using
it
a
lot
more
than
your
traditional
enterprise
customers.
But
anyway
we
use
this
inherently.
There
is
a
quota
limit
for
each
customer,
so
they're
using
the
free
tier
of
scratch.
B
A
B
A
C
A
D
A
A
A
Think
by
default
they
get
like
five
a
date
or
something
I'm,
not
a
hundred
sighs
sure,
but
out
of
the
box.
They
should
be
able
to
consume
this.
If
they
want
to
use
it
from
many
pipelines
per
day,
then
they
and
they
want
to
use
scratch.
Orgs
then
they'll
buff
it
up.
Technically,
you
don't
have
to
use
a
scratch
work.
Many
organizations
can
even
just
deploy
straight
to
their
staging
environment
and
not
even
go
through
the
ephemeral
use
case.
It
doesn't
cause
a
little
bit
more
complexity
because
they're
managing
multiple
environments.
A
That
way,
but
you
know
it
just
it's
just
deploying
to
a
target.
You
can
easily
substitute
scratch
or
turn
them
off.
If
you
wanted
to
there's
an
environment
variable
for
that
the
project
you
can
turn
the
scratch
on
call
or
you
could.
You
know,
amend
the
CI
CD
template
to
deploy,
go
sandbox
or
againsted,
which
customers.
D
Quick
I'm,
a
quick
google
of
like
dev
hub
Salesforce,
comes
up
with,
with
all
the
with
a
link
to
enable
death
hub
in
your
organizer
you're
actors.
You
need
to
consider
which
is
like
yeah,
maximum
six
scratch,
orgs
maximum
the
free
active
at
any
one
time
etc.
But
that's
for
the
dry
apparel
trial
licenses,
yeah
that
make
sense
seems
that
information
is
very
easily
accessible,
I
think.
A
Documenting
various
aspects
of
Salesforce,
so
I've
never
had
an
issue
with
that,
but
just
getting
the
street
knowledge
on
how
to
use
their
CLI
I
think
that's
still
hard
to
come
by
their
documentation
is
great,
but
actually
how
to
use
it
properly.
Sometimes
you
know
it
comes
with
experience
and
I
often
have
to
ask
for
help
in
that
regard.
A
So
some
of
the
questions
that
are
really
useful
to
ask
customers
or
are
you?
How
are
you
building
and
doing
development
they're
doing
completely
manual?
The
first
step
is
to
get
them
on
get
at
least,
and
if
they
are
already
using
it
or
are
using
some
notion
of
version
control
and
they
want
to
automate
the
process,
then
you
have
to
ask
them
where
you
use.
Are
you
doing
form
based
where
you're
just
managing
metadata
or
using
package
Facebook
we're
actually
creating
the
package
and
versioning?
It
then
deployed
it
and
if
they
say.
A
Package
based,
then
comes
the
you
know:
follow-up
like
how
do
we
automate
this
process?
How
do
we
start
with
this
template
and
amend
it
moving
forward
for
their
use
case
and
if
they're,
using
automation
or
they
familiar
with
SSD
X,
because
being
familiar
with
s,
FBX
become
the
prerequisite
of
really
getting
the
best,
really
realizing
the
automation
aspect
of
Salesforce
already
alright.
So
this
was
the
output
so
yeah.
So
while
this
is
creating
the
scratch
or
let
me
walk
you
through
an
existing
pipeline
I.
A
Think,
let's
look
at
this
one.
This
should
be
an
M
our
pipeline
here
created
it
and
here's
the
merge
request
and
I
wanted
to
show
you
here.
So
what
happens?
This
is
a
good
murder
quest
to
showcase
what
happens
is
you'll
see
the
review
up,
but
I
didn't
show
up
because
the
scratch
one
is
ephemeral.
I
can't
really
click
into
it,
because
it's
already
died.
A
We
go
back
to
the
pipeline
real,
quick,
so
right
out
of
the
box,
you
should
be
able
to
see
some
security,
criticals
and
mediums
show
up
for
this
example
and
within
the
jobs
we've
got
a
manual
step
of
delete
the
scratch
or
again
as
well
after
its
created.
Once
your
build
was
reviewing
it,
you
can
just
delete
the
scratch
org
or
automatically
after,
like
I,
think
three
days
or
so
it
automatically
deletes
and
gets
erased.
D
A
E
A
B
A
So
by
default
is
set
to
true
I,
think
you
have
explicitly
set
it
to
false
all
right,
but
anyway,
as
you
saw
like
the
review
app
has
done.
Some
of
the
testing
failed
I'm
looking
to
that,
but
that's
just
some
unit
testing
and
functional
testing
I
believe
so,
if
we
click
on
the
view
app
it
automatically
logs
you
into
the
org.
So
this
is
a
straight
single
sign-on,
directly
accessible
and
the
app
that
we
deployed
is
called
the
bike,
the
bike
store.
So
if
I
go
into
you
I
changed
a
bit.
A
A
A
B
A
What
happens
so
here?
It's
installed
with
the
CLI
stalling
jq4
quarrying
scratch
or
about
better
case
against
the
URL
sweet,
so
this
runs
scratch
or
scratch
old
name.
This
is
running
some
s,
FDX
testing.
So
if
you
look
at
the
NSF
PS
command,
it's
doing
some
apex
testing,
but
code
coverage
I
think
it
includes
linking
as
well
and
then.
Furthermore,
when
you
actually
upload
the
artifacts
look
at
the
CI
CD
template,
you
can
kind
of
look
at
what
would
be
outlined,
what
what
actual
testing
is
actually
doing?
A
A
A
A
Cool
so
I'll
go
into
too
much
detail
there.
The
other
thing
that
I
want
to
show
you
some,
fortunately
app
didn't
deploy,
but
I
look
at
an
existing
pipeline.
Instead,
where,
once
you
actually
merge
to
master,
you
will
see
the
longer
pipeline
that
deploys
is
staging
and
production
and
look
at
this
pipeline.
For
example,
this
one
goes
through
testing
again
it
creates
another
scratch
or
to
do
some
functional
unit
testing
and
then,
after
that's
done,
it
creates
a
package.
A
What
the
pipeline
looks
like
in
the
m
ru
c--
environments
for
prod
review
and
staging
as
well,
so
you
can
click
into
them
in
this
demo,
you
can't
actually
log
into
staging
or
production,
because
it's
as
someone
else's
salesforce
ID
that
I'm
actually
piggybacking
off
of
I.
Don't
have
the
authentication
to
go
in
their
sandbox
order,
the
production
or,
but
you
can
the
review
app
with
a
single
sign
on
it.
D
A
E
B
A
A
A
D
A
D
D
A
A
B
C
C
D
B
E
B
Yeah
there
is
some
some
I
guess
that
gives
a
webinar
there.
If
you
guys
wanted
to
see
a
webinar
I
mean
my
yankin
and
Francis
I
did
a
couple
of
webinars
with
Salesforce
I,
guess
some
other
stuff
there
as
well.
That's
been
included
in
the
actual
demo
project
readme
file,
so
yeah
like
some
useful
background
material
there
as
well
yeah.
D
I
mean
I
think
the
first
case
is
yeah,
finding
out
exactly
what
they
use
cases
in
terms
of
whether
they're
doing
it
all
based
or
package
based
where
they
are
with
their
journey.
In
that
sense,
then
it's
a
case
of
like
showing
them
what
we
can
do
to
support
those
two
different
methods,
and
then
it's
going
to
be
a
case
of
answering
questions
that
they
have.
They
may
have
on
those
points
there
I
mayn't
means
get
back
in
touch,
but
but
yeah,
it's
a
really
good
sign.