Skip to main content

Schedule and automatically tag a release or release candidate (expanded branching model)

Learn how to schedule a release or release candidate and understand automatic tagging

Written by Jacob Joshua

💡Scheduling applies to both releases and release candidates. When a release candidate is promoted to the final environment, it appears as a release and follows the release workflow from that point.

Schedule a release or release candidate when you want Gearset to promote the package automatically at a specific date and time. You can configure a regular release cadence or schedule a release when you create it or at any time afterward.

Configure a regular release cadence

To configure a recurring release schedule:

  1. Select the pipeline’s Settings cog.

  2. Select Edit pipeline settings.

  3. Open the Releases tab.

  4. Configure the release schedule.

You can also configure the default release pull-request naming format from the same settings tab.

Schedule during release or release candidate creation

When creating a release or release candidate:

  1. Select the features you want to include.

  2. Enter a name for the package.

  3. Choose the option to schedule its deployment.

  4. Select the date and time.

  5. Create the release or release candidate.

The scheduled deployment details appear with the package in the Releases or Release candidates tab.

Schedule an existing release or release candidate

  1. Open Releases or Release candidates in the appropriate pipeline environment.

  2. Select the package.

  3. Open the dropdown menu and select Schedule deployment.

  4. Choose the deployment date and time.

  5. Save the schedule.

Gearset automatically starts the promotion at the scheduled time.

You can continue adding features before the scheduled deployment. Gearset validates the updated package again after the additional features are merged.

Why wasn’t my scheduled release deployed?

A scheduled release won’t be deployed if:

  • Its validation has failed.

  • It has merge conflicts with the environment branch.

  • Its pre-deployment steps are incomplete.

  • The target environment is blocked.

If the environment is blocked, Gearset postpones the deployment for five minutes and retries when the environment becomes available. If the deployment starts but fails, Gearset displays an error for you to investigate.

Automatic release tagging

Gearset automatically tags releases using the release name. This makes releases easier to find in your repository and helps you:

  • Identify changes that have been merged into main or master but haven’t yet been deployed.

  • Review everything included in a previous release.

A release created by promoting a release candidate follows the same release-tagging behaviour when it is deployed.

Related Articles
Did this answer your question?