CommunityDevOps ExchangePartners
Articles
5/13/2020
10 minutes

Why Change Sets Suck (the Time out of your DevOps Process) – Part 1

Written by
Jen Nelson
Table of contents

Hello, #AwesomeAdmins! 

In our last gathering, Copado Continuous Delivery for #AwesomeAdmins, I shared how perturbed I was when I finally realized, after 15 years of being an #AwesomeAdmin, that we are a big part of the DevOps Process.

What I did not tell you is that another consternation I have is that I spent endless nights, weekends and holidays doing Deployments the old-fashioned way, using native Change Sets.

For approximately 10 years, I suffered through 2- and 3-day Deployments which primarily leveraged native Change Sets, and uber-detailed SmartSheets to track all of my additional Deployment Steps which couldn’t be addressed via native Change Sets.  

I got stopped with Code Coverage issues, Merge Conflicts, poor Code and Configuration Quality, you name it.

To make matters even more frustrating, I had to rebuild my Change Sets for every move between my Sandboxes and on up to Production.

There are many limitations to native Change Sets, and Copado resolves all of them!

In Part 1 of our 3-Part Series, we will look at Version Control, Release Pipelines and Cross-Salesforce Stack Deployment capabilities.

Native Change Sets have NO Version Control

Without Version Control, there is no ability to:

  • Have a unified Branching Strategy and Release Workstream
  • Have Overlap Awareness when a discreet Metadata Component is being worked upon in multiple lower Environments
  • Have a unified Merge Process, for example, if 3 lower-level Dev Sandboxes are all deployed up to a common UAT Sandbox
  • Resolve Merge Conflicts
  • Sync Metadata changes across Environments to minimize overwrites and conflicts on Work-in-Progress
  • Traceability of Metadata Changes back to Technical and Functional Requirements
  • Package once; deploy many (Every time that you wish to Deploy Metadata from one Salesforce Environment to another with native Change Sets, a new Change Set must be built, by hand, from scratch. Inbound Change Sets cannot be Cloned to create Outbound Change Sets.)
  • Backup Metadata for Work-in-Progress
  • Backup Metadata Pre- and/or Post-Deployment
  • Regularly schedule Metadata Backups
  • Perform an Org-to-Org Compare and Deploy
  • Perform a Rollback
  • Deploy Destructive Changes (You know all of those old Workflow Rules that you have consolidated into clean Process Builders and wish to now delete so that they are no longer used by anyone?  Validation Rules that no longer apply? Legacy Custom Fields with “OLD” and “Do Not Use” in the Label? With native Change Sets, you cannot Deploy the deletion of all those old Workflow Rules, Validation Rules or Fields…you have to manually delete them in every Salesforce Environment, one-by-one)

Deploy Full Profiles and Permission Sets (All that work that you have done to clean up your old Profiles and Permission Sets, maybe even take away a chunk of Permissions that you didn’t realize your Users had, and even add a few new Profiles and Permission Sets to address your current Policies.  There is no way, with native Change Sets to Deploy a full Profile nor a full Permission Set.)

Copado Git Integration for Version Control

