2023-04-17 Hotfix Craft Release

Owned by
Jessica Feigal
Last updated: Apr 18, 2023 by
Ian Shields (Deactivated)
2 min read

Release Info:

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

Jira Releases: https://relias.atlassian.net/projects/PAP/versions/33389/tab/release-report-all-issues ,
https://relias.atlassian.net/projects/PAP/versions/33391/tab/release-report-all-issues

Release Owner: @Ian Shields (Deactivated)

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

Prerequisites:

When cutting a branch for the fix

Verified with PM that hotfix is absolutely necessary (cannot wait to go out until the next scheduled release).
Bug ticket for hotfix is created by team.
If there is staging testing currently happening for a scheduled release, need to coordinate with current release owner.
Create hotfix/PAP-XXXX branch off of staging branch.
PR for hotfix branch → staging is created, approved and merged.
PM: create fix version for hotfix.

Once Staging PRs are approved, during staging verification:

Run deploy scripts as needed.
CHM ticket is created by Release Owner.
Confirm fix version is applied to tickets to be released.

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
Ticket(s) 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

Code Deploy:

push to Cloud Remote and Tag*
# cd to craft repo, checkout+pull production then: git tag -a CHM-3502 -m "4/14/23 Craft Release" | git push --tags # cd to magento project, checkout and pull production, then: git push cloud production:Production git tag -a CHM-3489 -m "04/07/23 Magento-Cloud Release" | git push --tags

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

Configuration Items:

Update .env file on craft for n8n endpoints

Post Deploy Release Procedure: