Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 44 Current »

Release Info:

Release Owner: Lakshmi Kondragunta

Code readiness Owner : Doug Wagner

Deployment owner: Doug Wagner

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

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

Endeca Configuration and Template Changes:

Server Configuration Changes (ATG-Data) on Production Boxes:

  • Verify and update URLCaseServlet, SitemapGeneratorService, ProductIndirectTemplate components on the Production instances.
  • Set the Sitemap schedule to once everyday at 9am ET

Any style changes (update the relias.css file): No

Pre-release steps:

  • Pull current URL list with Screaming Frog Brandon Hendry
  • Backup current Production sitemap files from
    /opt/app/apache/store/html/
  • Backup current Production ATG-Data properties files (only localconfig on webapp1, 2, and BCC) from
    /opt/app/jboss/ATG-Data/servers/
    [ecom@1196878-ProdWebApp1 servers]$ cp -pr prod_store01/localconfig/ /home/ecom/store01_localconfig_atg-data/
  • Update Endeca indexing schedule to skip Thursday morning run, restart BCC before 2am ET nightly catalog import
  • Disconnect sitemap update from Endeca indexing
    cd /opt/app/endeca/apps/CRS/control
    comment out last line in sitemapGeneration.sh
    chmod -x sitemapToApache.sh
  • Merge working branch PAP-4542_Academy_SEO_priorities 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 the nightly catalog import completed successfully, including BCC project deploy
  • Make the required template changes for Endeca
  • Server Configuration Changes (ATG-Data) on Production Boxes
  • Check that there’s sufficient disk space on utility machine to do build and deploy
  • Build and deploy
  • Restart the instances

Post Release Procedure:

  • Generate the Sitemap on App1 Store 2 instance. Update the sitesToInclude with the main store, and MHFA (storeSiteUS,MHFA)
  • After code deployment is complete, start regression testing. (Lakshmi Kondragunta Henry Fu you can start on this when you start your work day)
  • Update any product URLs in XM pages, including sb1 link in grid below hero image
  • Update profession URLs on the Endeca landing pages in XM, including changing text in hero image
  • Trigger the Ghost Inspector tests (Some will fail, it’s expected)
  • Verify all the tickets in the fix version and mark them as done. (Brandon Hendry need your help with the SEO tickets)
  • Update reCaptcha score on all the store instances Lakshmi Kondragunta
  • Crawl site with Screaming Frog to monitor changes & check for errors Brandon Hendry
  • Force Crawls for new Sitemap URLs on Search Console Brandon Hendry
  • Restore Endeca indexing schedule and restart BCC
  • Release Owner to Mark Jira Release as Released, Mark CHM ticket as Complete
  • Release Owner to Notify Stakeholders via email that release is complete
  • Notify Stakeholders in Slack ReliasEcom > sprint_releases channel that release is complete

  • No labels