-
Notifications
You must be signed in to change notification settings - Fork 24
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
fix(semantic-release): resolve semantic release issues #653
Conversation
…ravis-deploy-once
.travis.yml
Outdated
@@ -17,8 +17,7 @@ env: | |||
|
|||
install: | |||
- DC_FILES="-f docker-compose.yml -f docker-compose.ci.yml" | |||
- docker-compose $DC_FILES build | |||
- docker images | |||
#- docker-compose $DC_FILES build |
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 thought it was best to remove the build arg, because docker-compose up
will build the container if does not exist. Since in travis, the environments are ephemeral, its safe to remove the explicit build and let docker-compose up handle this.
@@ -6,7 +6,7 @@ set -o pipefail | |||
# always tag on git hash | |||
TAG="v-$(git log -1 --pretty=%h)-beta" | |||
|
|||
docker build -t "${REPO}":"${TAG}" . |
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.
Since are already building a container, and running the tests in that container, it makes no sense to have to rebuild it, rather tag it as required and pushed. This should speed up the build times a bit as well
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.
- [skipped] Tested changes manually
- [n/a] Checked accidental architectural/style changes
- Reviewed entire diff
- [n/a] Unit tests
- [n/a] Documentation
- [n/a] Filenames and locations
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
PR Process - PR Review Checklist
Release
Description of Changes
Fixes #637
The
language: minimal
travis environment does not have npm installed, causing semantic release not to run. Also having the semantic-release step inafter_deploy
meant that even though it was failing, the job was still passing. The travis-deploy-once package is also not needed since we are running the semantic-release inside a docker container, and thetravis-deploy-once
will not run and throughs an error if being run no in Travis.