Salesforce Devops For Architects [2021] Free Pdf May 2026

3. Reference Architecture: The 4-Environment Pipeline While many teams use Dev -> QA -> Prod, the architect’s standard for high-velocity teams is a 4-track trunk-based strategy .

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] salesforce devops for architects free pdf

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. Every change—from a custom label update to a

6. Governance and Compliance for Architects DevOps is the enforcement mechanism for governance. Design the pipeline for the worst rollback scenario,

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

| Governance Rule | DevOps Automation | | :--- | :--- | | No Apex SOSL queries without index review | PMD scanner in PR pipeline | | No hardcoded URLs in LWC | ESLint rule with fail condition | | Profile updates require security lead approval | Git branch protection rule (CODEOWNERS) | | Deployments only during maintenance window | Jenkins pipeline time-based gate |