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

[Spike] Document deploy process in all envs #8345

Open
mehansen opened this issue Dec 6, 2024 · 0 comments
Open

[Spike] Document deploy process in all envs #8345

mehansen opened this issue Dec 6, 2024 · 0 comments
Labels
Tech Debt issues dedicated to the resolution of technical debt

Comments

@mehansen
Copy link
Collaborator

mehansen commented Dec 6, 2024

Description

The engineering team could benefit from a deeper understanding of what goes on when we deploy, especially for debugging build issues or ensuring that sufficient tests have been run. Examples of questions to be answered are:

  • at what point in the process do certain tests get run? (e.g. on merge to main, build, deploy)
  • when you run the GitHub action to deploy, how many containers are booting up and initializing the app and in what order?

Proposed solution

For each environment, document the following:

  • what triggers the deploy
  • steps, including tests
  • when containers booted and when/how slot swap happens
  • anything else?

For environments that have identical behavior, no need to duplicate info.

@DanielSass DanielSass added Tech Debt issues dedicated to the resolution of technical debt and removed Needs refinement sync labels Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tech Debt issues dedicated to the resolution of technical debt
Projects
None yet
Development

No branches or pull requests

2 participants