| Feature | DevOps Center (Native) | Copado / Gearset / Autorabit | | :--- | :--- | :--- | | | Basic (GitHub only) | Full (GitLab, Bitbucket, Azure) | | Data Deployment | None | Advanced (lookup mapping, data plans) | | Pre-deploy Tests | Manual | Automated (Apex, Jest, Browser) | | CI/CD Orchestration | Minimal | Full (Jenkins, GitHub Actions integration) | | Governance (Approvals) | Basic | Advanced (4-eye, change windows) | | Cost | Free (with Salesforce license) | 5-20% of license spend |
Treat metadata exactly like application source code (Apex, LWC). Every change—from a custom label update to a new Sharing Rule—must be version-controlled in Git. salesforce devops for architects free pdf
Design the pipeline for the worst rollback scenario, not the best deploy scenario. Appendix A: Sample .yml Pipeline (GitHub Actions) name: Salesforce CI - Validate and Deploy on: pull_request: branches: [ main ] jobs: validate: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - name: Install sfdx run: npm install -g sfdx-cli - name: Authenticate to Dev Hub run: sfdx auth:jwt:grant --client-id $ secrets.CLIENT_ID --jwt-key-file keys/server.key -u $ secrets.DEVHUB - name: Create Scratch Org run: sfdx force:org:create -f config/project-scratch-def.json -a validate-org -d 1 - name: Deploy Source run: sfdx force:source:deploy -p force-app -u validate-org -l RunLocalTests -c - name: Run Apex Tests run: sfdx force:apex:test:run -u validate-org -c -r human End of Report | Feature | DevOps Center (Native) | Copado
graph LR A[Feature Branch] --> B(GitHub/GitLab) B --> CPR Validation C -->|Static Analysis & Apex Tests| D(Scratch Org) D --> E[Integration Sandbox] E --> F[UAT Sandbox] F --> G[Production] Appendix A: Sample
This report provides a reference architecture for implementing DevOps in complex Salesforce environments. It covers source-driven development (SDD), metadata API limitations, environment management strategies, and the architectural evaluation of the modern tooling landscape (Copado, Gearset, Autorabit, Flosum, native Salesforce DevOps Center). Historically, Salesforce encouraged declarative development (clicks not code). This created the "metadata chaos" problem: two administrators modifying the same Profile or Custom Field in different sandboxes would inevitably cause deployment collisions.