-
Notifications
You must be signed in to change notification settings - Fork 7
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
[BAC-943] v1.0.0: Build staging branch #2
base: master
Are you sure you want to change the base?
Conversation
# Push to ECR | ||
$(aws ecr get-login --no-include-email --region us-east-1) | ||
docker tag $SERVICE_NAME:v$version $AWS_ACCOUNT_ID.dkr.ecr.us-east-1.amazonaws.com/$SERVICE_NAME:v$version | ||
docker push $AWS_ACCOUNT_ID.dkr.ecr.us-east-1.amazonaws.com/$SERVICE_NAME:v$version | ||
|
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.
Not a huge deal but this will make us not have to wait on dockerhub to have our services be deployable
@@ -6,11 +6,6 @@ if [ "$CIRCLE_JOB" == "" ]; then | |||
exit 1 | |||
fi | |||
|
|||
# Install AWS cli |
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.
These are already installed in our base docker container: https://github.com/dydxprotocol/docker-node/blob/master/Dockerfile#L3
set -euxo pipefail | ||
|
||
if [ "$CIRCLE_JOB" == "" ]; then | ||
echo "version-and-build.sh should only be run in circle" |
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.
small nit: Assuming you meant version-and-build-staging.sh
?
Publish to the docker repositories a container for the staging branch. Will need to update cookbook to make these versions deployable. And then update each service's circleci config so run this script on the staging branch.
Note: there is a separate version file and version numbering for staging. I think this is necessary as commits can be merged independently to master and staging but we'll have to have engineers adjust to it (not the same version numbers for prod and staging anymore)
Publish as breaking change as VERSION_STAGE needs to be added now
Also I think we should upgrade it to X.0.0 over 0.X.0