[Travis] Only test/produce binaries for v0.10 and v4 #159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
springmeyer
pushed a commit
that referenced
this pull request
Mar 1, 2016
[Travis] Only test/produce binaries for v0.10 and v4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Now that Node.js is stabilized to the LTS concept I think we should only target node v4.x (instead of the old v0.12 that very few updated to and the v5 that is the unstable series). And for a while longer we should still support node v0.10.x.
So, this moves to only testing and building against v0.10.x and v4.x.
The
Project-OSRMorganization on travis only has 5 concurrent builds (like all open source orgs) so this reduces a single node-osrm commit to only triggering 3 jobs on Linux. This should allow for multiple node-osrm commits to different branches to run (almost) in parallel.