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

[TASK] Configure Travis for better performance #10

Merged
merged 1 commit into from Jan 5, 2015
Merged

Conversation

oliverklee
Copy link
Collaborator

  • Set sudo: false. This allows Travis to use the new container-based
    infrastrukture, which should speed up the builds.
  • Enable bundler caching.

Closes #9

* Set sudo: false. This allows Travis to use the new container-based
  infrastrukture, which should speed up the builds.

* Enable bundler caching.

Closes #9
@oliverklee
Copy link
Collaborator Author

It looks like the build fails with the latest Rails version. We should use Appraisal for builds with different Rails versions.

@oliverklee
Copy link
Collaborator Author

I have just created issue #11 for this.

@lwe
Copy link
Owner

lwe commented Dec 22, 2014

It looks like the problem is actually only in the tests and the test_helper.rb mainly, basically changing Rails = Object.new to Rails = Module.new fixes this error. However it appears that starting with Rails 4.2 the tests are no longer run, I suppose there's an incompatibility with ActiveSupport::TestCase or something like that.

@oliverklee
Copy link
Collaborator Author

So it looks like we should add an Appraisal configuration first (#11), test with different Rails versions and fix any problems, and then continue with this PR.

@lwe
Copy link
Owner

lwe commented Jan 2, 2015

Yes, totally agree.

@oliverklee
Copy link
Collaborator Author

Done in #19.

lwe added a commit that referenced this pull request Jan 5, 2015
[TASK] Configure Travis for better performance
@lwe lwe merged commit 9d9e81e into master Jan 5, 2015
@lwe lwe deleted the task/travis-config branch January 5, 2015 07:20
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.

Use the container-based infrastructure
2 participants