DevOps Center FAQ
Forward Looking Statement: Please note that we are sharing forward-looking information below, and this information is subject to change. Please remember to make all purchasing and investment decisions based on product that is currently generally available.
Product Basics
- What is DevOps Center?
- DevOps Center provides a full end-to-end experience allowing teams of declarative developers, admins, and programmatic developers to work together to build and deliver software applications using modern best practices around Change and Release Management and DevOps. Users can now use clicks to manage their changes, integrate with source control, and deploy metadata across their test and production environment. This means that low-code users can now work alongside their pro-code counterparts, operating against the same source of truth and utilizing the same modern processes. And DevOps Center is truly available to all, as it’s free/included with Professional, Enterprise, and Unlimited editions!
DevOps Center, ALM Release Management Overview and Vision (3).png
- When will DevOps Center be released?
- DevOps Center was launched as GA on Dec 9, 2022.
- Can anyone use DevOps Center now?
- Yes! Anyone can enable and install it in a production org with Professional (with API Enabled), Enterprise or Unlimited edition, or in a Developer Edition, Trailhead Playground, or scratch org.
- Will DevOps Center be a paid add-on or will it be free?
- We plan to offer a free/included and paid offering. At GA, we will only offer the free/included version which is available with Professional, Enterprise, Unlimited, Developer, Performance editions. Pricing and packaging for the paid offering, which will be released post-GA, are TBD.
- How will DevOps Center be delivered?
- DevOps Center will be delivered as a Managed Package and will be installed into a production org. It can then be connected to any Sandboxes, Scratch Orgs, and Production Orgs to do development and deploy changes.
- What is the future for Change Sets now that DevOps Center is coming?
- The DevOps Center is meant to subsume the functionality provided currently by Change Sets. We don’t have immediate plans to retire Change Sets, but once we have reached functional parity between DevOps Center and Change Sets we will look at possible retirement strategies, and we will communicate that clearly and with plenty of advance notice to our community. We are not planning to further enhance Change Sets at this point.
- Where can I learn more and see it in action?
- Visit and join our “DevOps Center” Trailblazer Community to stay up-to-date with all the latest product news and information, and to engage in conversation about the product. This site contains links to demo videos as well.
Product Integrations
- What source control tools (VCS) will DevOps Center integrate with?
- At the time of launch, DevOps Center is integrated with cloud-based GitHub. We have plans to also support Bitbucket, Azure DevOps Git, GitLab, and Enterprise level editions in the future. Our roadmap provides more information on our plans.
- Do I need to use a VCS tool with the DevOps Center?
- Yes, as source control is central to the DevOps Center experience, it is required that you use a version control system.
- What if I don’t currently use a VCS tool?
- GitHub is easy to sign up with and has free plans!
- Does DevOps Center provide or work with CI/CD tools?
- At GA DevOps Center will be able to work alongside existing CI/CD tools that you may be using with your Salesforce development flows.
- In a future release post-GA we plan to offer built-in CI/CD capabilities
- Will DevOps Center integrate with agile work tracking tools like JIRA or Agile Accelerator?
- Post-GA we have plans to provide integrations to existing work tracking tools like JIRA and Agile Accelerator. Our roadmap provides more information on our plans.
- Will DevOps Center work with GitHub Enterprise or other internal VCS servers?
- We’ll be initially focusing on public services such as GitHub, Bitbucket, GitLab, but as we know that some customers have internal VCS servers we will consider implementations there as well. Internal source repositories have different levels of security policies so we would need to work more closely to understand the path forward. If you are using this kind of implementation and are interested in using DevOps Center we’d be interested to talk with you more to understand your setup and security policies.
Product Functionality
- Will DevOps Center work with Salesforce Classic?
- No, DevOps Center will be supported in Lightning enabled orgs only.
- Will I be able to deploy changes directly from the DevOps Center?
- Yes, you will be able to configure a “pipeline” of test sandboxes and production orgs and manage deployments directly from within DevOps Center.
- Does DevOps Center utilize the SourceMember object to track the changes? If so, does it mean that SourceMember is going to be available in sandboxes?
- Yes, the DevOps Center uses the same “source tracking” mechanisms that SFDX uses to track changes. In Summer ‘20, this Source Tracking feature using Source Member object is available in Sandboxes as an open beta, please see https://releasenotes.docs.salesforce.com/en-us/summer20/release-notes/rn_sandboxes_source_tracking.htm.
- What happens if multiple users are making changes in the same sandbox and I pull changes from the sandbox via the DevOps Center? Do all changes get pulled, or just the ones I made?
- We recommend that each developer use their own development sandbox, but understand that some teams do share sandboxes. In this case, the tool will pull all changes that were made since the last time you pulled changes, regardless of who made the change. There is a field in the UI that shows who made the last change to the component, so you can use that to determine if you want to include/migrate each component based on that.
- Does DevOps Center support development with Scratch Orgs or 2nd Generation Packaging?
- The first release of DevOps Center will be targeted at an “org-based development model”, where development is typically done in Developer Sandboxes, and arbitrary sets of changes are moved from one environment to the next. In a subsequent release, we will also support a “package-based development model”, where development is done in Scratch Orgs, and source is packaged into modularized and independent “Packages” which are then installed into downstream environments. All this said, if you have Scratch Orgs where you’re doing your development, you can in fact connect them to DevOps Center to use as your development environment, even in the first release.
- My company has a policy that prevents developers from having production org access. Will DevOps Center be an option for us, or does it require production org access?
- Your developers will need to have a user in the org where DevOps Center will be installed. However, this user only needs at minimum a Free Limited Access or Identity Only license which will restrict them from having access to any production data or making any configuration changes to the org. This is the same model as is used with Salesforce DX.
- Will DevOps Center be supported in Gov Cloud?
DevOps Center has been validated to be interoperable with Gov Cloud Plus. Please note tha t turning on DevOps Center in Government Cloud Plus orgs can send data outside the authorization boundary. See: https://help.salesforce.com/s/articleView?id=000384503&type=1.
Horizontal Rule
Reference: Forward-Looking Statement
Salesforce Platform Development (Dev Tools + DevOps + SFDX) FY21 FCD (Draft).png
Horizontal Rule