Releases

Releases are either created automatically during the import process or manually from the  Releases search view. Releases can also be created by Jenkins if you launch the import process externally.

Follow the subsequent steps to create a new release manually.

To edit release details, either right-click on it in the  Releases search view then select  Edit, select the item then click the  edit icon or double-click it. The  Release editor is opened where all of the entity's details are managed.

The information that defines releases can be edited at any time by users with the rights to do so.

Application

A static field that displays the release's parent application.

Release Number

If a release was created automatically, the release number is automatically populated following the template defined in the Release Number Template field in the parent application.

Change the value in this field to modify the release number.

Note

The release number must be unique for the application.

Release Description

Manually enter a description for an existing release to easily identify it in the Release view and the deployment process.

Note

If you change the description of an release in Jenkins, this field will be updated.

Status

Select a status for the release that will enable users to easily recognize how or when to use it in the import and deployment processes.

Closed releases cannot be deployed.

The list is prepopulated with the statuses defined in the Preferences menu.

Reference

For more information about defining release statuses, refer to Defining release statuses.

Release Dates

This section displays the static dates that the release was created and closed. These fields cannot be modified. When the Closed checkbox is ticked, the Closed date is updated.

Important!

The CLO status for releases is not to be confused with the Closed checkbox in the release editor. The status must be updated manually and does not have a functional effect on the release or its ability to be deployed. It is only for information.

Note

Closed releases can not be imported or deployed.

If a release has been deployed, all of the target environments to which it was delivered, and the corresponding delivery dates, are displayed in the  Receiver Environments tab in the  Release editor.

Use the  Comment tab in the  Release editor to enter any details that users should be aware of when using the release to import or deploy content.

Attachments can be automatically added to releases if an import strategy includes this action. The strategy defines which files can be saved as attachments. View any attachments added during the import process from the  Attachments tab in the  Release editor.

Double-click on an attachment or select it and click the  Open button to open it in a new tab in the studio.

Download an attachment by selecting it and clicking the  Save button.

If the release was associated with a workitem, a link to the JIRA issue is included in the Workitem tab. Click the link to open the issue in your default explorer. The list of workitems in releases is populated automatically when the import process is launched.

Locked releases cannot be used to import artifacts.

To lock or unlock a release and prevent users from using it to import artifacts, either right-click on it in the  Releases search view then select  Lock/ Unlock or select the item then click the corresponding icon.

To view the artifacts imported in a release, either right-click on it in the  Releases search view then select  Show Artifacts or select the item then click the artifacts icon.

Search for the artifacts in a release in the  Release Artifact view by name, file type (Extension) or Component. To display the complete list of artifacts imported into the current release, click the Search button without entering any search criteria.

Imported artifacts are nested under their corresponding  components' node and found in their source directory structure. Select an artifact and either right-click, then select  Show History, or click the  Show the release history icon to open the artifact History view.

This view displays when the artifact was added (its first release), and when it was modified (imported in other releases).

Archiving the artifacts from closed or outdated releases creates space on the DROPS Server and cleans up the artifact repository. The history of each release is maintained and the name(s) of the imported artifacts can still be found, but the artifacts themselves no longer appear in the repository.

To delete a release, search for it in the  Release search view. Either right-click on it, then select  Delete or select it, then click the  delete icon. Click OK to confirm or click Cancel to keep the release.