Value added features of Delivery functionality¶
ALE portal has provided a separate section called "Deliveries" with some additional features for successful deliveries(Figure 1.1). This section can be found on both Buildplace and Release Studio overview pages with respective deliveries.
|Figure 1.1 - Deliveries button|
The features supported by the deliveries section are,
View all the successful deliveries with the information such as Delivery Name, Product Version, Job ID, Baseline Delivery ID, Approval status, Approved By, Last commit Date, Build Time (Figure 1.2).
Lists the deliveries sorted by "created date" in descending order.
Filter deliveries using a text search (Figure 1.2) 
Figure 1.2 - Deliveries table
Download delivery package (Figure 1.3)
Download delivery logs (Figure 1.3)
Download delivery report (Figure 1.3)
Figure 1.3 - Downloadables in Deliveries table
Delivery report is a resultant of a successful delivery creation which downloads in .pdf format and it contains related information on a particular delivery. View sample report Figure 1.4.
Download delivery report option is not available for Initial deliveries and not-approved (pending) deliveries. This option is available for all the successful buildpalce-normal, buildplace-corrective and release-studio deliveries.
"Report" button will be hidden for initial deliveries  and, the button is disabled for not-approved deliveries. (Figure 1.3)
Delivery report is named with the delivery package name. eg: ifs-cloud-22.2E.0-testbp-2.8.0-20230103T110115Z-success.pdf.
Delivery report can contain multiple pages depends on the number of pull requests.
Following are the information included in a delivery report (Figure 1.4).
Title of the report
- Delivery package name
- Customer name
- Customer ID
- User who created the delivery
- User who approved the delivery
- Product version
- Delivery package Release Number
- Delivery package name
- Delivery created timestamp
- Delivery approved timestamp
- Target Branch / Tag of the delivery. For normal delivery, the value of this would be a sanity tag. If it is a corrective delivery, the value would be the topic branch created using the baseline-delivery tag.
- Commit ID of the Target Branch / Tag
- Baseline delivery release number
Baseline delivery name
Delivery report contains all the pull requests details that has been merged in between the baseline delivery tag commit and the target tag / branch commit.
Pull request ID
- Pull request title
Pull request description
If any of the information is missing, it will be indicated with the text "Information Not Found!" in a gray background.
Note: Whatever is added in the Pull Request description will be shown in the delivery report Pull Request Description field. Therefore, when raising a PR, make sure to add a meaningful Pull Request description that is relevant to the commits contained in the PR.
Figure 1.4 - Normal Delivery report Figure 1.5 - Corrective Delivery report Figure 1.6 - Release Update Delivery report
During a failure in the report generation, below toast message will be appeared. In a failure situation, users are advice to raise a support defect with the "Ale TraceId" and the "ErrorCode" mentioned in the toast message.