Current production deployment builds are launched manually from the docsgenstaging branch. Since the docsgen repo contains documentation dependencies that affect content, the updates to the staging branch do affect content on the production builds. Eventually both contents synchronize - that happens when staging is merged to main and the production site is built from the main branch. This is what this ticket is about.
AC:
Deploy to production from docsgen main branch, but need to be careful within AWS server:
manually checkout the main branch
run script to build to production
verify correct deployment on web portal, else revert from backup
manually checkout the staging branch again (or nightly staging builds will be affected)
create ticket for long term solution
Long term solution is to add to scripts functionality to clone docsgen repo and checkout main when deploying to production, or staging when deploying to staging.
Current production deployment builds are launched manually from the
docsgen
staging
branch. Since thedocsgen
repo contains documentation dependencies that affect content, the updates to thestaging
branch do affect content on the production builds. Eventually both contents synchronize - that happens whenstaging
is merged tomain
and the production site is built from themain
branch. This is what this ticket is about.AC: Deploy to production from docsgen
main
branch, but need to be careful within AWS server:This ticket split from #191.