The Definition tab on each release allows for editing basic release details, as well as managing release content (projects/packages) and work items.
Editing Basic Details
To edit basic release information, go to the Definition tab and select the icon on the right side panel.
Field | Description |
---|---|
Name | The name of the release. |
Folder | The folder the release is located in. All security and settings are inherited from this folder, unless overridden. |
Pipeline | The pipeline which is used to process snapshots for the release. The pipeline attached to the release is displayed below the folder path for quick access, and can be updated both from here and from the right side panel. |
Description | An optional description for the release. |
Status | The current status of the release.
|
Snapshot Schedule | A cron expression to initiate the creation of a snapshot on a regular basis, using new project versions for all release projects. Project-level scheduled build triggers are created, which can be viewed from the project triggers screen as well. More than one cron expression can be provided using ; as a separator. This would allow for more complex schedules, but all projects in the release will use the same schedule. For example,
If a project added to the release does not have a build environment selected, then a new build will not be triggered as part of the snapshot creation. The latest project version will be used for that project. When a release is ended, all the scheduled build triggers for each project/package in the release will be deleted. Release Scheduled Build Processing
|
Content (Projects/Packages)
To view all projects and packages in your release, make sure you have the content view selected on the Definition tab.
Adding Content
To add a project or a package to the release, enter the name in the Add Content input field and select the content you want to add. To add multiple projects and packages at once, select the icon at the end of the input field.
Viewing/Editing Content
After adding content to a release, it can be configured from the context menu or actions column at the end of each row. To edit an individual item, open the context menu and select Edit or choose a field to update directly from the menu.
Multiple rows can be updated at once by selecting the rows you want to edit and right clicking on any of the rows, or by pressing the [2] icon above the table.
The table below explains each field displayed in the table and how it is initialized/updated.
Just like other tables in FlexDeploy, displayed columns and ordering can be updated from the table menu. Even though there’s no saved query support, your table settings will be saved for future use and applied to all releases.
Note that the Project Groups column will appear only if the pipeline attached to the release has project group(s) defined, and the CI column will appear only if a snapshot schedule is defined for the release.
Column | Description |
---|---|
Priority | Priority defines the sequence of deployment for the project/package when a release snapshot executes the Deploy All Step.
|
Item | The project and package (if project is package-based). The project/package combination cannot be edited after adding to the release. The project’s full folder path will be displayed only when not using Dense mode. Hovering over the project or package name in the content table will open a hover menu displaying more details for that item. Selecting the name at the top of the hover menu will open the corresponding project/package. |
Project Groups | An optional categorization based on groups defined on the associated pipeline. Selection can affect the behavior/implementation of Deploy All, Test All, and Execute All pipeline stage steps, if any of these steps are configured to execute against only certain project group(s). This will only be displayed if the attached pipeline has project group(s) defined. |
Branch | The branch used when building the project/package during snapshot creation. Only one branch per project/package per release may be used. When an item is added to the release, the branch is initialized in this priority:
|
CI | Read-only column which defines how builds are initiated for the project/package. This column will appear only if a snapshot schedule is configured for the release.
|
Build Environment | The environment to use for builds triggered based on the snapshot schedule. If no build environment is specified and the release has a snapshot schedule, this project/package will not be included in the scheduled build. This environment is also what’s set initially for this item when creating a snapshot manually, although it can be updated. If there is only one build environment for the project, then this will be auto-set. Otherwise, the build environment will be initialized to the last environment the project/package was built against, if one exists. |
Added | The FlexDeploy user who added this item to the release and timestamp of when it was added. Note that this could be a FlexDeploy Bot user if the item was auto-added based on linked work items. |