Thanks to visit codestin.com
Credit goes to github.com

Skip to content

chore(travis): add OS X to Travis CI #283

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

Merged
merged 1 commit into from
Jan 16, 2016
Merged

chore(travis): add OS X to Travis CI #283

merged 1 commit into from
Jan 16, 2016

Conversation

nfischer
Copy link
Member

Just adding OS X to the CI, since this should be supported (and it was very easy to add). If this PR fails, then it'll point out some bugs that we have to track down.

@ariporad
Copy link
Contributor

It looks like travis doesn't fully support node on osx out of the box:
travis-ci/travis-ci#2311.
On Sun, Jan 10, 2016 at 9:50 PM Nate Fischer [email protected]
wrote:

Just adding OS X to the CI, since this should be supported (and it was
very easy to add). If this PR fails, then it'll point out some bugs that we

have to track down.

You can view, comment on, or merge this pull request online at:

#283
Commit Summary

  • chore(travis): add OS X to Travis CI

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#283.

@nfischer
Copy link
Member Author

Yup, saw that as soon as I pushed. I'm going to try the steps here (travis-ci/travis-ci#2311 (comment))

@nfischer
Copy link
Member Author

@ariporad This should be ready for review now. Commits are squashed.

This wound up being more changes to the yaml file than I anticipated. It should work very similarly to the previous behavior though. I followed the recommendation from this comment. I changed language to c++ because that gets rid of the automatic nvm commands (and works under both linux and os x).

This makes things look a bit uglier in the yaml file, but perhaps the benefit of testing under os x is worth it.

Also, does this follow the preferred convention for commit messages?

- NODE_VERSION="0.10"
- NODE_VERSION="0.11"
- NODE_VERSION="0.12"
- NODE_VERSION="4.2.4"
Copy link
Contributor

Choose a reason for hiding this comment

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

Two things:

  1. I'd say just change this to 4
  2. Can you add 5, and/or stable?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think it's at 4.2.4 because that's the latest LTS (@arturadib set that up). I'll add a more recent version as well though.

Copy link
Contributor

Choose a reason for hiding this comment

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

@nfischer: I know, but change this from NODE_VERSION="4.2.4" to just NODE_VERSION="4". That way if they do a patch release it will automatically work.

Copy link
Member Author

Choose a reason for hiding this comment

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

@ariporad Finally got around to fixing this. You're right, 4.x.x is a better move going forward. This should be good for review now.

@ariporad
Copy link
Contributor

@nfischer: I made a comment or two, but otherwise looks good. And the commit message is great!

@nfischer
Copy link
Member Author

👍

@nfischer
Copy link
Member Author

@ariporad
I updated travis. The CI will still test under 4.2.4 (I think that's the last LTS) and will now test under 5.0. I think this should be sufficient coverage for node versions on both linux and OS X, so this is ready for review. Let me know if this needs any other changes.

- NODE_VERSION="0.11"
- NODE_VERSION="0.12"
- NODE_VERSION="4.2.4"
- NODE_VERSION="5.0"
Copy link
Contributor

Choose a reason for hiding this comment

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

This should just be 5 (The current version of node is 5.4.1, and that won't match 5.0.

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, I can switch to 5. I wasn't sure if we always wanted to test against the latest release of node (could be somewhat unstable).

Change language to c++ to delay nvm commands until after nvm is installed.
Install steps are explicit to make sure that Travis CI will always have the nvm
package, even on OS X. Changing to Node v4.x.x
@ariporad
Copy link
Contributor

LGTM!

ariporad added a commit that referenced this pull request Jan 16, 2016
chore(travis): add OS X to Travis CI
@ariporad ariporad merged commit b8f110d into shelljs:master Jan 16, 2016
@nfischer nfischer deleted the osx-ci branch January 16, 2016 04:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants