deployment-automation-architecture
Deployment automation architecture on Salesforce: pipeline orchestration, branch strategy, environment topology, quality gates, release trains. Selecting between Copado, Gearset, Flosum, and native SFDX + GitHub Actions. NOT for cloud-specific deploy mechanics (use cloud-specific-deployment-architecture). NOT for CI/CD tool tutorials.
Best use case
deployment-automation-architecture is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deployment automation architecture on Salesforce: pipeline orchestration, branch strategy, environment topology, quality gates, release trains. Selecting between Copado, Gearset, Flosum, and native SFDX + GitHub Actions. NOT for cloud-specific deploy mechanics (use cloud-specific-deployment-architecture). NOT for CI/CD tool tutorials.
Teams using deployment-automation-architecture should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/deployment-automation-architecture/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How deployment-automation-architecture Compares
| Feature / Agent | deployment-automation-architecture | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deployment automation architecture on Salesforce: pipeline orchestration, branch strategy, environment topology, quality gates, release trains. Selecting between Copado, Gearset, Flosum, and native SFDX + GitHub Actions. NOT for cloud-specific deploy mechanics (use cloud-specific-deployment-architecture). NOT for CI/CD tool tutorials.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Deployment Automation Architecture Activate when designing or overhauling the Salesforce deployment pipeline: branch model, environment topology, tool selection (Copado / Gearset / Flosum / Salesforce DX + GitHub Actions), quality gates, release train cadence. This is an architect-level decision that determines release velocity, blast radius, and auditability. ## Before Starting - **Articulate the pain point.** "We want CI/CD" is not a requirement. "Hotfixes take 5 days" or "scratch-org setup is 2 hours" are requirements. Design to the problem. - **Count the teams and environments.** One team and one sandbox is different from six teams and thirty sandboxes. Tooling selection changes with scale. - **Identify the compliance envelope.** SOX, HIPAA, SOC 2 impose audit trail requirements. Copado / Flosum / Gearset offer native audit trails; DIY SFDX + GitHub Actions can match but must be deliberately designed. ## Core Concepts ### Branch strategy Common patterns: trunk-based (short-lived feature branches merged into main) and GitFlow (long-lived develop / release branches). Trunk-based suits fast-moving teams with strong CI; GitFlow suits release-train governance. ### Environment topology Dev sandbox per developer → shared feature integration sandbox → UAT → Staging → Prod. Scratch orgs replace per-developer sandboxes for app/package development. Partial Copy and Full Copy sandboxes for UAT/Staging. ### Quality gates Static analysis (PMD / CodeScan / SFDX Scanner), Apex coverage, security scan (Checkmarx / Salesforce Code Analyzer), validation deploys. Gate failures block promotion. ### Release train Time-boxed release cycles (two-week, monthly). All changes merge by cutoff; everything else waits. Reduces coordination overhead for large orgs. ### Tool category - **Commit-based** (Copado, Gearset Promote, Flosum): Git-native with platform-specific deploy engines. - **Artifact-based**: Build a package per deploy; promote artifacts. - **Native**: SFDX + GitHub Actions / Azure DevOps / Jenkins. ## Common Patterns ### Pattern: Small team, trunk-based, SFDX + GitHub Actions One main branch. PR triggers validation deploy to a feature sandbox. Merge triggers deploy to UAT; manual gate to prod. Low TCO, needs engineering discipline. ### Pattern: Enterprise, Copado / Flosum, release train Multiple teams merge into a release branch on a two-week cadence. Tool tracks stories / user stories, enforces approval gates, generates audit trail. High TCO, lowest coordination friction. ### Pattern: Hybrid — Gearset for data/diff + GitHub Actions for pipeline Gearset handles metadata diffs and data deploys; GitHub Actions orchestrates. Suits mid-size teams that want pipeline ownership but not to build diffing. ## Decision Guidance | Situation | Recommended Approach | Reason | |---|---|---| | <10 devs, engineering-led | SFDX + GitHub Actions | Flexible, low TCO | | 10-50 devs, mixed dev + admin | Gearset + GitHub Actions | Best diff tooling | | 50+ devs, regulated | Copado / Flosum | Audit + governance | | ISV / package-based development | SFDX second-gen packaging | Native packaging | | High change volume, low risk | Trunk-based + fast gates | Velocity | | Low change volume, high risk | Release train + heavy gates | Safety | ## Recommended Workflow 1. Articulate the release problem to solve (velocity, risk, audit, developer experience). 2. Inventory teams, environments, and current pain points. 3. Define branch strategy aligned to team size and risk profile. 4. Design environment topology with explicit promotion path. 5. Select tooling with an evaluation matrix (cost, capability, scale). 6. Define quality gates — static analysis, coverage, security, validation deploy. 7. Roll out incrementally: one team migrates first; iterate; broaden. ## Review Checklist - [ ] Release problem documented and agreed by stakeholders - [ ] Branch strategy chosen with rationale - [ ] Environment topology diagrammed - [ ] Tool selection justified against evaluation matrix - [ ] Quality gates defined and measurable - [ ] Audit trail meets compliance requirements - [ ] Rollback plan documented and rehearsed ## Salesforce-Specific Gotchas 1. **Metadata API deploys are not atomic across components.** A partial failure may leave an environment in a mixed state — design for idempotent re-deploys. 2. **Profiles deploy as the whole profile.** Unintended FLS changes ride along if not diffed carefully. 3. **Destructive changes require a separate destructive manifest.** Tooling handles this differently; validate your pipeline actually deletes what it should. ## Output Artifacts | Artifact | Description | |---|---| | Pipeline topology diagram | Branches + environments + gates | | Tool selection memo | Evaluation matrix + decision | | Quality gate spec | Checks and thresholds | | Rollback playbook | Per-environment rollback steps | ## Related Skills - `architect/cloud-specific-deployment-architecture` — per-cloud mechanics - `devops/cicd-pipeline-design` — implementation patterns - `devops/sandbox-strategy` — environment lifecycle
Related Skills
salesforce-shield-deployment
Roll out Shield (Platform Encryption + Event Monitoring + Field Audit Trail) end-to-end, sequencing feature enablement to avoid data lockout. NOT for Classic Encryption or general PE design.
omnistudio-deployment-datapacks
Use when exporting, importing, or version-controlling OmniStudio components using DataPacks via the OmniStudio DataPacks tool or vlocity CLI. Covers DataPack export/import, Git version control integration, CI/CD for OmniStudio. NOT for SFDX-based metadata deployment of non-OmniStudio components.
flow-deployment-and-packaging
Move a Flow from sandbox to production reliably — source format, version-on-deploy semantics, deploy vs activate, dependency bundling, Change Set vs SFDX vs Unlocked vs Managed, validate-then-quick-deploy, and rollback by activating a prior version. NOT for source-driven setup or branching strategy — see devops/salesforce-dx-project-structure and devops/source-tracking-and-conflict-resolution.
salesforce-cli-automation
Use this skill when automating Salesforce work with the unified Salesforce CLI (`sf`, v2): shell scripts, Make/npm tasks, cron jobs, and CI steps that need stable flags, `--json` output, org aliases, bulk/data commands, plugins, and non-interactive auth patterns. Trigger keywords: sf CLI automation, sfdx migration, JSON output CI, sf project deploy script, sf data bulk, CLI plugins, target-org alias, machine-readable CLI. NOT for choosing or wiring a specific CI platform (GitHub Actions, GitLab, Jenkins, Bitbucket, Azure DevOps—use those devops skills), VS Code Salesforce extensions, or Copado/Gearset release management UIs.
release-notes-automation
Use when generating customer- or stakeholder-facing release notes from git history, Jira/ADO ticket links, and Salesforce metadata diffs at deploy time. Triggers: 'auto-generate release notes', 'changelog from commits', 'release notes from PR titles', 'what changed in this deployment'. NOT for managed-package version creation, push upgrades, or org assessment.
pre-deployment-checklist
Use when preparing a Salesforce metadata deployment for production and need a structured gate-check before releasing. Trigger keywords: 'pre-deploy checklist', 'what to check before deploying', 'validation deploy', 'deploy readiness', 'quick deploy window', 'checkOnly deploy', 'pre-release backup'. NOT for post-deployment smoke tests (use post-deployment-validation), full cutover sequencing (use go-live-cutover-planning), or change set UI workflow (use change-set-deployment).
post-deployment-validation
Verifying Salesforce deployments succeeded end-to-end after metadata lands in the target org. Covers validation deploys (checkOnly), quick deploy from validated IDs, Apex test result interpretation, Deployment Status page drill-down, and rollback strategies. NOT for writing Apex tests (use apex test patterns). NOT for CI/CD pipeline setup (use github-actions-for-salesforce or gitlab-ci-for-salesforce).
permission-set-deployment-ordering
Use when deploying permission sets, permission set groups, or profiles and encountering cross-reference errors, silent permission loss, or ordering failures. Triggers: 'permission set deployment fails', 'cross-reference id error during deploy', 'permissions disappear after deployment', 'permission set group deployment error'. NOT for permission set design or architecture decisions (use permission-set-architecture), NOT for creating permission sets from scratch (use admin/permission-set-architecture).
health-cloud-deployment-patterns
Use when planning or executing a Health Cloud deployment to production or a full sandbox, including managed package installation sequencing, Permission Set License assignment, care plan template setup, HIPAA compliance controls, and post-deploy manual steps not captured in metadata. Triggers: 'how do I deploy Health Cloud', 'HealthCloudGA package install order', 'care plan template not working after deployment', 'Health Cloud HIPAA Shield Encryption setup', 'CarePlanProcessorCallback registration post-deploy'. NOT for Health Cloud data model design (use health-cloud-data-model), NOT for Apex extensions in Health Cloud (use health-cloud-apex-extensions), NOT for API usage patterns (use health-cloud-apis).
experience-cloud-deployment-dev
Use this skill when scripting or automating the deployment of Experience Cloud sites between Salesforce orgs using the Metadata API, Salesforce CLI, or CI/CD pipelines. Covers ExperienceBundle (Aura-based sites), DigitalExperienceBundle (enhanced LWR sites), the ExperienceBundleSettings prerequisite, CMS content exclusion gaps, and required post-deployment manual steps for domain configuration, SSO, and CDN bindings. NOT for general Experience Cloud site building in Experience Builder, OmniStudio-based sites, CMS content authoring, or Salesforce Sites (Force.com Sites) deployments.
experience-cloud-deployment-admin
Use this skill when deploying an Experience Cloud site (formerly Community) between Salesforce orgs or sandboxes — including metadata ordering, ExperienceBundle enablement, post-deployment publishing, and change-set or SFDX-based migration. NOT for: LWC component development within Experience Builder, CMS content migration via Managed Content REST API, or Aura/LWC code authoring.
destructive-changes-deployment
Managing destructiveChanges.xml manifests for safe metadata deletion in Salesforce deployments. Use when deleting metadata components via Metadata API or sf CLI. Covers pre vs post destructive manifests, safe deletion sequencing, dependency handling. NOT for package.xml basics (use metadata-api-and-package-xml). NOT for basic deployment setup (use change-set-deployment).