Salesforce DevOps Center: How to Develop and Deploy Faster

Share this article...

At TrailheaDX 2020, we had quite a few announcements about new and upcoming products and features, and the Salesforce DevOps Center was one of them. Here to help Salesforce development teams (working with both clicks and code) to collaborate to deliver faster, it’s the announcement that I am most excited about!

The big difference of using a modern UI is that you no longer have to use ‘change sets’ to move changes between environments, org to org. All you need to do is use a code repository instead. Let me tell you more about what you can do using Salesforce DevOps Center.

“Natterbox"

Track Changes with a Modern UI

Let us consider the DevOps Center as a release management app in which the ‘Work Item’ object is the big player, which holds tickets for changes to be made. The records are key for tracking changes across the development life cycle, and even beyond when they reach production.

Using the friendly path that we all are familiar and comfortable with, we can get a visual representation of the work-in-progress, per Work Item record.

From here, you can launch a development environment, in which you can incorporate changes. This environment is to be connected to your Source Code Repository and once you are done with it, you can ‘Pull Changes’ with the click of a button.

That’s it! No need to manually track all items that have changed. Likewise, it saves you the trouble of having to go through a long list of potential components, to select the ones that are to be deployed.

Seamless Integration with Version Control

Version control is key, and so is having as a single source of truth.

Version Control makes it easy to collaborate. While you are working on new features and enhancements, you can pull in the most recent version. This may also help you view the progress of others, helping you be in sync with the latest bundle that will be deployed.

Also, let’s not forget the ability to do a peer review, which is also known as code review. This is a practice carried out to reduce bugs, whilst improving quality and internal knowledge.

In addition to these, you avoid overriding each other’s work, and can easily merge everyone’s work to achieve a successful deployment. Aside from this, it also protects the work of all those involved; you, your developers, QAs, release champion, the operations team, end users, customers and the list goes on….

Deployment Based on a Centralised Source of Truth

Though it may sound crazy, your production environment can’t be your source of truth. If something goes wrong there, it could be disastrous for you. Apart from this, in production, there’s no quick and easy way to revert changes or identify the problem at a granular level.

Instead, a repository like GitHub that provides hosting for software development version control by using Git (a distributed version control system which is free and open source), can act as an enabler. It can reduce recovery time and bring down the rate of failure.

Summary

So the big difference of using a modern UI is that you no longer have to use ‘change sets’ to move changes between environments, org to org. All you need to do is use a code repository instead.

Fortunately, with the DevOps Center, it is easier to collaborate using either clicks, code or even both. Developing and delivering collaboratively results in better Salesforce value – full stop!

You can see it in action within the DevOps demos section.

Leave a Reply