-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Docker base and CircleCI updates #3045
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,6 +11,7 @@ jobs: | |
- DOCKER_VERSION: 17.05.0-ce | ||
- DOCKER_COMPOSE_VERSION: 1.15.0 | ||
- METEOR_ALLOW_SUPERUSER: true | ||
- TOOL_NODE_FLAGS: "--max-old-space-size=4096" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. any further reference on the memory issue / fix here? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There is no update on the memory usage of the Meteor build tool. I think the real solution is just building a smaller app. And that's one of the focuses of our upcoming performance work on Reaction. |
||
|
||
steps: | ||
- setup_remote_docker | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,39 +5,17 @@ | |
# | ||
# $DOCKER_USER - Docker Hub username | ||
# $DOCKER_PASS - Docker Hub password | ||
# $DOCKER_EMAIL - Docker Hub email | ||
|
||
|
||
## Optional Environment Variables | ||
# (used to customize the destination on Docker Hub without having to edit the CircleCI config) | ||
# | ||
# $DOCKER_NAMESPACE - the image name for production deployments [Default]: reactioncommerce/reaction | ||
# $DOCKER_NAMESPACE_DEV - the image name for development deployments [Default]: reactioncommerce/prequel | ||
|
||
|
||
if [[ "$CIRCLE_BRANCH" != "master" && "$CIRCLE_BRANCH" != "development" ]]; then | ||
if [[ "$CIRCLE_BRANCH" != "master" ]]; then | ||
echo "Not running a deployment branch." | ||
exit 0 | ||
fi | ||
|
||
|
||
## Development | ||
if [[ "$CIRCLE_BRANCH" == "development" ]]; then | ||
set -e | ||
|
||
DOCKER_NAMESPACE=${DOCKER_NAMESPACE:-"reactioncommerce/reaction"} | ||
DOCKER_NAMESPACE_DEV=${DOCKER_NAMESPACE_DEV:-"reactioncommerce/prequel"} | ||
|
||
docker tag $DOCKER_NAMESPACE:latest $DOCKER_NAMESPACE_DEV:latest | ||
docker tag $DOCKER_NAMESPACE_DEV:latest $DOCKER_NAMESPACE_DEV:$CIRCLE_BUILD_NUM | ||
|
||
docker login -u $DOCKER_USER -p $DOCKER_PASS | ||
|
||
docker push $DOCKER_NAMESPACE_DEV:$CIRCLE_BUILD_NUM | ||
docker push $DOCKER_NAMESPACE_DEV:latest | ||
fi | ||
|
||
|
||
# Master branch deployment (only runs when a version git tag exists - syntax: "v1.2.3") | ||
if [[ "$CIRCLE_BRANCH" == "master" ]]; then | ||
VERSION=$(git describe --tags | grep "^v[0-9]\+\.[0-9]\+\.[0-9]\+$") | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hmm.. how do you guys handle tagging releases such as patch, hotfix, & the like? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We tag release versions in the format |
||
|
@@ -49,7 +27,7 @@ if [[ "$CIRCLE_BRANCH" == "master" ]]; then | |
|
||
docker tag $DOCKER_NAMESPACE:latest $DOCKER_NAMESPACE:$VERSION | ||
|
||
docker login -e $DOCKER_EMAIL -u $DOCKER_USER -p $DOCKER_PASS | ||
docker login -u $DOCKER_USER -p $DOCKER_PASS | ||
|
||
docker push $DOCKER_NAMESPACE:$VERSION | ||
docker push $DOCKER_NAMESPACE:latest | ||
|
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.
Should I wait to merge this until after we've released 1.5.0?
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.
I was under the impression the
release-1.5.0
branch is marketplace. No?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.
Either way, this will have no effect on whether marketplace continues to build in CI unless you merge
release-1.5.0
back into marketplace.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.
And we definitely want this to be part of the 1.5.0 release. The current Docker base isn't using the current 4.x version of Node that we should be (4.8.4).