Salesforce DevOps enables organizations to operate Salesforce at scale through continuous innovation delivery. This involves establishing a CI/CD delivery pipeline that integrates version control, automated testing, and deployment across environments from development to production. Separating deployments from releases allows for safer rollouts through techniques like feature flags, permissions, and A/B testing. DevOps is a journey that starts with getting the basic foundations in place and continually improving processes over the long term.

1. Discover Salesforce DevOps
with Copado CI/CD automations

2. Don’t wait until the end to ask your question!
● Technical support will answer questions starting now.
Respect Q&A etiquette
● No need to repeat questions. The support team is working their way down
the queue.
Head to the Trailblazer Community
● More questions? Visit http://trailblazer.salesforce.com/answers
Have Questions?

3. Go Social
@salesforcedevs
Salesforce Developers
Salesforce Developers
Salesforce Developers

4. Forward-Looking Statement by Salesforce
This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the
assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we
make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber
growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any
statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.
The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new
products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in
our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the
immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new
releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise
customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the
most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are
available on the SEC Filings section of the Investor Information section of our Website.
Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be
delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available.
Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements.
Statement under the Private Securities Litigation Reform Act of 1995

5. Your Hosts
• Fifteen years IT and Management experience
• 16 Salesforce Certifications
• Four years full-time focus on Salesforce DevOps
• Senior Product Manager at Copado
• 15 Years on the Salesforce Platform
• 7 Yrs at Salesforce on the Platform Team
• Focus: Cloud App Dev, APIs, Integration
• SVP Marketing and Alliances Copado
Andrew Leigh Andrew Davis

6. Agenda
01 Why DevOps for Salesforce?
02 Delivery Performance
03 Delivering Innovation
04 The Innovation Pipeline
05 Quality and Testing
06 Release and Deploy
07 Questions?
Agenda

7. What is DevOps?

8. DevOps Enables You to Operate Salesforce at Scale
Only 10% of CIOs say they are very successful at rapid software development and deployment
INNOVATION VELOCITY
TRUST & QUALITY
CREATE TEST RELEASE
PLAN MONITOR
Go-Live Gap
DELIVERY PIPELINE
SFDC DevOps Needs
FEEDBACK LOOP
SALESFORCE
PLATFORM
Go
Live!
Merge Conflicts
No Collaborative Development Tools
No structured release process
No source repositories
Trouble Keeping Sandboxes in sync
No Integration with 3rd party DevOps Tools
Lack of version control
Lack of compliance
DEPLOY

9. Why Salesforce DevOps?
Which of these areas do you believe you could improve for your organization if your team was able to
prioritize improvements to your Salesforce development and release process over the next 3-5 years?
Salesforce DevOps Is Paying Off
$5 Million In Benefits
17% of Respondents
What business impacts have you seen from your
Salesforce DevOps strategy?
Why Do Salesforce Customers Move to DevOps?

10. The Challenge: Two Competing Motivations
Developers focus on
Change
Ops/Admins focus on
Stability
* Salesforce Admins
function more like
developers!!!

11. Text
■ Text
These Two Motivations
are in Tension
▪ Competitive disruption
▪ Unserved needs
▪ Inefficient systems
▪ Excluding people
▪ Ignoring opportunities
▪ Unsustainable future
What’s at risk if we don’t change?
Things have to change …. fast
▪ Trust
▪ Security
▪ Compliance
▪ Quality
▪ Users
▪ Customers
▪ Money
What’s at risk if we change?
… but there’s a lot at risk

12. DevOps Breaks Down the Silos That Hold Your Team back
Change your culture by changing the communication across teams
INNOVATION DELIVERY PERFORMANCE
➔ Faster Time to Market
➔ More Secure and Stable Releases
➔ Align Business Goals With Technology
➔ Optimize Salesforce Performance
➔ Measure Digital Transformation Progress SECURITYADMIN
ARCHITECTDEVELOPER
CIO
IT SALES MARKETING OPS

13. System-level Thinking: Data Driven DevOps

