- DevOps for Salesforce
- Priyanka Dive Nagraj Gornalli
- 159字
- 2021-07-16 17:38:53
Issues with traditional deployment
No versioning is provided in a sandbox environment, so it becomes difficult when multiple developers are working on a project and are not in sync. Keeping track of all changes in project can look like finding a needle in a haystack. Deployment with a change set is not recommended for large projects and creating a change set is not scriptable. So it becomes a repetitive task.
The Force.com Migration Tool is good for large projects, but we do not have versioning, so we cannot revert code to its previous version. Also, we are not able to track changes done by developers.
We have different environments, such as development, test, stage, and production, in almost all technical stacks. In Salesforce, we use a sandbox for development and test environments. Sandboxes come in different types as per our requirement, and we can choose which sandbox to use. Let's look at the different types of sandboxes.
- Mastering Proxmox(Third Edition)
- Dreamweaver CS3網(wǎng)頁制作融會貫通
- 實時流計算系統(tǒng)設(shè)計與實現(xiàn)
- 程序設(shè)計缺陷分析與實踐
- 21天學(xué)通C++
- 21天學(xué)通ASP.NET
- 最后一個人類
- 永磁同步電動機變頻調(diào)速系統(tǒng)及其控制(第2版)
- 21天學(xué)通Java
- Windows 7寶典
- Windows環(huán)境下32位匯編語言程序設(shè)計
- Machine Learning with Apache Spark Quick Start Guide
- 分?jǐn)?shù)階系統(tǒng)分析與控制研究
- Pentaho Analytics for MongoDB
- SQL Server數(shù)據(jù)庫應(yīng)用基礎(chǔ)(第2版)