Express Deploy is designed to be a simpler, faster way to move your changes with Gearset. We’re releasing this as an experimental pilot to gather feedback that we’ll use to plan our next stages of development.
This is a more concentrated version of our Compare & Deploy tool, allowing you to deploy your changes more efficiently and giving you more time to focus on your development rather than the deployments. No filters to deal with here - just hop straight into a comparison and choose the items you want to deploy.
We’re also moving the Validate and Deploy actions right into the comparison screen so there’s now even fewer steps between comparing and getting a successful deployment. If you've missed a dependency you can add it right from the same screen and validate/deploy again straight away.
How do I get started?
Express deploy can be accessed in Pipelines or via metadata deployments > Compare and deploy.
Compare and deploy
When on the Compare and Deploy you will see the option to deploy using Standard deploy or Express Deploy. No filters to deal with here, just select your source and target and jump straight into a comparison.
Use the dropdown to choose the type you’re looking to deploy, and the input on the right to help you filter down the results. Select the items you want to deploy using the checkboxes on the left. You can view the differences for each item using the View diff button.
From here you can immediately start validating or deploying the items you’ve selected using the Validate and Deploy buttons in the bottom right corner.
If you’d like to review extra details such as the dependency trees for your selections or to customise subcomponent selections, head on over to the Review tab to do so.
Accessing Express deploy via Pipelines
When deploying changes through Pipelines, you can review, compare, and commit updates using either the Standard or Express deployment workflow.
Who is this for?
We believe this will be great for users who perform frequent and small (5 or fewer items) deployments. You don’t want or need to compare everything between your source and target orgs, because you’ve just built it - you know what’s important to compare and can quickly gather those changes for your deployments. The aim is to get you to value faster than ever by keeping comparisons small and focused, fitting into your development and DevOps lifecycle seamlessly.
Feature support
A quick reference of what each workflow supports today. Express Deploy is in open pilot; several items marked ❌ are on the roadmap.
Feature | 🔍 Standard | ⚡ Express |
Problem Analysers | ✓ | ✗ |
Metadata filters (saved & team-shared) | ✓ | ✗ |
Ticket integration (Jira, ADO, Asana) | ✓ | ✗ Jira coming soon |
Vlocity, CPQ, RCA configuration | ✓ | ✗ |
Config Data deployments | ✓ | ✗ |
Managed package metadata | ✓ | ✗ |
Precision selections | ✓ | ✗ |
Workflow metadata type | ✓ | ✗ |
Layered module repositories | ✓ | ✗ |
Configurable API version | ✓ | ✗ |
Subcomponent selection (e.g. custom fields) | ✓ | ✓ |
Sales Cloud metadata | ✓ | ✓ |
In-screen Validate & Deploy | ✓ | ✓ |
We are continuing to improve support for Profiles, Translations and CustomObjectTranslations where you need to select multiple type in your comparison filter.
As always we’re eager to hear your feedback and your experience with our new experimental workflow, so please get in touch via our support chat if you have anything to share.
Need to switch mid-session?
If at any point you feel like you need to go back to Compare and Deploy there's a menu at the top right where you can continue switch to the standard comparison journey in the existing tool - your comparisons and selections will move right over.
What about Compare & Deploy?
With support for features such as Source Tracking, Vlocity, CPQ, and RCA, Compare & Deploy remains our flagship industry leading deployment tool.
Our Express Deploy workflow is an augmentation of Compare & Deploy designed to have a laser focus on a specific use case, sacrificing flexibility for speed and simplicity.
Can I deploy individual subcomponents (such as custom fields) using Express deploy?
Yes it is possible to deploy individual an subcomponent such as custom field using Express deploy. Simply select Custom object and subcomponents, and click the chevron next to the related component to display the subcomponents and select the one that you want to deploy.
