2023-06-28 Craft Release

Owned by
Ben Williamson (Deactivated)
Last updated: Jun 08, 2023
2 min read

Release Info:

Change Management ticket: [insert link]

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

Release Owner:

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

Prerequisites:

Ongoing, beginning the last day of the 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.

Due to a few updates in this release, the deployment may be a bit slow (minutes, not hours). The deploy script needed to be run during staging deployment multiple times to update dependencies, plugins, and configuration.

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: (EXAMPLES)

 

Code Deploy:

push to Cloud Remote and Tag*
git push cloud production:Production git tag -a CHM-3152 -m "06/5/23 Magento-Cloud Release" | git push --tags # cd to craft repo, checkout+pull production then: git tag -a CHM-3152 -m "06/5/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: