Switch to CircleCI #42
Merged
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.
Switch from Travis CI to Circle CI.
There are a handful of build-related scripts in the
travis/directory, and some of them expect the environment variables that Travis CI provides. Rather than modify those scripts, I chose to set the variables they expect from their CircleCI counterparts when they're called from.circleci/config.yml. For example:TRAVIS_BRANCH="${CIRCLECI_BRANCH}" travis/setup-git.shI chose this approach because upstream still uses Travis. If they alter these build scripts, keeping them "clean" will make it easier to merge from upstream in the future.
The rest of the config attempts to match the previous behavior, with the exception that I added
package-lock.jsonand usenpm cithrough thenode/install-packagescommand from thenodeorb.