Book Image

DevOps for Salesforce

By : Priyanka Dive, Nagraj Gornalli
Book Image

DevOps for Salesforce

By: Priyanka Dive, Nagraj Gornalli

Overview of this book

Salesforce is one of the top CRM tools used these days, and with its immense functionalities and features, it eases the functioning of an enterprise in various areas of sales, marketing, and finance, among others. Deploying Salesforce applications is a tricky event, and it can get quite taxing for admins and consultants. This book addresses all the problems that you might encounter while trying to deploy your applications and shows you how to resort to DevOps to take these challenges head on. Beginning with an overview of the development and delivery process of a Salesforce app, DevOps for Salesforce covers various types of sandboxing and helps you understand when to choose which type. You will then see how different it is to deploy with Salesforce as compared to deploying with another app. You will learn how to leverage a migration tool and automate deployment using the latest and most popular tools in the ecosystem. This book explores topics such as version control and DevOps techniques such as Continuous Integration, Continuous Delivery, and testing. Finally, the book will conclude by showing you how to track bugs in your application changes using monitoring tools and how to quantify your productivity and ROI. By the end of the book, you will have acquired skills to create, test, and effectively deploy your applications by leveraging the features of DevOps.
Table of Contents (14 chapters)
Title Page
Packt Upsell

What the Migration Tool is?

The Migration Tool provides a scripted way to deploy or retrieve metadata to and from a Salesforce sandbox. It is based on Ant/Java.

The Migration Tool helps us to copy Salesforce components from one organization easily. In normal practice, we have different environments such as development, test, UAT, and production. As developers develop components in a Developer sandbox, they need to move those changes to test or UAT for testers to test and give the green light for a feature/change to production. However, this is not a one-time process. Often, features or changes do not work properly or they introduce some bugs, testers raise an issue/bug, and developers start working on them. Once the bug/issue is fixed in the development environment, we need deployment of the change to test/UAT again. So, this is a repetitive process due to many reasons. Doing this deployment using a change set every time is not a convenient option, hence we need...