Releases in ReleaseOps
Scheduled and on-demand releases are how changes are deployed to target instances with ReleaseOps. Releases can contain one or more deployment requests.
Creating a release
Generally, a release manager is responsible for creating releases and mapping a team or organization’s release workflows to a release cadence.
There can be a single release stream or multiple release streams available at any given time. However, only one release can be in the process of deploying to a target instance at any time.
- A regular weekly cadence for Releases, at 10:00 each Friday.
- A daily cadence for high-priority Releases, at 12:00 each day.
For more information about creating a release, see Create a release.
Release types
Releases that are planned and scheduled in advance are considered scheduled releases. These releases can consist of one or more deployment requests. Each deployment request in the release can include of one or more update sets.
On-demand releases are created dynamically when the need arises, such as deploying changes to patch a defect in an application. When a developer creates a deployment request and selects the option for an on-demand release, ReleaseOps dynamically creates a release to drive this request to its target instance. As a result, only one deployment request can be attached to an on-demand release.
ReleaseOps includes deployment analyzer, a tool provided to introspect a deployment. The deployment analyzer enables release administrators to verify that on-demand releases meet certain criteria, such as only making specific types of code changes. For more information, see Deployment analyzer in ReleaseOps.