Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Entities Sprint 19.5b Hotfix Release #18862

Closed
17 of 28 tasks
argush3 opened this issue Dec 5, 2023 · 0 comments
Closed
17 of 28 tasks

Entities Sprint 19.5b Hotfix Release #18862

argush3 opened this issue Dec 5, 2023 · 0 comments
Assignees
Labels
ENTITY Business Team release Release tickets

Comments

@argush3
Copy link
Collaborator

argush3 commented Dec 5, 2023

link to release report

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

  • Tag the release to this ticket
  • Update version numbers in the code being released and list them here:
    • Legal API v2.96.0a
  • Ensure deployment steps are filled in - remove/replace placeholders
  • Create draft releases in GitHub and confirm the correct commits are present
  1. Confirm the correct commits are present
  2. Select appropriate target 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.
  • Dev to ensure that the commit list is represented on the release report
  • QA to schedule the release with staff/clients (daytime's best or when staff are available for rollback)
  • All dev/test pipeline test suites green
  • Dev/QA chat to plan prod verification testing (unless already automated)
  • Post message that projects are being deployed to Prod in Entities Product Team channel
  • Release the code to production and complete smoke test (STEPS BELOW)
  • Post message that projects have been deployed to Prod in Entities Product Team channel and OPS Team channel
  • Finalise/publish the releases in GitHub, tagging it
  • Merge release branch back to master (if applicable)
  • Change openshift builds/pipelines back to master (if applicable)

Deployment Steps

Dev:

  • Legal API v2.96.0a - done by CD script
    .
  • config map changes
  • are there any dependencies, such as an auth/pay deployment or keycloak changes?
  • are there any one-time scripts to be run, such as for data migration?
  • database updates which should be run automatically as part of GH CD via the legal-api pre-hook

Test:

  • Legal API v2.96.0a - done by AC on Dec 4

Prod:

  • Legal API v2.96.0a - done by AC on Dec 4
    .
  • notify the team via the OPS Team channel

Smoke Test Script

  • load Filings UI
  • 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

Verifications specific to release

  • confirm firms previously failing to load are loading without error
@argush3 argush3 added ENTITY Business Team release Release tickets labels Dec 5, 2023
@argush3 argush3 changed the title Copy of Entities Sprint 19.5b Release Entities Sprint 19.5b Hotfix Release Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ENTITY Business Team release Release tickets
Projects
None yet
Development

No branches or pull requests

4 participants