Out-of-the-box, Copado allows integration with any Git Provider (common examples are GitHub, GitLab, BitBucket, Azure Repos) for seamless, under-the-hood Version Control that does not require Command-Line experience:

  • Have a unified Branching Strategy and Release Workstream
  • Copado employs a unified Branching Strategy that supports multiple workstreams
  • Have Overlap Awareness when a discreet Metadata Component is being worked upon in multiple lower Environments
  • Copado has User Story Overlap Awareness to allow identification Potential Conflicts before they create a problem and Pull Requests to proactively address Potential Conflicts
  • Have a unified Merge Process, for example, if 3 lower-level Dev Sandboxes are all deployed up to a common UAT Sandbox
  • Copado out-of-the-box will merge User Story Feature Branches in ascending order by the auto-numbered User Story Reference field and Copado also allows Override of the User Story Promotion Merge Order
  • Resolve Merge Conflicts
  • Copado includes multiple options for resolving Merge Conflicts, including Auto-Resolution, Online Conflict Resolution with a Merge Conflict Resolution Panel, and Smart Conflict Resolution  
  • Sync Metadata changes across Environments to minimize overwrites and conflicts on Work-in-Progress
  • Copado not only forward Deploys Metadata Changes, Copado also includes Back Promotion and Mass Back Promotion (no more Sandbox Refreshes!)
  • Traceability of Metadata Changes back to Technical and Functional Requirements
  • Copado’s User Story-centric model, where all Commits contribute to the User Story Feature Branch in Git, allows full traceability of Metadata Changes Committed and Deployed back to the source Technical and Functional Specifications/Requirements prescribed in the User Story
  • Package once; deploy many
  • The combination of Copado’s Git Integration, Branching Strategy and User Story-centric Model allows us to commit our Metadata Changes to discrete User Story Feature Branches once and then Promote and Deploy many times as we move up our Release Pipeline
  • Backup Metadata for Work-in-Progress
  • Copado allows multiple Commits on a single User Story so that, as an example, if our Metadata Changes for a particular User Story has complexity or spans multiple Work Days, we can Commit the new Metadata Changes and add Recommits as appropriate to update our User Story Feature Branch until we complete all Metadata Changes prescribed in the User Story
  • Backup Metadata Pre- and/or Post-Deployment
  • Copado includes a wide array of Deployment Steps including a Webhook URL Callout and one example documented in our Webhook Library is a Git Snapshot
  • Regularly schedule Metadata Backups
  • Copado’s Git Snapshot can also perform an on-demand Snapshot from any Org Credential and can also be scheduled to run on a Daily, Weekly or Monthly frequency
  • Perform an Org-to-Org Compare and Deploy
  • Copado includes both Org Differences and Git Snapshot Differences for Compare and Deploy
  • Perform a Rollback
  • There is no such thing as a Rollback in any system; however, by following Copado’s Best Practices and leveraging regularly scheduled Git Snapshot and/or Git Snapshots via a Pre- or Post-Deployment Step for Webhook URL Callout, you can seamlessly follow Copado’s guidelines for performing a Rollback
  • Deploy Destructive Changes (You know all of those old Workflow Rules that you have consolidated into clean Process Builders and wish to now delete so that they are no longer used by anyone?  Validation Rules that no longer apply? Legacy Custom Fields with “OLD” and “Do Not Use” in the Label? With native Change Sets, you cannot Deploy the deletion of all those old Workflow Rules, Validation Rules or Fields…you have to manually delete them in every Salesforce Environment, one-by-one)
  • Copado includes Destructive Changes amongst the types of Commit Git Operations that can be added to a User Story
  • Deploy Full Profiles and Permission Sets (All that work that you have done to clean up your old Profiles and Permission Sets, maybe even take away a chunk of Permissions that you didn’t realize your Users had, and even add a few new Profiles and Permission Sets to address your current Policies.  There is no way, with native Change Sets to Deploy a full Profile nor a full Permission Set.)
  • Copado includes Full Profiles and Permission Sets amongst the types of Commit Git Operations that can be added to a User Story
  • Additional documentation on Full Profiles and Permission Sets Commit Behavior

Native Deployment Settings do NOT allow Deployment Connections across Salesforce Stacks and do NOT allow Deployment Sequencing

Native Deployment Settings define the Deployment Connections across which our natitve Change Sets are permitted to move amongst Salesforce Environments.

Native Deployment Connections are limited to a single Salesforce Stack.

This means that a Company with, say three (3) Salesforce Production Orgs, must define Deployment Connections amongst the Sandboxes and Production Org of each individual Salesforce Production Org:

In Salesforce Production Org A (“Stack A”)

  • Sandbox Dev 1A → Integration Sandbox A
  • Sandbox Dev 2A → Integration Sandbox A
  • Sandbox Dev 1A ←→ Sandbox Dev 2A
  • Integration Sandbox A → UAT Sandbox A
  • UAT Sandbox A → Production Org A

In Salesforce Production Org B (“Stack B”)

  • Sandbox Dev 1B → UAT Sandbox B
  • Sandbox Dev 2B → UAT Sandbox B
  • Sandbox Dev 3B → UAT Sandbox B
  • Sandbox Dev 1B ←→ Sandbox Dev 2B
  • Sandbox Dev 2B ←→ Sandbox Dev 3B
  • Sandbox Dev 1B ←→ Sandbox Dev 3B
  • UAT Sandbox B → Production Org B
  • Hotfix Sandbox B → Production Org B

In Salesforce Production Org C (“Stack C”)

  • Sandbox Dev 1C → UAT Sandbox C
  • UAT Sandbox C → Production Org C

There is no ability to perform cross-Stack Deployments (say from Production Org A to Production Org B) and there is also no ability to incorporate a Common-Code Environment, whether a Sandbox, Production Org or Developer Org, to Deploy Metadata Components that are common across all 3 Stacks.  Furthermore, within a single Stack, although we can limit Inbound and Outbound Connections between Environments, there is no ability to define nor enforce Sequencing amongst the native Deployment Connections.

Copado OAuth Authentication, Git Integration and Release Pipelines

Copado leverages native OAuth Authentication to Connect Any Salesforce Environment to Copado

