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

[IT-3891] Refactor CI #44

Merged
merged 2 commits into from
Sep 20, 2024
Merged

Conversation

zaro0508
Copy link
Contributor

@zaro0508 zaro0508 commented Sep 20, 2024

Refactor Github CI to deploy to multiple environments (dev, stage, prod).

This enforces the following workflow..

  1. Create PR from the git dev branch
  2. PR is reviewed and approved
  3. PR is merged
  4. CI deploys changes to the dev environment (dev.openchallenges.io) in the org-sagebase-openchallenges-dev account.
  5. Changes are promoted (or merged) to the git stage branch.
  6. CI deploys changes to the staging environment (stage.openchallenges.io) in the org-sagebase-openchallenges-prod account.
  7. Changes are promoted (or merged) to the git prod branch.
  8. CI deploys changes to the prod environment (prod.openchallenges.io) in the org-sagebase-openchallenges-prod account.

Refactor Github CI to deploy to multiple environments (dev, stage, prod).

This enforces the following workflow..
1. Create PR from the git dev branch
2. PR is reviewed and approved
3. PR is merged
4. CI deploys changes to the dev environment (dev.openchallenges.io)
   in the org-sagebase-openchallenges-dev account.
5. Changes are promoted (or merged) to the git stage branch.
6. CI deploys changes to the stage environment (stage.openchallenges.io)
   in the org-sagebase-openchallenges-prod account.
6. Changes are promoted (or merged) to the git prod branch.
7. CI deploys changes to the prod environment (prod.openchallenges.io)
   in the org-sagebase-openchallenges-prod account.
@zaro0508 zaro0508 requested review from a team as code owners September 20, 2024 15:57
@zaro0508 zaro0508 requested a review from tschaffter September 20, 2024 16:38
@tschaffter
Copy link
Contributor

This is great! Ultimately, I may request that the dev deployment is executed when a commit is pushed to a branch, e.g. https://github.com/Sage-Bionetworks/sage-monorepo/commits/main.

@zaro0508
Copy link
Contributor Author

zaro0508 commented Sep 20, 2024

This is great! Ultimately, I may request that the dev deployment is executed when a commit is pushed to a branch, e.g. https://github.com/Sage-Bionetworks/sage-monorepo/commits/main.

you may can try and experiment with that but I can tell you that parallel deployments from multiple branches to a single AWS environment does not work very well.

@zaro0508 zaro0508 merged commit 52d6fd7 into Sage-Bionetworks-IT:dev Sep 20, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants