entity icon indicating copy to clipboard operation
entity copied to clipboard

Entities Sprint 22.1a Release

Open severinbeauvais opened this issue 1 year ago • 3 comments

Prior to moving into production, the following steps should be completed or confirmed:

  • [x] Add release # to this ticket
  • [x] Create Zenhub release report -> Entities Sprint 22.1a Release
  • [x] Update version numbers in the code being released and list them here:
    • Business Create UI v5.11.7
    • Business Filings UI v7.3.9
    • Business Edit UI v4.10.2
    • Legal API v2.117.0
    • Business Pay (no version)
    • Involuntary Dissolutions job (no version)
    • Furnishings job (no version)
    • Entity Filer v2.117.0
    • COLIN API v2.117.0
  • [x] Ensure deployment steps are filled in - remove/replace placeholders
  • [x] Create a draft release in GitHub:
    1. Confirm the correct commits are present
    2. Select appropriate target is selected which represents the build in Test - either a commit from recent commits or a reference to a branch
    3. Autogenerate release notes using last release tag as a point of reference. Update change list manually if required.
  • [x] Dev to ensure that the commit list is represented on the release report
    • tag all respective tickets to current release
  • [x] All dev/test pipeline test suites green
  • [x] Dev/QA chat to plan prod verification testing (unless already automated)
  • [x] Post message that projects are being deployed to Test in "Entities Product Team" channel
  • [x] Deploy the code to production
  • [x] Complete smoke test (STEPS BELOW)
  • [x] Post message that projects have been deployed to Prod in "Entities Product Team" and "Ops Team" channels
  • [x] Finalise/publish the releases in GitHub (including tagging them)
  • [ ] ~Merge release branch back to master (if applicable)~ not applicable
  • [x] Close the Zenhub release report when complete
  • [x] Move this ticket to Done when complete

Deployment Steps

Dev:

  • [x] Business Create UI v5.11.7
  • [x] Business Filings UI v7.3.9
  • [x] Business Edit UI v4.10.2
  • [x] Legal API v2.117.0
  • [x] Business Pay (no version) - see Business Pay deployment in comment below
  • [x] Involuntary Dissolutions job (no version)
  • [x] Furnishings job (no version)
  • [x] Entity Filer v2.117.0
  • [x] COLIN API v2.117.0 .
  • [ ] ~config map changes~ none
  • [ ] ~are there any dependencies, such as an auth/pay deployment or keycloak changes?~ none
  • [ ] ~are there any one-time scripts to be run, such as for data migration?~
    • note that there is an automatic migration script associated with #21817
  • [ ] ~database updates which should be run automatically as part of GH CD via the legal-api pre-hook?~ none

Test:

  • [x] Business Create UI v5.11.7 - done by SB on July 5, 2024
  • [x] Business Filings UI v7.3.9 - done by SB on July 5, 2024
  • [x] Business Edit UI v4.10.2 - done by SB on July 5, 2024
  • [x] Legal API v2.117.0 - done by SB on July 5, 2024
  • [x] Business Pay (no version) - see Business Pay deployment in comment below - done by SB on July 5, 2024
  • [x] Involuntary Dissolutions job (no version) - done by SB on July 5, 2024
  • [x] Furnishings job (no version) - done by SB on July 5, 2024
  • [x] Entity Filer v2.117.0 - done by SB on July 5, 2024
  • [x] COLIN API v2.117.0 - done by SB on July 5, 2024 .
  • [ ] ~config map changes~ none
  • [ ] ~are there any dependencies, such as an auth/pay deployment or keycloak changes?~ none
  • [ ] ~are there any one-time scripts to be run, such as for data migration?~
    • note that there is an automatic migration script associated with #21817
  • [ ] ~database updates which should be run automatically as part of GH CD via the legal-api pre-hook?~ none

Prod:

  • [x] Business Create UI v5.11.7 - done by SB on July 11, 2024
  • [x] Business Filings UI v7.3.9 - done by SB on July 11, 2024
  • [x] Business Edit UI v4.10.2 - done by SB on July 11, 2024
  • [x] Legal API v2.117.0 - done by SB on July 11, 2024
  • [x] Business Pay v2.117.0 - see Business Pay deployment in comment below - done by SB on July 11, 2024
  • [x] Involuntary Dissolutions job v2.117.0 - done by SB on July 11, 2024
  • [x] Furnishings job v2.117.0 - done by SB on July 11, 2024
  • [x] Entity Filer v2.117.0 - done by SB on July 11, 2024
  • [x] COLIN API v2.117.0 - done by SB on July 11, 2024 .
  • [ ] ~config map changes~ none
  • [ ] ~are there any dependencies, such as an auth/pay deployment or keycloak changes?~ none
  • [ ] ~are there any one-time scripts to be run, such as for data migration?~
    • note that there is an automatic migration script associated with #21817
  • [ ] ~database updates which should be run automatically as part of GH CD via the legal-api pre-hook?~ none

Smoke Test Script

  • [ ] load Filings UI, eg, display an application or business
  • [ ] load Edit UI, eg, start change or alteration filing
  • [ ] load Create UI, eg, start an IA or registration or voluntary dissolution
  • [ ] watch Sentry logs for 60 minutes
  • [ ] watch Kibana logs for 60 minutes

severinbeauvais avatar Jun 25 '24 16:06 severinbeauvais

When deploying business-pay to DEV:

export OPENSHIFT_DOCKER_REGISTRY="image-registry.apps.silver.devops.gov.bc.ca/cc892f-tools/business-pay"
docker login -u openshift -p $(oc whoami -t)  $OPENSHIFT_DOCKER_REGISTRY
docker build --platform linux/amd64 --build-arg APP_ENV=production -t business-pay -f Dockerfile .
docker tag business-pay image-registry.apps.silver.devops.gov.bc.ca/cc892f-tools/business-pay
docker push image-registry.apps.silver.devops.gov.bc.ca/cc892f-tools/business-pay
oc -n cc892f-tools tag business-pay:latest business-pay:dev

After that, when deploying to TEST:

oc -n cc892f-tools tag business-pay:dev business-pay:test

So, basically, you just need to run one command Sev which is that last one.

JazzarKarim avatar Jul 05 '24 16:07 JazzarKarim

After that, when deploying to PROD:

oc -n cc892f-tools tag business-pay:test business-pay:prod

severinbeauvais avatar Jul 05 '24 21:07 severinbeauvais

Just a note that deploying Legal API took most of the afternoon and lots of help from Ops Team (Patrick, Andryi and Travis). The CD script kept failing due to some processes not completing, apparently due to insufficient CPU resources and pod scaling. Eventually Legal API was deployed manually (not using CD script).

We may need an action to review CPU allocating and pod scaling to avoid Legal API CD issue next time.

severinbeauvais avatar Jul 11 '24 16:07 severinbeauvais

Completed

NaveenHebbale avatar Jul 15 '24 14:07 NaveenHebbale