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.

Sign up for GitHub

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

Jump to bottom

Automate prod release workflow #438

Closed
5 tasks
Tracked by #346
manasaV3 opened this issue Feb 2, 2024 · 1 comment
Closed
5 tasks
Tracked by #346

Automate prod release workflow #438

manasaV3 opened this issue Feb 2, 2024 · 1 comment
Assignees
@manasaV3
Labels
infrastructure P0 Must have
Milestone
OLD - sprint 3 (p...

Comments

@manasaV3
Copy link
Contributor

manasaV3 commented Feb 2, 2024 •
edited
Loading

Tasks:

  • Trigger prod deployment workflow on schedule
  • Validate checks are passing
    • All tests pass successfully in staging
    • The kill switch allows for a deployment
  • Get the changelog added and version
  • Deploy tagged version to prod
  • Run Tests against prod
@manasaV3 manasaV3 mentioned this issue Feb 2, 2024
Closed
3 tasks
@manasaV3 manasaV3 self-assigned this Feb 2, 2024
@manasaV3 manasaV3 changed the title Automate release workflow Automate prod release workflow Feb 2, 2024
@manasaV3
Copy link
Contributor Author

manasaV3 commented Feb 5, 2024 •
edited
Loading

Depends on: #437 , #337, #338, #340, #341, #342

@manasaV3 manasaV3 mentioned this issue Feb 20, 2024
Merged
manasaV3 added a commit that referenced this issue Feb 27, 2024
@manasaV3
feat: Update workflow for automating prod deploy (#471)
48bce7f 
Relates to
#438

### Changes introduced

- Adds conventional commit check to PRs as the `release-please`
dependency that we use for generating change logs expects commit
messages to follow the conventional commit format.

#### Prod deploy
- Adds a schedule to deploy on weekdays Mon-Fri @ 18:00 UTC (10AM PST
[winter] / 11AM PDT [summer])
- Conditionals checks introduced before prod deployment:
- If there have been new changes added to the front end since the last
release using change release.
  - If the staging e2e tests pass before kicking off a deploy.
- If the kill switch for prod deploys `secrets.IS_DEPLOY_ALLOWED`, it
allows deployment. The kill switch is added for cases where regressions
are identified in staging that we don't want to be deployed to
production.
- Adds a check to verify if the prod e2e tests pass after kicking off a
deploy


### Doc deploy
- Currently, the doc generation and deploy workflow uses adding a tag as
a trigger. The PR updates it to ignore any tag prefixed by `frontend-`.
@manasaV3 manasaV3 mentioned this issue Feb 29, 2024
Merged
manasaV3 added a commit that referenced this issue Feb 29, 2024
@manasaV3
fix: prod deploy tagging (#516)
2a4524d 
Relates to
#438
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@manasaV3 manasaV3

Labels
infrastructure P0 Must have
Projects
None yet
Milestone
OLD - sprint 3 (phase 3)
Development

No branches or pull requests
2 participants
@manasaV3 @junxini