Skip to content
This repository has been archived by the owner on Sep 3, 2024. It is now read-only.

Latest commit

 

History

History
28 lines (28 loc) · 3.55 KB

release-checklist.md

File metadata and controls

28 lines (28 loc) · 3.55 KB
Raw

--- Production Deployment Preparation

  • [] Confirm that dev_tests_passed_[timestamp] tag was created for the commit you wish to deploy.

When the latest code passes tests in GHA, it is tagged dev_tests_passed_[timestamp] where [timestamp] is the epoch time when the tag was created.

  • [] Update the ticket name, replacing x.x.x with the semver number.
  • [] Create Bond Release in Jira

In Jira, make sure the Bond Release exists or create a new one in the Cloud Integration Project named like: Bond-X.Y.Z where X.Y.Z is the same semantic version number you created in the previous step

  • [] Set the Fix Version for each Jira Issue included in this release

Find the tickets included in this release by looking through the commits/PRs committed to the main branch since the last release.

Set the Fix Version field to the release name you created in the previous step. The status of each of these issues should be: Merged to Dev. If the status is something else, verify whether the ticket should be included in this release. Each Jira issue must have a clear description of the change and its security impact.

  • [] Set the Fix Version on this Release Issue --- Deploy and Test
  • [] Deploy to dev and perform manual test
  • Bond is automatically deployed to dev on merge to the default branch (i.e. develop).
  • Perform the manual test If desired, you can manually promote Bond through to whatever environments you want as follows, however, new Bond helm charts and versions are automatically released on merge to Bond and terra-helmfile and promoted with the monolith release, so this is for independent releases or hotfixes only:
  • [] Check the Release Protection Window Calendar
  • [] Notify the #workbench-release Slack channel that you will be releasing a new version of Bond to staging, and prod along with the link to the release version in Jira.
  • [] Deploy to staging and perform manual test
  • Navigate to bond-staging in Beehive, click on "Change Versions" and then "Click to Refresh and Preview Changes". Review the changeset, and if it looks good, apply it and wait for Staging to be updated.
  • Perform the manual test
  • [] Deploy to prod and perform manual test
  • In order to deploy to prod, you must be on the DSP Suitability Roster.
  • Navigate to bond-bond in Beehive, click on "Change Versions" and then "Click to Refresh and Preview Changes". Review the changeset, and if it looks good, apply it and wait for Prod to be updated.
  • Perform the manual test
  • [] Transition all tickets in the Release in Jira to "Done"
  • [] Mark the Release in Jira as "Released"

Navigate to the Releases Page in Jira and mark the version as "Released"