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

How to track application changes

Tracking application changes without a version control system is like finding a needle in a haystack. We have seen how to use GitLab to track application changes in Chapter 5, Version Control. Whenever bugs are reported by testers, we use a bug tracker such as Bugzilla to track the life cycle of a bug—from identifying it until the fix is released to production. When a new bug or feature is added to the bug tracker, it is assigned to a developer and the developer starts working on that fix or new feature. Code changes are tracked in Git repositories when developers commit changes to the respective feature branch. The develop branch commit message should contain the bug ID to identify the changes done with respect to a particular bug or feature.


If a new feature is added or an issue is fixed, developers can add meaningful commit messages to help us track changes for a new functionality. When we want to merge changes to develop a branch or perform cherry-picks...