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.
| Environment | Purpose | Refresh Strategy | Data Strategy | | :--- | :--- | :--- | :--- | | | Ephemeral feature testing | On every PR | Sample dataset (100 records) | | Integration (CI) | Merge validation & conflict resolution | Nightly (auto) | Anonymized production subset | | Staging/UAT | Business sign-off & performance | Bi-weekly | Full copy (masked) | | Production | Live customer environment | Never (backup only) | Live data | 4. Tooling Landscape: Build vs. Buy Architects must decide between the Salesforce DevOps Center (native, free, immature) and ISV solutions (costly, robust). 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 Buy Architects must decide between the Salesforce DevOps