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

Publishing a build report to Git

As we have seen in Chapter 6, Continuous Integration, we can trigger a Jenkins job as code is pushed to Jenkins using a Git Webhook. Jenkins will start the build using the Ant Migration Tool and deploy metadata to the sandbox. However, whether the build failed or is successful is not shown anywhere. So we need to change the Jenkins job to deploy changes from Git to the sandbox. Go to the Jenkins job that you want to change and click on Configure.

Add the post-build Git Publisher step to set the build status to Git commit:

In GitLab, you can view the status of the Jenkins job to check whether is successful or it failed. We can track each commit in Git and see if the deployment to the sandbox step build has passed. If we configure the Jenkins job to run automation test cases after deployment is done in testing the sandbox, we can get the status of the execution of automation test cases in Git: