You are here:
Install and Configure DevOps Center (Managed Package)
A Salesforce admin or user with the appropriate permissions can install DevOps Center (Managed Package). A Salesforce admin or user who is assigned the DevOps Center Manager permission set can configure DevOps Center.
Required Editions
| Available in: Lightning Experience in Enterprise, Performance, Professional (API access required), Unlimited, and Developer Editions. |
| Available in: Government Cloud Plus as interoperable. Turning on DevOps Center in Government Cloud Plus orgs can send data outside the authorization boundary. Contact your Salesforce account executive for more details. |
| Not available in: EU Operating Zone. EU Operating zone is a special paid offering that provides an enhanced level of data residency commitment. DevOps Center is supported in orgs in the EU that aren’t part of EU OZ, per standard product terms and conditions. |
| User Permissions Needed | |
|---|---|
| To install and configure DevOps Center: | “Download AppExchange Packages” |
To install DevOps Center in a Professional Edition org, the org must have API access, which enables DevOps Center to access data from the source control system. If you attempt to install DevOps Center in a Professional Edition org without API access, an installation error occurs. Contact your Account Executive to request the API add-on.
Check out this video, which explains how to securely manage and release changes in Salesforce using sandboxes and DevOps Center.
Install the DevOps Center package in a supported org edition from the DevOps Center Setup page. You can install DevOps Center in the org that is the final release org in your pipeline, or in another org that’s unrelated to the orgs in the pipeline. After you install it, you connect DevOps Center to any environments that you use for development, testing, and final release.
As part of the configuration process, you add DevOps Center users in the org in which it’s installed. You can provide minimum access to the org by assigning users either the Identity Only or Salesforce Limited Access - Free license. Then you assign users to DevOps Center permission sets that determine what tasks they can perform in the DevOps Center app.
Why Can’t I Install DevOps Center in a Sandbox?
DevOps Center is a managed package that is installed in an org that acts as a “hub” for the application. From within DevOps Center, you connect to your development orgs, pipeline environments, and release orgs. DevOps Center doesn’t interact with the existing data in the org, yet generates data in the form of custom object records for the custom objects delivered with the package.
We don’t provide the ability to install DevOps Center in sandboxes because:
- Sandbox refreshes result in the loss of DevOps Center projects and their associated records. All your DevOps Center data will be gone.
- It’s designed so that all team members log in to the same org to access DevOps Center. Cloning a sandbox would result in multiple instances of the managed package, which can lead to confusion and synchronization issues for teams expecting to be working against the same projects.
- Unlike some other packages, DevOps Center has no interaction with existing data or metadata in your org.
To evaluate DevOps Center, enable and install it in a Developer Edition org or a scratch org. However, remember that scratch orgs expire.
What Source Control Repositories Can I Use with DevOps Center?
Although we’ve built a framework for DevOps Center to eventually integrate with multiple third-party source control systems, we now support these source control systems:
- GitHub.com Cloud-based plans, including GitHub Enterprise Cloud. Locally hosted versions of GitHub, including GitHub Enterprise Server, aren’t currently supported. See Set Up DevOps Center for GitHub to get started.
- Bitbucket Cloud (beta). See Set Up DevOps Center for Bitbucket to get started.
Provide General Feedback
To provide general feedback, request product enhancements, start discussions with other DevOps Center users or the product team, and share recommended practices, use the DevOps Center Trailblazer group.
- DevOps Center Releases
Based on your feedback and our drive for innovation, the DevOps Center team releases new features, product enhancements, and bug fixes on a regular basis. If you want to know all the goodness included in each package version, you’ve come to the right place. - Evaluate DevOps Center in a Non-Production Org
So you want to evaluate DevOps Center, but prefer to install it in an org other than your production org. Have no fear. You have options. You can completely evaluate DevOps Center using a combination of Developer Edition (DE) orgs and scratch orgs. - Enable and Install DevOps Center in the Org
Enable DevOps Center to provide the permissions needed to install the DevOps Center package in the org. You can install DevOps Center in the org that is the final release org in your pipeline, or in another org that is unrelated to the orgs in the pipeline. - Upgrade to the Latest DevOps Center Version
In most cases, you don’t have to do anything to upgrade to the latest version of the DevOps Center. When we release a new package version, we update your org automatically. - Set Up DevOps Center for GitHub
To use GitHub with DevOps Center as your source control repository, some tasks are performed within GitHub, such as creating a repository and adding team members. And some tasks are performed in DevOps Center, such as setting up the associated DevOps Center project, adding development and pipeline environments, configuring your pipeline, and creating and assigning work items to team members. - Set Up DevOps Center for Bitbucket (Beta)
Set up DevOps Center to use a Bitbucket source control repository. Currently, we support only Bitbucket Cloud. - Manage DevOps Center Projects
Your team’s central arena for work in DevOps Center is the project. The purpose of a project is to help you and your team manage changes being developed for a particular application. - Complete Optional Setup Tasks
Complete these optional setup tasks, as needed. - Manage Environments
When first configuring DevOps Center, identify the environments that you’re going to use for each project. After environments are defined in the Pipeline Environments tab, you can manage each environment from its drop-down menu. - Plan Your Pipeline
A pipeline defines the sequence of stages that work items progress as they go through the release lifecycle from development through to production (or some other final release stage). - Create and Assign Project Work Items
Create work items so that when your team members open DevOps Center for the first time, project work is already identified and assigned to them. - Build an Extension Package for DevOps Center
Salesforce partners and ISVs can use scratch orgs as their dev environments when building managed second-generation (2GP) extension packages that expand the functionality of DevOps Center. An extension is any package, component, or set of components that adds to the functionality of a managed package. An extension requires that the base managed package is installed in the org. - Uninstall DevOps Center
You can uninstall DevOps Center, if necessary. If you plan to reinstall DevOps Center, don't delete the DevOps Center auth providers. However, if you deleted the auth providers, you can recreate them by re-enabling the DevOps Center preference in Setup. - Troubleshoot DevOps Center Configuration
Here are some tips if you encounter issues when installing or configuring DevOps Center.