14. How Do You Measure Your Performance?
“Faster delivery alone merely leads to customer disappointment when the software
delivery process defers to velocity without also addressing quality”
PERFORMANCE FACTORS:
➔ Size of the Delivery Team
➔ Number of Users
➔ Number of Production Orgs
➔ Amount of Customization
➔ Use of a DevOps tooling
The Four Measures of Delivery Performance
Time from code
committed to production
• Shorter is better
• Faster feedback cycles
• Adjust to the market
How often you release to
production
• More is better
• Small batch size
• More market agility
How long to recover from
failures released to
production
• Shorter is better
• Decrease customer exposure
• Decrease down time
Percentage of releases
requiring rollback or fixes
• Less is better
• Early detection is critical
• Automation is important
8hrs Hourly 10% 60min

15. SALESFORCE INNOVATION PERFORMANCE
LEAD TIME FROM
DEV TO
PRODUCTION
RELEASE
FREQUENCY
CHANGE
FAIL RATE
RESTORE
TIME
ELITE
(Top 13% of SFDC)
Less than one
hour
On
Demand
0-15% Less than
an hour
HIGH
(36% of SFDC)
Less than one day
O
Between once per
day and once per
week
0% - 15% Less than a day
MED
(43% of SFDC)
Between one day
and one week
Between once per
day and once per
week
16% - 25% Between one day
and one week
LOW
(8% of SFDC)
Between one week
and one month
Between once per
week and once
per month
51% - 75% Between one day
and one week
IMPROVEMENT
2555x
Faster
46x More
Releases
8x Fewer
Failures
96x Faster
Restore Time
State of Salesforce DevOps 2019
How Do You Compare to Your Peers?

16. Real World Example:
Benchmark Your Performance
Use the 4 Performance Metrics
Use Salesforce Native Dashboards
Value Stream Mapping
Salesforce Analytics
Benchmark your Salesforce Innovation Performance

17. 02 Salesforce Dev

18. Salesforce Development
There are tons of books, conferences, videos, and groups who can help
You don’t need me to tell you how to develop on Salesforce

19. Real World Example:
Commit Changes via a Command Line Interface
Do everything you need from the IDE
Leverage Git and SFDC Commands
Leverage Agile tools like Jira
Leverage User Stories and CCD
CLI is a plugin to the SFDC CLI (SFDX)
Authenticate
& Set User
Story
Push
Changes,
Validate, &
Submit
Use Your
Favorite IDE
To Develop
Solution
Commit
Changes
Repeat as Required
TYPICAL DEVELOPER FLOW
> sfdx force:auth:web:login
Successfully authorized joedev@mycompany.com with org ID 00D0Y000002HsLKUA0
You may now close the browser
> sfdx copado:auth:set -u joedev@mycompany.com
Copado CLI configured…
Step 1: Authenticate
> sfdx copado:work:set -a Jira004
User Story US-0031295 configured
Step 2: Set the User Story using Jira
Set the User Story
Primary Agile Tool External ID (-a),
Copado User Story Name (-u), or
Copado User Story ID (-i)
Local branch is created and checked out.
> git commit -a -m "Updated FinanceManager Unit Test class"
Step 3: Make Changes & Commit with Git like always
Use any Terminal or Desktop application to deliver changes
-a All Changes
-m Required message for the commit
> sfdx copado:work:push
Success: Pushing all commits to User Story US-0031295
… User Story Commits added
… Metadata Selections Updated
… User Story ready to be submitted.
Step 4: It’s time to push!
All changes are pushed to remote branch (Git Host)
MD is Linked to User Story Copado
Because many developers prefer a CLI

20. Salesforce Architecture
Technical Debt:
The implied cost of additional rework caused by
choosing an easy (limited) solution now instead of
using a better approach.
One of the main roles of architects is to
recognize the risk of technical debt and
to avert that by proper system design
Most of the IT industry struggles with technical debt
Time
Millionsof
LinesofCode

21. Salesforce Architecture
Our research shows that teams are slowing down as they get larger

22. Tight Coupling
Examples:
● Emphasis on procedural code (as opposed
to functional or object-oriented code)
● Highly complex relationships between code
● No modules or packages

23. Loose Coupling
Examples:
● Object-oriented design
● Functional Programming
● Modular architecture
● Run-time dependency injection
● Event-driven architecture

24. Actual Dependencies
in one org
Those Dependencies as
Packages

