After a release branch is created, Gearset automatically runs a validation on the testing org linked in the Release & Testing stage (if applicable) giving early warnings about potential failures.
Viewing the open release
If you click on the release name, users can view:
The features included in this release
Linked Jira/ADO issues
All changed components
If a static environment is configured for this stage, you must deploy the release to this org before creating the PR against main.
Deploying to the release testing org (if applicable)
By clicking the name of the static environment, you can:
View validation results
Review features and commits
Confirm linked work items
Once satisfied, select Deploy release to deploy the release branch to your testing org. You will see a record of that deployment in the Deployment history tab.
💡The source branch of the CI job is automatically updated when a new release is created, so that the promotion history is preserved between releases.
Gearset continues to use Delta CI, if enabled, to deploy only the net-new changes in current release instead of redeploying the entire branch.
In the next article you can read about deploying a release to the production.