Any Salesforce Environment (Developer Sandbox, DevPro Sandbox, PartialCopy Sandbox, FullCopy Sandbox, Dx Scratch Org, Developer Edition Org or Production Org) can be connected to Copado with native OAuth Authentication against one or more Users’ native Org Credentials.

Copado allows any combination of Salesforce Environments in a single Release Pipeline

Any Release Pipeline built in Copado can include any combination desired of Salesforce Environments (Developer Sandboxes, DevPro Sandboxes, PartialCopy Sandboxes, FullCopy Sandboxes, Dx Scratch Orgs, Developer Edition Orgs and/or Production Orgs).

Copado requires every Pipeline to have a dedicated Git Repository and a Git Environment Branch for each Salesforce Environment in the Pipeline

In order to ensure Version Control throughout the Copado Pipelines, it is necessary that each Pipeline in Copado has a dedicated Git Repository and every Salesforce Environment in a Pipeline has a corresponding Git Environment Branch.

Copado allows Sequencing of Salesforce Environments in a single Release Pipeline

Copado’s Pipeline Connections allow discreet sequencing of the Pipeline’s Salesforce Environments in order to enforce a unified Release workstream.

Copado allows the orchestration of multiple Release Pipelines from a single installation of Copado

Copado should always be installed and formally executed from a Production-quality Salesforce Organization (Enterprise Edition or higher).  This is for both licensing requirements and speed/performance. 

Since Copado leverages OAuth to Connect Salesforce Environments, and Git for Version Control, a single Production-installation of Copado can orchestrate multiple Release Pipelines to support your DevOps Workstreams.

Summary

Native Change Sets Limitations Addressed by Copado

Native Change Sets only cover a single-step in a Complete DevOps Process.

Create–>Test–>Deploy–>Release–>Monitor–>Plan

Native Change Sets have no Version Control.

Native Change Sets do not allow for any Release Pipeline structure nor cross-Stack Deployments.

Copado covers the end-to-end DevOps Process and is 100% native to Salesforce.

Create–>Test–>Deploy–>Release–>Monitor–>Plan 

Stay tuned for Part 2 of our 3-Part Series which will cover:

  • Standard Components, Standard Settings and Custom Settings
  • Quality Gates to ensure that the Metadata being Deployed is of high quality and is compliant

Want to learn more about Copado?

Here’s some additional Resources for all my #AwesomeAdmin Ohana:

Want to join the Team?

Book a demo

About The Author

Director, Product Enablement

Jen Nelson is a 20-year veteran of the Salesforce ecosystem, a current Salesforce MVP Hall of Fame member and has 30+ years experience in DevOps. Jen has been with Copado for 4 years and is the Director of Product Technical Enablement.

