SALESFORCE DEVOPS
(VS code + GitHub + Copado)
What is Salesforce DevOps?
Salesforce DevOps combines development and operations to automate the
process of building, testing and releasing Salesforce applications
It ensures that every configuration, customization, and line of code moves
smoothly from development to production faster, safer and with traceability.
Key Pillars
Source Control (Git)
Automation (CI/CD)
Collaboration (Team Branching)
Continuous Integration & Delivery (Copado, AutoRabit, Gearset)
Salesforce DX & Source Format
Why DevOps Matter in Salesforce
Speeds up delivery and reduces manual errors
Ensures a single source of truth in Git
Gives traceability between user stories, commits and
deployments
Enables continuous delivery (CI/CD)
DevOps turns your Salesforce release process into an automated, reliable
machine.
Tools you’ll need
VS Code + Salesforce CLI - Build and retrieve metadata using salesforce DX source
format
GitHub - Manage version control and code reviews via pull requests
Copado - Orchestrate commits, CI/CD pipelines, and deployments tired to user
stores
Always use Salesforce DX Source Format for metadata - It’s Git friendly and supports
incremental deployments.
Branching Strategies (Copado Supported)
Choosing a strategy shapes how you release:
Trunk-Based Development - Short lived feature branches, continuous delivery
Feature / Release Branching - Controlled releases with QA gates
Environment Branching - Each sandbox = one branch (Strict separation)
Branching Strategies (Copado Supported)
The DevOps WorkFlow
1. Developer Stage
Authenticate your org
Clone the Repo
Make changes locally in VS Code
Retrieve metadata and push to a new branch in Github
2. Github Stage
Open a pull request(PR)
Review → Approve → Merge
3. Copado Stage
link the metadata to the user story
Triggers a CI job to deploy to the QA org (Depends on your setup)
This means every PR automatically updates Copado and pushes your
changes to QA - no manual clicks
Architecture at a Glance
Best Practice
Use short-lived feature branches
Keep metadata commits small & meaningful
Always test in QA before promoting to higher environments (always require
test evidence)
Protect main or develop branches (require PR reviews( 2 or more
approvers) - create policies on the branches)
Document commit messages with the copado User Story ID
Automate back deployments to keep orgs in sync (Avoid code overrides)
Make sure developer have not have edit access on the branches linked to
the sandboxes( also no system admin access in higher environments)
Found it helpful?
LIKE
&
RESPOST