2023-12-19 Relias Academy GPay release - Relias Communities Platform

REMINDER: before we plan for the release, we need to account for getting approval from Google to use GPay for payments on production. Should we send the screenshots of payment pages to get it approved?

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 (#nextrelease)

Merge working 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

Release steps Relias Academy:

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 (do switch branch cleanup first)

Deploy to all instances

Add StoreConfiguration.properties to store instances (e.g., /opt/app/jboss/ATG-Data/servers/prod_store01/localconfig/atg/store/)

Create table PRODCORE.RLS_GOOGLEPAY in database (if we dropped it from test run)

Restart the instances

Purge cache on Cloudflare

Post Release Procedure:

After code deployment is complete, start regression testing. (@Lakshmi Kondragunta @Henry Fu)

Trigger the Ghost Inspector tests (they should pass; updated test steps this time to add back state to URL when a state is selected)

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 (nextrelease channel)