PERSONAL PROJECT

CI/CD Pipeline — Multi-environment Salesforce Deployment

CI/CD pipeline setup

Context

To ensure quality and traceability of Salesforce deployments across multiple environments, I designed and implemented a complete CI/CD pipeline. The goal: automate Apex validations, tests, and deployments from the development sandbox all the way to production — with a structured Git branching strategy and automated checks on every Pull Request.

What I built

Git branching strategy: feature → develop → staging → main with branch protection rules
GitHub Actions workflow: Apex validation + automated tests triggered on every Pull Request
Automatic deployment to sandbox on develop merge, staging deployment on main merge
Quick Deploy to production after full test run validation
Salesforce credentials management via GitHub Secrets (encrypted SFDX Auth URL)
Deployment status notifications integrated at every pipeline stage

Tools & Technologies

Salesforce CLI (SFDX) — metadata packaging and deployment
GitHub Actions — CI/CD pipeline orchestration
GitHub Secrets — secure SFDX credential management
Apex Test Run — automated unit test execution
SFDX Source Format — Salesforce metadata version control

Implementation steps

1
Analysis
Mapping of environments (Dev, Staging, Prod) and defining a branching strategy adapted to the Salesforce release cycle
2
SFDX Setup
Project initialization in SFDX Source Format, .forceignore configuration and authentication setup via SFDX Auth URL
3
CI Pipeline
GitHub Actions workflows: Apex validation job with unit test execution triggered on every Pull Request to develop
4
CD Pipeline
Deployment automation: sandbox on develop merge, staging on main merge — with Quick Deploy to production after validation
5

Results

Environments covered

Dev, Staging, Production

< 5 min

Validation time

Per Pull Request

Manual deployments

Fully automated

> 75%

Test coverage

Apex — required for deployment