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

Travis build: use a node_js container #509

Merged
merged 2 commits into from Feb 26, 2016

Conversation

Projects
None yet
2 participants
@jonathanperret
Contributor

jonathanperret commented Feb 26, 2016

This could shave a bit off the Travis build times.

jonathanperret added some commits Feb 25, 2016

Tell Travis to use a node_js environment, not Haskell
Since #447 Elm is no longer built from source to run the tests,
therefore a few seconds can probably be shaved from the Travis build by
requesting a node_js environment.
Force Travis to run the build on container-based infrastructure
According to https://docs.travis-ci.com/user/workers/container-based-infrastructure/,
container-based builds are slightly faster, and the default for new
forks. Explicitly requiring a container-based build in `.travis.yml`
should help avoid suprises.
@jonathanperret

This comment has been minimized.

Show comment
Hide comment
@jonathanperret

jonathanperret Feb 26, 2016

Contributor

This seems to be the last obstacle to returning Travis builds to green. So, ping @evancz hopefully?

Contributor

jonathanperret commented Feb 26, 2016

This seems to be the last obstacle to returning Travis builds to green. So, ping @evancz hopefully?

evancz pushed a commit that referenced this pull request Feb 26, 2016

Merge pull request #509 from jonathanperret/travis-node
Travis build: use a node_js container

@evancz evancz merged commit c227e8d into elm:master Feb 26, 2016

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment