-
Notifications
You must be signed in to change notification settings - Fork 87
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
feat: migrate CI pipeline to github actions #3120
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm. Just a question; we seem to have 3 of each CI running; I assume that's due to PR CICD steps + staging/staging-alt deployments yeah?
Closing and reopening to refresh the checks as Travis CI is still there |
This PR migrates the CI pipeline to Github Actions.
Note that we have dropped Sentry integration with this migration to GA.
New environment variables:
staging
,staging-alt
,release
,uat
):APP_NAME
DEPLOY_ENV
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION
ECR_REPO
BUCKET_NAME