Now that a release branch has been created, this article covers how to view the contents of the release and, if a release environment is configured, how to validate and deploy it before moving to production.
Viewing the open release
Selecting your release name and opening the Details tab provides a summary of everything included in the release. This is where the release manager can confirm exactly what is moving forward before any deployment takes place:
The features included in this release
Linked Jira, ADO or Salesforce tickets
All changed components
Deploying to the release environment (if configured)
If a Release & Testing environment has been configured, the release must be successfully deployed there before a PR can be opened against main. Selecting the name of the release environment allows you to:
Review features, changes and tickets
Run and/or view validation results
Once satisfied, select Deploy release to deploy the release branch to your release environment. A record of the deployment will be available in the Deployment History tab (this is also available in your CI job history).
Gearset also uses Delta CI, if enabled, to deploy only the net new changes in the current release, rather than redeploying the entire branch.
Once you have viewed the release and, if applicable, validated and deployed it to your release environment, the next step is to deploy it to production.