25. 03 Innovation Delivery
RELEASE
CONTINUOUS INTEGRATION CONTINUOUS DELIVERY
• Prioritize requirements
• New and updated
requests
• Task assignment
• Timeline finalization
• Click and code development
• Commit to version control
• Static code analysis
• CI Pipeline creation
VERIFYCREATEPLAN
• Integration tests
• UI Testing
• Requirements testing
• Security testing
• Delivery Pipeline
• Automated Tests
• Metadata Fast Lane
• Monitor work in progress
• Release to users
• Validate features
CONTINUOUS INNOVATION
MONITOR
DEPLOY
• Innovation Performance Metrics
• Dev and Release Dashboards
• Compliance
Agile Development Iterative Delivery
CI/CD For Salesforce

26. Real World Example: The CI/CD Delivery Pipeline
"Our highest priority is early and continuous delivery of working software”
- The Agile Manifesto, 2001

27. ● Changes are made in production that are not propagated to dev and test
environments
● Changes are made in dev environments that are never moved to test or prod
environments
● Different test environments may have different configurations
● Metadata in different production orgs that is supposed to be consistent may grow
increasingly different
Environment Management
Environments Getting Out of Sync is a Major Challenge

28. Configuration Drift
Identical systems gradually diverge over time as they’re updated
Risks of configuration drift:
● Different behaviors in different Environments
● Environment-specific deployment errors
● Overwritten changes
● Impossible to predict how something will behave in
production

29. ● Systematically propagate changes from development through testing to production
● Accommodate slight differences between orgs (usernames, URL endpoints, etc.)
Environment Management
The challenge
● Strictly limit the kinds of changes that can be made directly in an environment
● Automate deployments to ensure consistency
● Regularly destroy or refresh development and testing environments
● Automate the creation and setup of development and testing environments
The general solution

30. Real World Example: Deploying Relational Data
Enable release managers to deploy complex
relational data easily & reliably between orgs
Benefits:
Key for Enterprises that deploy complex app
configurations like CPQ, CloudSense, B2B
Commerce (Cloudcraze), and nCino
Test Data requires a relational model with realistic
data scrubbed of all PII and sensitive information

31. The Delivery Pipeline

32. Real World Example: The CI/CD Delivery Pipeline
"Our highest priority is
early and continuous
delivery of working
software”
- The Agile Manifesto, 2001

33. Real World Example: The CI/CD Delivery Pipeline
Work is deployed continuously across environments as it is ready and tested

34. Version Control
▪ In general, use Git
You can use any version control system you want
▪ Actively tracking all the work done by developers. Admins are developers too!
▪ It’s a very small step from there to automating your deployments
▪ Automating your deployments opens the door to automating tests and other processes
“Offensive Version Control”
▪ Passively capturing (at least) daily snapshots of your metadata to provide some fallback and history
“Defensive Version Control”

35. Branching Strategy
▪ The following development practices contribute to higher software delivery
performance:
○ Merging code into trunk on a daily basis.
○ Having branches or forks with very short lifetimes (less than a day).
○ Having fewer than three active branches.
▪ Also:
○ High performers have the shortest integration times and branch lifetimes, with branch life and
integration typically lasting hours.
○ Low performers have the longest integration times and branch lifetimes, with branch life and
integration typically lasting days.
Research from the State of DevOps Reports

36. Our Research
Teams who integrate more frequently deploy more frequently

37. Real World Example:
Merge Conflict Resolution ….
Simplify merge conflict resolution
Interactive conflict editors
Resolutions are auto-applied
YAML view for XML metadata

38. Quality and Testing

39. Quality & Testing
● Some amount of our work will be
thrown away
● What remains will be tested
● It will either be tested before
reaching production
● Or it will be tested by end users
On behalf of end users,
● Please test your work!

40. This is
what the
business
requested
This is
what you
built
Quality
has many
levels

41. Testing is a way of verifying quality
● Fast Tests for Developers
○ Static Analysis - Linting
○ Static Analysis - Quality Gates
○ Unit Testing
Developers Need Tests to Give them
Fast Feedback on Their Work
● Comprehensive Tests
○ Automated Functional Testing
■ Code-based Acceptance Testing
■ UI Testing
○ Non-functional Testing
■ Static Analysis - Full Codebase
■ Security Analysis
■ Performance Testing
■ Code Reviews
○ Manual QA and Acceptance Testing
But we also need comprehensive tests
before sending work to prod

