2024-05-14 Relias Academy release

Release Info:

Release Owner: Lakshmi Kondragunta

Code readiness Owner : Doug Wagner

Deployment owner: Henry Fu

Change Management ticket: CHM-4625 - Getting issue details... STATUS

Jira Fix Version for Relias Academy: https://relias.atlassian.net/projects/PAP/versions/34590/tab/release-report-all-issues

Any style and JavaScript changes (update the relias.css file): JS changes.

Pre-release steps:

• production Segment write keys
• Release Owner / Product Owner to Notify Stakeholders via Microsoft Teams Relias Academy Release Channel regarding this upcoming release. (link)
• Release Owner / Deployment owner to Notify Platform Engineering and Communities teams regarding the upcoming release, in slack channels. ReliasEcom (#sprint-releases), Relias Engineering (#next-deployment)
• Merge release_gelato (sprint name) branch into develop branch
• Build and deploy develop branch to Staging and do a round of regression testing
• Merge develop branch into oracle_ATG_upgrade_11.1_to_11.3.2 release branch
• Update Endeca template (see https://relias.atlassian.net/browse/PAP-7572?focusedCommentId=460921 for steps and also see Config Notes field in that Jira)

Release steps Relias Academy: (To Update all sections below)

• Check that there’s sufficient disk space on utility machine to do build and deploy
• Build oracle_ATG_upgrade_11.1_to_11.3.2 branch
• Properties files changes?
• DB changes?
• Deploy to all instances
• check DB changes
• Restart the instances
• Purge cache on Cloudflare
• https://reliasacademy.com/crsdocroot/content/css/relias/min/relias.css
• https://reliasacademy.com/crsdocroot/content/javascript/relias/min/customNew.js
• https://reliasacademy.com/crsdocroot/content/javascript/relias/min/myAccount.js
• others?

Post Release Procedure:

• After code deployment is complete, start regression testing. (Lakshmi Kondragunta Henry Fu)
• Trigger the Ghost Inspector tests (may need to update tests)
• Verify all the tickets in the fix version and mark them as done
• Release Owner to Mark Jira Release as Released, Mark CHM ticket as Complete
• Release Owner to Notify Stakeholders via Microsoft Teams Release Channel that release is complete
• Notify Stakeholders in Slack ReliasEcom > sprint-releases channel that release is complete, Engineering Slack too (next-deployment channel)