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

Update .travis.yml #341

Merged
merged 1 commit into from
May 12, 2017
Merged

Conversation

junaruga
Copy link
Contributor

  • Updated Rubies to latest version.
  • Added ruby-head as allow_failures.
    Because it's good to know new version Ruby's issue as faster before the release.
  • Added ruby 2.4.1 as allow_failures to share the test failure.
    => Let me try to test 2.4.1 on Travis.

The motivation is same with cucumber/cucumber-ruby#1087 .

@junaruga
Copy link
Contributor Author

junaruga commented May 12, 2017

The result of 1st Travis test.
https://travis-ci.org/cucumber/cucumber-rails/builds/231615503

It looks Rails 4.1 have not supported Ruby 2.4. So, I will exclude the case.
https://github.com/rails/rails/blob/4-1-stable/.travis.yml

Rails 4.2 latest version have supported Ruby 2.4.
https://github.com/rails/rails/blob/4-2-stable/.travis.yml

* Update Rubies to latest version.
* Add ruby-head as allow_failures.
  Because it's good to know new version Ruby's issue as faster before the release.
@junaruga junaruga force-pushed the feature/update-travis branch from baa6a99 to 6ca7efe Compare May 12, 2017 16:38
@junaruga junaruga merged commit d266767 into cucumber:master May 12, 2017
@Kosmas
Copy link
Member

Kosmas commented May 13, 2017

@junaruga thanks.
Could you please update the History.md file next time if needed?

@junaruga
Copy link
Contributor Author

@Kosmas If you like, I will be able to update History.md for this PR.
When I checked the file yesterday, I thought that only important features and bugs were updated in case of cucumber-rails.

@junaruga
Copy link
Contributor Author

@Kosmas you have already updated it . Thank you for that!

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.

2 participants