42. Create connection behaviors in your
pipeline
Schedule or automate deployments and
back promotions.
Implement quality gates such as
validations, compliance scans or
Selenium tests.
Real World Example:
Continuous Delivery and Quality Gates

43. Deploying and Releasing

44. Releasing
Deploying Releasing

45. Releasing means exposing functionality to users
1. Releasing by Deploying
a. Very straightforward
b. Disadvantages
i. Deployments must be scheduled
ii. Deployments must be coordinated with training and change enablement
iii. Deployments are high risk and high stress
iv. Rollbacks can be very tricky
2. Separating Deployments from Releases
a. Permissions
b. Layouts
c. Dynamic Lightning Pages
d. Feature Flags
e. Branching by Abstraction
There are many ways of releasing!

46. Separating deployments from releases can incur a
cost in terms of technical debt
If you add complexity to enable features to be
temporarily disabled
It’s important to remove that complexity later
The Power of Separating
Deployments from Releases
1. Dark Deployments
a. Deploying during business hours without users noticing
2. Make releases simple
3. Hide work in progress
4. User Acceptance Testing in Production
5. Batch releases to coincide with training/notifications
6. A/B Testing
a. This is common practice in marketing
b. Experiment, see what works best
7. Canary Deployments
a. Releasing to a small group of users to assess impact
8. Easy Rollbacks
The Cost of Separating
Deployments from Releases

47. Start Where You Are
DevOps is a Journey
Salesforce as Source
of Truth. Ad Hoc
Component Releases
Version Control as the
Single Source of Truth,
Manual Branch
Management
Releases based
on user stories for better
collaboration/merging btn
multiple developers and teams
Automate manual tasks
to scale your delivery
and increase efficiency
Continually release
changes all the way to
production for a faster
time to value
Take a long-term, patient view
● Understand your processes using Value Stream Mapping
● Benchmark your current state using the four Software
Delivery Performance Metrics
● Get the basic foundations in place (user story management,
version control, delivery pipeline)
● Identify your current constraint (what limits your flow of
quality work)
● Eliminate that constraint
● Rinse and Repeat

48. Trusted by the Global Leaders
15X
7,086,748

49. 100% SALESFORCE
NATIVE INTEGRATION
DevOps Orchestration
Proxy Agent
Merge Engines
Security / Auth
(OAuth 2.0 support)
Process Builder
Webhooks
Job Scheduling
Global Find & Replace
Alerts & Notifications
Dashboard and Reports
Salesforce APIs
Prod Environments
Profiles
Permission sets
Page Layouts
Roles
Metadata XML
Updated Continuously
SECURITY & COMPLIANCE
Salesforce Platform Security
All major certifications:
ISO, SOC, HIPAA, GDPR, Truste.
Secure API-based architecture
Encrypted credentials
OAuth Support / SSO-enabled
Secure access to repository
On-premise or cloud repositories
User access controls
Compliance hub
Configurable compliance rules
Exception reporting with Alerts
Data Backup & Recovery
Business Continuity
Disaster Recovery
PREBUILT INTEGRATIONS
Agile Planning Tools
IDEs
3rd Party CI/CD Tools
Monitoring
Testing
AI/Analytics
Security/Compliance
NATIVE SFDC EXPERIENCE
Lightning UX
Native Dashboards
Einstein Analytics
Salesforce Mobile
Salesforce Flow
Chatter Collaboration
Workflows and Alerts
Dev/Test Environments
Real World Example: Native CI/CD DevOps Platform for Salesforce
DEPLOY
Pipelines
Deployment
Rollbacks
Data Management
100% Version Controlled
RELEASE
Dynamically Assign Permissions
Release Dashboard
Continuous Integration
SALESFORCE DEVOPS 360
Innovation Performance Metrics
CI/CD Dashboards and Reports
Real Time Monitoring and Alerts
Team Benchmarking
Continuous Delivery
COMPLETE CI/CD PROCESSES
PLAN
Agile Planning Tools
Metadata Tracking
CREATE
Metadata Tracking
Environment Management
VERIFY
Static Code Analysis
Selenium Recorder
Apex Tests
Metadata Validation
Manual Test Scripts
Pull Requests

