2023-05-03 Craft Release

Owned by
Ben Williamson (Deactivated)
Last updated: May 04, 2023
2 min read

Release Info:

Change Management ticket: https://relias.atlassian.net/browse/CHM-3547

Jira Release: https://relias.atlassian.net/projects/PAP/versions/33354/tab/release-report-all-issues

Release Owner: @Ben Williamson (Deactivated)

Testing Assignment spreadsheet (Check ALL 4 TABS to see if any are assigned to you.)

https://docs.google.com/spreadsheets/d/1mcP2skcGdncsIss8bRa7i37EHW49M_PiX-M2CWXWyYA/edit#gid=1693716108

Prerequisites:

Ongoing, beginning the last day of the sprint:

Create two Jira tickets: one to capture the release owners work and one to capture the QA work for staging verification and pull them into the current sprint.
Create PRs from feature branches to staging for all tickets tagged in the release as they reach Ready for Stage Deployment status.
Post links to the PRs in a highly visible channel to signal to team members that they’re ready for review
Run deploy scripts as needed and move tickets to Ready for Stage Testing status

Once Staging PRs are approved, during staging verification:

All code merged to Staging branch at least 2 business days before release
Tickets with configurations are assigned to developers
CHM ticket is created by Release Owner
Confirm fix version is applied to all tickets to be released. Use No Release Impact fix version for tickets with no code or user-facing changes.

If the staging deploy of Craft or Magento took longer than usual, communicate this to the team and discuss scheduling the release call for everyone.

If deployment will take substantially more time than ~20 minutes, please consider starting the release call with Manager, PM, Release Owner, QA Team Lead. Once the deployments are complete, open the release call to the rest of the team for testing and debugging.

Day of:

Clean Stable build on Stage, not updated since testing period began
All tickets in “ready to release” status
CHM approval given by Default reviewer - usually Matt
Create PRs for deploy
PRs are approved and code is merged into production branch on our repository
Message in the #sprint-releases channel that the release is beginning

Pre-Deploy:

Recent Automated tests run and results verified

Configuration Items:

@Ben Williamson (Deactivated) and - .env file has n8n variables before build time
@Ben Williamson (Deactivated) - Confirm data in place for course descriptions and rlms_id aka importSourceId

Code Deploy:

git push cloud production:Production git tag -a CHM-3547 -m "05/04/23 Magento-Cloud Release" | git push --tags # cd to craft repo, checkout+pull production then: git tag -a CHM-3547 -m "05/04/23 Craft Release" | git push --tags

*Sample snippet only, code deploy owner to verify prior to release. Do NOT trust the release owner.

Post Deploy Release Procedure: