fix: auto-deploy#1835
Merged
Merged
Conversation
spaenleh
force-pushed
the
auto-deploy-dev
branch
from
5c7956b to
f64753b
Compare
pyphilia
approved these changes
Apr 30, 2025
spaenleh
force-pushed
the
auto-deploy-dev
branch
from
84409d4 to
5965b11
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In this PR I
build.shscript up into the AWS auth part and the docker build and push partBUILD_TIMESTAMPenv var that is set at build time so we can get when the image was built on the/versionendpointHow the dev deploy works now
When we merge to main, we build an image that we push to the private ECR of the dev environment.
It is tagged as
core-next.Every morning a workflow in infra is triggered and deploy this
core-nextwith the migration.So at the latest the next day, the changes will be on dev.