Skip to content
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

add node 0.12 to travis #415

Closed
wants to merge 1 commit into from
Closed

Conversation

dduugg
Copy link
Contributor

@dduugg dduugg commented Feb 14, 2015

Resolves #414. Also includes some travis-related cleanup, cutting the Travis build time in half (to <1 minute under normal load).

@@ -1,14 +1,12 @@
language: node_js
sudo: false
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A tweak to allow Travis to start up faster. More info here.

@@ -29,7 +29,7 @@
"postinstall": "node node_modules/bower/bin/bower install"
},
"engines": {
"node": "~0.10.0"
"node": "0.10.x"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Equivalent, just switching to the prevailing style. I assume we want to do more thorough testing before adding or switching to "0.12.x".

@coveralls
Copy link

Coverage Status

Coverage remained the same at 70.82% when pulling 39c9d23 on dduugg:wip/travis into 48bdd80 on nightscout:master.


travis: test travis-cov
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Redundant – it's not necessary to separate testing and generating the coverage report.

@dduugg dduugg closed this Feb 14, 2015
@dduugg dduugg reopened this Feb 14, 2015
allow_failures:
- node_js: "0.11"
- "0.10"
- "0.12"
services:
- mongodb
before_script:
- sleep 10
- echo mongo mongo_travis
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious – what is this supposed to do?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe left over from testing the Travis setup? @bewest?

@dduugg dduugg force-pushed the wip/travis branch 2 times, most recently from 7adef4f to 650074b Compare February 15, 2015 01:45
@coveralls
Copy link

Coverage Status

Coverage remained the same at 70.82% when pulling 650074b on dduugg:wip/travis into 48bdd80 on nightscout:master.

@jasoncalabrese
Copy link
Member

Need a new PR that targets dev too, since we're only updating master with releases

@coveralls
Copy link

Coverage Status

Coverage remained the same at 70.82% when pulling 8ddbf09 on dduugg:wip/travis into 48bdd80 on nightscout:master.

@dduugg
Copy link
Contributor Author

dduugg commented Feb 15, 2015

Abandoning to target dev branch

@dduugg dduugg closed this Feb 15, 2015
@dduugg dduugg mentioned this pull request Feb 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add node v0.12 to travis
4 participants