50. Questions?
Get a Copy of Salesforce
DevOps Report
Get a Personalized Salesforce
DevOps Assessment
go to copado.com

51. Enterprise Security & Compliance for Salesforce DevOps
Secure Architecture
● Secure Platform & Application Architecture – built on
Salesforce / Heroku platform
● Secure communications using oAuth (v2.0) and multiple
layers of runtime authentication
● Single-Sign-On (SSO) Support and Secure, encrypted
credential storage & access
Secure Communications and Access
● Securely access your repositories on-premise or in the
cloud (with multiple access levels)
● Full control over user provisioning & access controls
Audit Trails, Backup & Recovery
● Enterprise-class Data Backup & Recovery
● Logging & monitoring all security and access events
Meeting Security Standards
● Received certifications for all major standards:
○ EU-U.S. and Swiss-U.S. Privacy Shield
○ ISO 27001/27017/27018
○ Service Organization Control (SOC1,2,3)
○ TRUSTe, Payment Card Industry (PCI)
○ HITRUST, GDPR, FedRAMP, HIPAA, IRAP
Policies and Systems
● Annual security reviews and penetration testing
● Formal Change Mgt, Incident Mgt, SDLC processes & formal
Corporate Security Policy
● Enterprise-class Business Continuity & Disaster Recovery
Compliance
● Industry’s 1st & only Compliance Hub for SF DevOps
● Set Compliance rules with exception alerts

52. What is Continuous Integration?
(CI) is the process of integrating and testing the work of all
developers and teams on an early and ongoing basis, at
least daily
Benefits
● Find errors as early as possible
● Reduce integration problems
● Avoid compounding errors
Solutions:
● Next Gen CI Pipelines
● Prebuilt Repository Integration
● Metadata Selection Grid
● Advanced Branch Management
● Conflict Resolution
● Integration Analytics
New Winter ‘20
New Winter ‘20
COPADO
CONTINUOUS INTEGRATION

53. Next Gen CI Pipeline Manager
Process collaboration drives faster development times
Realtime Pipeline Visualization
Simplified Submit
Fine Grained Testing Rules
Scheduled Back Deployment

54. Automatic Merge Conflict Resolution
….
Increase your team collaboration
Reducing the amount of overwrites.
Use the DX Source File format
Updated our metadata grid
Easier to digest all your metadata.
1, 2, and 3 Panels

55. What is Continuous Delivery?
“Get changes of all types including new features, configuration
changes, bug fixes, and experiments into production and in the
hands of users, safely and quickly in a sustainable way.”
Jez Humble, author of Continuous Delivery
Benefits
● Ensure every change is releasable
● Increase release velocity
● Improve release quality and security
Solutions
● Next Gen CD Pipelines
● Auto Deploy
● Quality Gates
● Smart Behaviors
● Continuous Verification
● Advanced Data Deploy
● MD Fast Lane
● Delivery Rollbacks
● Audit Trails
● Delivery Analytics
New Winter ‘20
New Winter ‘20
New Winter ‘20
New Winter ‘20
New Winter ‘20
COPADO
CONTINUOUS DELIVERY
New Winter ‘20

56. Auto Deploy - Automated and
scheduled Deployments and Back
promotions
Quality Gates - Automated tests and
manual approvals using quality gates
Smart Behaviors - Default behaviors
with overrides as needed
MD Fast Lane - Specification of which
Metadata to expedite and which to
inspect
Next Gen Pipeline View on the
movement of changes through the
pipeline
New Copado Continuous Delivery

57. Dynamic Pipeline Editor
Two Clicks to Take Any Action
Hover to Get More Detail
Next Gen CD Pipelines

58. Advanced Data Deploy
Enable release managers to deploy complex
relational data easily & reliably between orgs
ADD is broken out into 3 components
1. Data template editor
2. Data deployment wizard
3. Advanced Data Step
Benefits:
Key for Enterprises that deploy complex app
configurations like CPQ, CloudSense, B2B
Commerce (Cloudcraze), and nCino
Test Data requires a relational model with realistic
data scrubbed of all PII and sensitive information
The existing Copado data feature requires high
technical knowledge to manually create relational
queries and understand the data model of the
records they’re migrating. This feature now makes it
easy for you to manage instead.