DevOps Center setup involves enabling the feature, connecting a GitHub repository, defining environments, and assigning user permissions. Plan an hour for the initial configuration; daily use takes minutes.
- Enable DevOps Center
Setup, then DevOps Center, then Enable DevOps Center. Confirm and save. The DevOps Center app appears in the App Launcher.
- Connect a GitHub repository
Open the DevOps Center app. Click Connect to GitHub. Authenticate with a GitHub account that has admin access to the target repo. Pick the repo and the default branch.
- Define the environment pipeline
Add each environment (sandbox or production) to the pipeline. Order them: Dev first, then UAT, then Staging, then Production. Each environment has a tracking branch in the GitHub repo; DevOps Center creates these automatically.
- Assign DevOps Center licenses
Setup, then Users, then Permission Set Licenses, then DevOps Center. Assign the license to developers and release managers. Without it, users cannot create or promote Work Items.
- Create a Work Item
In DevOps Center, click New Work Item. Pick the source environment and describe the change. The platform creates a branch in GitHub and assigns the Work Item to your user.
- Deploy work to the first environment
With the Work Item active, DevOps Center can pull changes from the source sandbox into the branch. Make changes in the sandbox, then commit them through DevOps Center to the branch. Promote the Work Item up the pipeline by clicking Promote.
The unit of change in DevOps Center. Each is a Git branch that promotes through the pipeline.
The configured chain of environments. Defines the promotion path.
A group of Work Items that promote together. Solves the dependency-coordination problem.
The required source-of-truth. Holds all DevOps Center state and metadata.
- DevOps Center requires GitHub specifically. GitLab, Bitbucket, and Azure DevOps are not supported yet. Plan accordingly if your team standardizes elsewhere.
- Some metadata types are unsupported. Industries-specific configurations, certain managed-package metadata, and some platform features cannot be deployed through DevOps Center yet.
- Pipeline changes are slow to propagate. Reordering environments or adding new ones can take several minutes for the platform to reflect.
- Merge conflicts in GitHub do not auto-resolve. DevOps Center surfaces them but you handle resolution in Git, not in the UI.