With Gearset’s clone package feature, you can promote successful changes to the next environment in your release pipeline. While this was, and still is, a huge time-saver, if you wanted to migrate changes from multiple deployments, you’d have to clone each in turn, or start from scratch with a fresh comparison.

To eliminate this and keep up the speed of your release cycle, Gearset allows you to combine multiple deployments into one package.

To get started, head to the Deployment history page. Choose which deployments you’d like to combine by selecting the checkboxes in the left-hand column, then click Combine packages… at the bottom of the page.

The resulting dialog lets you review and confirm the deployments you’re combining, and choose the source and target environments for the combined deployment you can select from both Salesforce orgs and version control.

Before you kick off the comparison, in the Metadata filter tab, you can choose from one of the two options:

Once you've run the comparison, the items from each combined deployment will be pre-selected for you in the new comparison results grid.

From this point, the deployment behaves like any other in Gearset. You can:

• Add or remove items from the deployment

• Refresh the comparison

• Save a draft

• Continue to validation or deployment

All without needing to repeat the steps for each original deployment

To find out more about how Gearset determines which metadata items are selected, please refer to this guide:

Which metadata differences are the same between different Gearset comparisons

Remember, Gearset's clone deployment works by running a fresh comparison, so you don't run the risk of overwriting changes.

• Gearset runs a new comparison between your selected source and target

• It automatically pre-selects components by name based on what was deployed in the selected past deployments

• You’ll then see up-to-date comparison results and can review each change before deployment

Only the list of item names is carried over from the combined packages. The actual XML metadata is pulled from the current source environment, ensuring your deployment is accurate and up to date.

This feature works for Salesforce orgs authenticated via any of the available "Connection type":