Standalone Releases
- Karl Henselin
- Blake Westmoreland
Standalone releases control the deployment of a single project or package. They are provided to simplify release management when releasing only one item, which may be applicable for emergency releases or to align to feature-driven development agile methodologies.
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 within the project.
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 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 automatically created when submitting a build request for a project, which is the recommended approach. This can be performed by selecting Create new Standalone Release from the release dropdown in the build request form.
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 releases 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.
Standalone releases can also be created manually 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 set on the release settings of the project’s parent folder) |
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 the project, then this will be defaulted. If no build environment is specified and the standalone release is set up for scheduled build, this project will not be included in the scheduled build. |
Branch | Yes | The branch used for building the project/package. |
Promoting Standalone Releases
Along with all other releases, standalone releases can be “Promoted” to other releases during a snapshot execution. Content of the standalone release can be added to other releases for group deployments to higher environments by using the Promote Step in the associated pipeline. This enables a feature-driven development agile methodology. That is, manage individual features through their own independent release lifecycle, each promoting to the master delivery release if/when they are approved for delivery.
For more information, see:
- style