Skip to content

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 Build place and Release Studio overview pages with respective deliveries.

Figure 1.1 - Deliveries button

The features supported by the deliveries section are,

  1. View all the successful deliveries with following information(Figure 1.2).

    • Delivery Packages - The short version of Package name Eg: If the package name is "ifs-cloud-22.1.13-abcd123-1.3.0-20230817T082647Z-success", delivery packages column value will be "1.3.0-20230817T082647Z-success"
    • Product Version - Service update version of the delivery
    • Job Id - Delivery creation job ID
    • Approval Status - Delivery Approval Status If the delivery is approved, the status will be labeled as "Approved"; otherwise, if it has not been approved yet, the status will be marked as "Pending."
    • Package Name - Delivery package name which is created in the format of *del-ifs-cloud-<version tag>-<build place ID>-<delivery version>-<datetime in UTC>-success
    • Baseline Delivery ID - ID of the delivery which the delivery is based on
    • Approved By - Email of the user who approved the delivery
    • Last Commit Date - Date and Time of which the delivery creation was completed
    • Build Time - Build time of the delivery

  2. Lists the deliveries sorted by "created date" in descending order.

  3. Filter deliveries using a text search (Figure 1.2) [1]
    Figure 1.2 - Deliveries table

  4. Download delivery package (Figure 1.2)[2]

  5. Download delivery logs (Figure 1.2)[3]

  6. Download delivery report (Figure 1.2)[4]

  7. Approve the delivery (Figure 1.2)[7]

Approve Delivery

  • It is recommended to approve the delivery once it is tested and ready, using the 'Approve Delivery' button which is available in the delivery environment at the time of delivery creation (Refer :After the Delivery is created). However, if the user is unable to approve the delivery during the lifespan of the delivery environment, it can be approved using the button visible in the 'Deliveries' table as well [7] (Figure 1.2). If you are approving the delivery through the 'Deliveries' table, please ensure that the delivery has already been tested using the delivery environment.

  • In order to approve delivery, click on the 'Approve' button (Figure 1.2) [7] from the deliveries table and then confirm delivery approval by clicking 'Yes' in the confirmation popup. (Figure 1.3).
    Figure 1.3 - Approve Delivery Confirmation pop up

  • Note that the deliveries created prior to IFS Cloud release 23R2 might have been created using the same sanity tag. The following error message (Figure 1.4) is shown if a user tries to approve such a delivery. In such a scenario, the user can approve only the latest delivery created which is shown in the error pop-up(Figure 1.4)[1].
    Figure 1.4 - Unable to approve delivery error pop up

Delivery report

  • 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.5.

  • 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 [6] and, the button is disabled for not-approved deliveries[5]. (Figure 1.2)

  • 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.5).

  • Title of the report[1]

  • Delivery package name[2]
  • Customer name[3]
  • Customer ID[4]
  • User who created the delivery[5]
  • User who approved the delivery[6]
  • Product version[7]
  • Delivery package Release Number[8]
  • Delivery package name[9]
  • Delivery created timestamp[10]
  • Delivery approved timestamp[11]
  • Target Branch / Tag of the delivery[12]. 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[13]
  • Baseline delivery release number[14]

  • Baseline delivery name[15]

  • 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[16]

  • Pull request title[17]

  • Pull request description[18]

  • If any of the information is missing, it will be indicated with the text "Information Not Found!" in a gray background[19].

    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.5 - Normal Delivery report
    Figure 1.6 - Corrective Delivery report
    Figure 1.7 - 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.