License requirements:
Your team needs an Automation Platform Enterprise license.
Release schedules are only available on team-shared pipelines.
Release schedules let pipeline owners define which days and times releases should be deployed to production, giving your team a consistent, recurring weekly cadence.
Defining your release schedule
To set up a release schedule, open your pipeline settings (Settings cog → Edit pipeline settings) and navigate to the Releases tab.
Toggle on Use a release schedule and configure two things:
Days to release - select which days of the week you want to release (Sunday through Saturday). You can pick as many days as you need.
Time to release - choose what time on each of those days the release should be deployed, shown in your local timezone.
Releases happen every week on the days and times you've selected. There's no option to set a different cadence (e.g. fortnightly or monthly), the schedule repeats weekly.
In the example above, the pipeline is configured to release at 9:00 PM on Mondays and Wednesdays. The next scheduled release is shown at the bottom of the panel.
How scheduling works when creating a release
When a user creates a new release in the pipeline (this requires the Create and add to releases permission), Gearset automatically schedules the deployment for the next time in your release schedule.
For example, if your schedule is set to Monday and Wednesday at 9:00 PM, and someone creates a release on a Tuesday afternoon, Gearset will schedule the deployment for Wednesday at 9:00 PM.
The scheduled date and time are pre-populated from your release schedule, so there's no manual step to get the timing right. Note that the release won't be deployed if it fails validation, has merge conflicts with the environment branch, or has incomplete pre-deployment steps.
How release schedules interact with permissions
Release schedules are enforced differently depending on a user's permissions on the target environment:
| Validate or lower | Run or higher |
Override scheduled deployment time | No - the deployment will always happen at the next scheduled time | Yes - can choose a different time or deploy immediately |
Create a new release when one is already scheduled | No - must wait until the existing scheduled release has been deployed | Yes - can create additional releases regardless |
This gives pipeline owners a way to enforce a consistent release cadence for most of the team, while still giving trusted users the flexibility to deploy outside the schedule when needed.
Release schedules and release candidates
If you're using release candidates, your release schedule also applies to the release candidate environment. When a user creates a release candidate, Gearset will schedule its deployment using the same days and times configured in your release schedule.
However, when a release candidate is propagated to the final environment, the resulting release is not automatically scheduled for deployment. This is deliberate - it gives your team time to do final checks and testing in the release candidate environment before committing to a production deployment time.