Standalone Releases control the deployment of a single project or package. They are used to eliminate the overhead of creating and maintaining a Release with multiple pieces of content.
Standalone Releases are linked directly to a project. Due to this, Standalone Releases can not be viewed within the standard Release Folder Structure. Instead, to view existing Standalone Releases for a project, navigate to the Releases tab on a project’s page.
Unique Standalone Releases
Standalone Releases are unique by the project, package, and branch of their content, not allowing for duplicates. A Standalone Release with matching content can not be created until the existing Standalone Release is completed.
Branch and priority can not be changed once a Standalone Release has been created.
Content can not be added or removed from a Standalone Release.
Creating a Standalone Release
Standalone Releases can be manually made for a project from the project’s Releases tab. Select the 
button in the top right of the table to open the create popup. The project and selected package will automatically be added to the Standalone Release’s content.
Field | Required | Description |
|---|---|---|
Release Name | Yes | The name of the standalone release. |
Pipeline | Yes | The pipeline which is used to process snapshots for the standalone release. (Uses default pipeline from the release settings setup of the Folder containing this Project) |
Description | No | An optional description for the standalone release. |
Package | Yes - If Package-Based Project | Name of package to be added to the standalone release. |
Build Environment | No | If there is only one build environment for project, then this will be defaulted. If no build environment specified and standalone release is setup for Scheduled Build, this project will not be included in Scheduled Build. |
Branch | Yes | The branch used for the project/package. |
Standalone Releases can also be automatically created when submitting a Build Request for a project. This can be done by selecting Create new Standalone Release from the release dropdown in a Build Request popup.
Specify a release name and pipeline. After submitting the build request, a new Standalone Release will be created and the project/package will be added as content. Once the build completes successfully, a Snapshot will be automatically initiated for the new Standalone Release.
To cancel creating a new Standalone Release on a Build Request, click Select Existing Release to bring back the Release dropdown. Existing Standalone Release can be selected from this dropdown. Selected Package and Branch must match the content of a Standalone Release for it to appear in the dropdown.
Promoting Standalone Releases
Along with all other releases, Standalone Releases can be “Promoted” to other releases during a Snapshot execution. Content can be added to other releases for group deployments on other environments by using the Promote Step in the associated Pipeline. For more information, view: