Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
DevOps for Salesforce

You're reading from   DevOps for Salesforce Build, test, and streamline data pipelines to simplify development in Salesforce

Arrow left icon
Product type Paperback
Published in Sep 2018
Publisher
ISBN-13 9781788833349
Length 220 pages
Edition 1st Edition
Concepts
Arrow right icon
Authors (3):
Arrow left icon
Mukta Aphale Mukta Aphale
Author Profile Icon Mukta Aphale
Mukta Aphale
Nagraj Gornalli Nagraj Gornalli
Author Profile Icon Nagraj Gornalli
Nagraj Gornalli
Priyanka Dive Priyanka Dive
Author Profile Icon Priyanka Dive
Priyanka Dive
Arrow right icon
View More author details
Toc

Table of Contents (10) Chapters Close

Preface 1. Salesforce Development and Delivery Process 2. Applying DevOps to Salesforce Applications FREE CHAPTER 3. Deployment in Salesforce 4. Introduction to the Force.com Migration Tool 5. Version Control 6. Continuous Integration 7. Continuous Testing 8. Tracking Application Changes and the ROI of Applying DevOps to Salesforce 9. Other Books You May Enjoy

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:

 

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image