6. Agenda
● DevOps 101: Culture than technology
● Salesforce DevOps Ecosystem
● Use case: Salesforce GitOps
● QA Session
7. Andrew Davis
Sr. Director of
Research and Innovation
at Copado
Jeff Gallimore
Chief Technology and
Innovation Officer at
Excella
Ron Westrum
Professor of Sociology and
Interdisciplinary
Technology at Eastern
Michigan University
Sebastien Colladon
Technical Architect at
Salesforce
33. Don’t argue with science!!!
Forsgren, N., J. Humble (2016). "The Role of Continuous Delivery in IT and Organizational Performance." In the Proceedings of the Western Decision Sciences Institute (WDSI)
2016, Las Vegas, NV.
38. Blameless PostMortems and a Just Culture
“Having Just Culture means that you are making effort to
balance safety and accountability”
39. “Earlier this week, much of the
internet ground to a halt when the
servers that power them suddenly
vanished. The servers were part
of S3, Amazon’s popular web
hosting service, and when they
went down they took several big
services with them. Quora,
Trello, and IFTTT were among
the sites affected by the
disruption.“
43. The Google researchers found that individuals on
teams with higher psychological safety are less
likely to leave Google, they’re more likely to
harness the power of diverse ideas from their
teammates, they bring in more revenue, and
they’re rated as effective twice as often by
executives.
46. DO! Get commitment from all
the appropriate players.
DON’T! Use an ad hoc or
improvisational approaches.
DO! Use the scientific method.
DON’T! Use experiments to as a
tool for evil.
51. • Changes to the source are Automatically Tracked
• Entire Package (all metadata) always version controlled
• Dev, Test and CI executed via force:source commands via CLI or VS Code
• Release Schedule for each QA, Production Deployment
• Release Artifacts are every merge to master from staging
• CD and Release Mgmt executed via force:source:deploy commands
Version Control System (repo) [i.e. GitHub]
Develope
r
Sandbox
Develope
r
Sandbox
Developer
Sandbox
Full SBX
(QA Env)
PROD
Code
Develop + Unit Tests
Build
Integration + UA
Test
Staging + UAT
Release
Training + Deploy
force:source:push
force:source:pull
force:source:deploy
| CLI or VS Code
| GitHub Actions CLI
53. CI/CD Pipeline
Production
UAT
SIT
integration
stage
master
Validation / Deployment
Validation / Deployment
Validation / Deployment
• Developers add their assets to dev branch and
create
Pull Requests against integration branch
• GitHub Actions starts validation against SIT2 org
• If validation succeed one of architects approves and
merges so GitHub Actions deploy it to target org
• Developers add their assets to dev branch and
create
Pull Requests against stage branch
• GitHub Actions starts validation against Staging org
• If validation succeed one of architects approves and
merges so GitHub Actions deploy it to target org
• Developers add their assets to dev branch and
create
Pull Requests against master branch
• GitHub Actions starts validation against Staging org
• If validation succeed one of architects approves and
merges and manually deploy via GitHub Actions
Only Pull Requests against build branch
56. Install SFDX CLI
Decrypt key
Setup job
Run actions/checkout@v2
Authorize
Install SGD App and Create Delta
Validate and Run Tests on Metadata
Post Run
actions/checkout@v2
Complete job
Install SFDX CLI
Decrypt key
Setup job
Run actions/checkout@v2
Authorize
Install SGD App and Create Delta
Deploy and Run Tests on Metadata
Deploy Destructive Changes
Post Run
actions/checkout@v2
Complete job
Validate Destructive Changes
Prospect GitHub Action Workflow
Validation Deployment