Copado Launches Copado Explorer to Simplify and Streamline Testing on Salesforce
Exploring Top Cloud Automation Testing Tools
Master Salesforce DevOps with Copado Robotic Testing
Exploratory Testing vs. Automated Testing: Finding the Right Balance
A Guide to Salesforce Source Control
A Guide to DevOps Branching Strategies
Family Time vs. Mobile App Release Days: Can Test Automation Help Us Have Both?
How to Resolve Salesforce Merge Conflicts: A Guide
Copado Expands Beta Access to CopadoGPT for All Customers, Revolutionizing SaaS DevOps with AI
Is Mobile Test Automation Unnecessarily Hard? A Guide to Simplify Mobile Test Automation
From Silos to Streamlined Development: Tarun’s Tale of DevOps Success
Simplified Scaling: 10 Ways to Grow Your Salesforce Development Practice
What is Salesforce Incident Management?
What Is Automated Salesforce Testing? Choosing the Right Automation Tool for Salesforce
Copado Appoints Seasoned Sales Executive Bob Grewal to Chief Revenue Officer
Business Benefits of DevOps: A Guide
Copado Brings Generative AI to Its DevOps Platform to Improve Software Development for Enterprise SaaS
Celebrating 10 Years of Copado: A Decade of DevOps Evolution and Growth
Copado Celebrates 10 Years of DevOps for Enterprise SaaS Solutions
5 Reasons Why Copado = Less Divorces for Developers
What is DevOps? Build a Successful DevOps Ecosystem with Copado’s Best Practices
Scaling App Development While Meeting Security Standards
5 Data Deploy Features You Don’t Want to Miss
Top 5 Reasons I Choose Copado for Salesforce Development
How to Elevate Customer Experiences with Automated Testing
Getting Started With Value Stream Maps
Copado and nCino Partner to Provide Proven DevOps Tools for Financial Institutions
Unlocking Success with Copado: Mission-Critical Tools for Developers
How Automated Testing Enables DevOps Efficiency
How to Keep Salesforce Sandboxes in Sync
How to Switch from Manual to Automated Testing with Robotic Testing
Best Practices to Prevent Merge Conflicts with Copado 1 Platform
Software Bugs: The Three Causes of Programming Errors
How Does Copado Solve Release Readiness Roadblocks?
Why I Choose Copado Robotic Testing for my Test Automation
How to schedule a Function and Job Template in DevOps: A Step-by-Step Guide
Delivering Quality nCino Experiences with Automated Deployments and Testing
Best Practices Matter for Accelerated Salesforce Release Management
Maximize Your Code Quality, Security and performance with Copado Salesforce Code Analyzer
Upgrade Your Test Automation Game: The Benefits of Switching from Selenium to a More Advanced Platform
Three Takeaways From Copa Community Day
Cloud Native Applications: 5 Characteristics to Look for in the Right Tools
Using Salesforce nCino Architecture for Best Testing Results
How To Develop A Salesforce Testing Strategy For Your Enterprise
What Is Multi Cloud: Key Use Cases and Benefits for Enterprise Settings
5 Steps to Building a Salesforce Center of Excellence for Government Agencies
Salesforce UI testing: Benefits to Staying on Top of Updates
Benefits of UI Test Automation and Why You Should Care
Types of Salesforce Testing and When To Use Them
Copado + DataColada: Enabling CI/CD for Developers Across APAC
What is Salesforce API Testing and It Why Should Be Automated
Machine Learning Models: Adapting Data Patterns With Copado For AI Test Automation
Automated Testing Benefits: The Case For As Little Manual Testing As Possible
Beyond Selenium: Low Code Testing To Maximize Speed and Quality
UI Testing Best Practices: From Implementation to Automation
How Agile Test Automation Helps You Develop Better and Faster
Salesforce Test Cases: Knowing When to Test
DevOps Quality Assurance: Major Pitfalls and Challenges
11 Characteristics of Advanced Persistent Threats (APTs) That Set Them Apart
7 Key Compliance Regulations Relating to Data Storage
7 Ways Digital Transformation Consulting Revolutionizes Your Business
6 Top Cloud Security Trends
API Management Best Practices
Applying a Zero Trust Infrastructure in Kubernetes
Building a Data Pipeline Architecture Based on Best Practices Brings the Biggest Rewards
CI/CD Methodology vs. CI/CD Mentality: How to Meet Your Workflow Goals
DevOps to DevSecOps: How to Build Security into the Development Lifecycle
DevSecOps vs Agile: It’s Not Either/Or
How to Create a Digital Transformation Roadmap to Success
Infrastructure As Code: Overcome the Barriers to Effective Network Automation
Leveraging Compliance Automation Tools to Mitigate Risk
Moving Forward with These CI/CD Best Practices
Top 3 Data Compliance Challenges of Tomorrow and the Solutions You Need Today
Top 6 Cloud Security Management Policies and Procedures to Protect Your Business
What are the Benefits of Principle of Least Privilege (POLP) for My Organization?
You Can’t Measure What You Can’t See: Getting to know the 4 Metrics of Software Delivery Performance
How the Public Sector Can Continue to Accelerate Modernization
Building an Automated Test Framework to Streamline Deployments
How To Implement a Compliance Testing Methodology To Exceed Your Objectives
Cloud Security: Advantages and Disadvantages to Accessibility
Copado Collaborates with IBM to Accelerate Digital Transformation Projects on the Salesforce Platform
Continuous Quality: The missing link to DevOps maturity
Why Empowering Your Salesforce CoE is Essential for Maximizing ROI
Value Stream Management: The Future of DevOps at Scale is Here
Is Salesforce Development ‘One Size Fits All?’
The 3 Pillars of DevOps Value Stream Management
Gartner Recommends Companies Adopt Value Stream Delivery Platforms To Scale DevOps
The Admin's Quick Glossary for Understanding Salesforce DevOps
Top 10 Copado Features for #AwesomeAdmins
10 Secrets Management Tools to Facilitate Stronger Security Practices
5 Cloud Security Compliance Basics to Prevent Data Breaches
5 Data Security Management Fundamentals
Cloud Agnostic vs Cloud Native: Developing a Hybrid Approach
Making DIE Model Security vs. the CIA Security Triad Complementary, Not Competitive
The CI/CD Pipeline: Why Testing Is Required at Every Stage
DevSecOps Roadmap: From Architecture to Automation
Pets vs. Cattle: More Than an Analogy for Modern Infrastructures
Data Compliance Solutions Provide Greater Control Over Enterprise Data
Copado Cares: Free Training, Collaboration and Product Access for Global Response to COVID-19
12 Types of Social Engineering Attacks to Look Out For
Go back to resources
There is no previous posts
Go back to resources
There is no next posts
Ready to Transform Your Software Delivery Process?

Explore more about

No items found.