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
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 FREE CHAPTER 2. Applying DevOps to Salesforce Applications 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

What the Force.com Migration Tool is?


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

The Force.com 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...

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