...

List of Jira tickets for Deployment: https://sydneyuni.atlassian.net/projects/TAPSS/versions/23027/tab/release-report-all-issues

Pre-Deployment Steps

•  Prepare Main package containing the following JIRAs (Ehanced Domain, TAPs, WB/Hogwarts). Here’s the source Bitbucket Branch:release/TAP-May-R2-Release-Package
•  Enhanced Domain items:

  Jira Legacy
  server System JIRA serverId e9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a key TAPSS-462

  . Contents should include the following items listed here
•  Close Batch Interim fix:

  Jira Legacy
  server System JIRA serverId e9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a key TAPSS-1205

•  Items c/o Swathi
•  TAPSS-222
•  TAPSS-260
•  TAPSS-906
•  TAPSS-912
•  TAPSS-1060
•  TAPSS-262
•  TAPSS-239
•  TAPSS-240
•  Well Being and Hogwarts items
•  

  Jira Legacy
  server System JIRA serverId e9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a key SPI1-3882

•  

  Jira Legacy
  server System JIRA serverId e9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a key SPI1-3945

•  

  Jira Legacy
  server System JIRA serverId e9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a key SPI1-3951

•  

  Jira Legacy
  server System JIRA serverId e9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a key TAPSS-895

•  Run validation in Bitbucket
•  Merge each branch approved for PROD Deployment to the Release branch for release/TAP-May-R2-Release-Package
•  Navigate to the release branch - release/TAP-May-R2-Release-Packageandclick the Create Pull Request button
•  Add the necessary approvers, and click Create Pull Request
•  The Validation Pipeline will run in the background. When the pipeline has no errors, it is ready for approval.
•  Once approved, merge the pull request. Merging to the Master branch will not trigger auto-deployment. Proceed to the Actual Deployment Steps

...