-
Notifications
You must be signed in to change notification settings - Fork 6
EE Build and Deploy Process
Erik Nelsestuen edited this page Mar 11, 2024
·
1 revision
Build and deploy EE to both prod and non-prod environments EE follows same CI/CD process as VRO. Detailed documentations can be found with below references
Reference: https://github.com/department-of-veterans-affairs/abd-vro/wiki/Deployment-Overview https://github.com/department-of-veterans-affairs/abd-vro/wiki/CI-CD-Workflows https://github.com/department-of-veterans-affairs/abd-vro/wiki/Deploying-VRO https://github.com/department-of-veterans-affairs/abd-vro/wiki/Container-Image-Versions
When the PR is merged to develop branch CI process gets triggered
- Navigate to https://github.com/department-of-veterans-affairs/abd-vro-internal/actions/workflows/update-deployment-ee.yml
- Select Domain-EE application, Select target env. Run the workflow
- Images has to be signed before deploying to Sandbox and higher environments
- Secrel job has to succeed. If there is sec-rel issue then visit https://github.com/department-of-veterans-affairs/abd-vro/wiki/Deploying-VRO#verify-and-fix-secrel, Follow steps listed in section Verify and Fix SecRel
- Make sure you sync secrets from vault to cluster using https://github.com/department-of-veterans-affairs/abd-vro-internal/actions/workflows/deploy-secrets.yml
- Follow Release process listed in https://github.com/department-of-veterans-affairs/abd-vro/wiki/Release-Process
- Run workflow https://github.com/department-of-veterans-affairs/abd-vro-internal/actions/workflows/update-deployment-ee.yml, Select target environment and deploy
- Verify Applications are up and running