| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Travis still don't have a updated version
|
| |
|
| |
|
|
|
|
|
|
|
| |
As we are not running tests for JRuby on travis this option is not
needed.
For more details check 0e8c04529159522aadbfe4fe71ea3d326df07d52
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This will save Travis some precious resource since it will not need to
run 18 jobs for these Ruby implementations on every push or pull
request.
We do care about these implementations but we should fix the build
locally before having it running on travis. We would love to have
someone working on this but right now it is not our reality.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The bug report templates are now executed from the `ci/travis.rb` when
`GEM` contains `guides`.
I started by creating a `test` task in `guides/Rakefile` to handle this,
but since inline `gemfile` must not be executed with `bundle exec`, that
rake task would not be consistent with others. So I went back by
executing them directly from `Build`.
Use inline Gemfile dependency when reporting gem bugs
|
| |
|
|
|
|
|
| |
The version of SQLite used by Travis is outdated. We need to install a
newer version.
|
|
|
|
| |
This reverts commit 81b42970f02d07ca5007bbce920b489d80172636.
|
|
|
|
| |
This reverts commit 410d246bc0ddabe47f0bf54116be9087bd3d4bda.
|
|
|
|
| |
This reverts commit 9ff901bd3e046b0373b28459269146707b5bf8c9.
|
| |
|
| |
|
|
|
|
| |
See https://github.com/bundler/bundler/issues/3681
|
| |
|
|
|
|
| |
This is required to run https://github.com/rails/rails/pull/19752 successfully.
|
|
|
|
| |
They may be fixed at #19470
|
|
|
|
|
|
|
| |
Travis is green. Let's keep it that way rather than let AJ
languish as a second-class citizen.
This reverts commit 2a6b3e14cff61639978a55f47aea9ff4c8e72758.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The main reason is to make bisect easier.
In some points, we have a lot of git dependencies. Since we don't have
the information of which commit we are referring to, bundler get the
latest commit of the master branch of the dependency. This sometimes
returns a version that is not compatible with Rails anymore, making the
tests fail and the harder to identify the commit that introduced a bug.
Also this will make sure that a contributor will always get a set of
dependencies that are passing with our tests.
In our CI server we delete the lock file to make sure we are always
testing against the newest release of our dependencies.
|
|
|
|
|
| |
We're about a year a way from either project releasing, their
development doesn't need to break our builds for now.
|
|
|
|
|
|
|
| |
Currently, bundling `activerecord-jdbc-adapter`'s master branch seems to
be broken. See jruby/activerecord-jdbc-adapter#614
This commit partially reverts #12107
|
|
|
|
| |
Arel head does not support 1.9 anymore.
|
| |
|
|
|
|
|
| |
Travis recommends a default of 3.
See: http://docs.travis-ci.com/user/languages/ruby/#Default-Test-Script
|
|
|
|
|
| |
Stems from [this comment](https://github.com/rails/rails/pull/18203#issuecomment-68138096) by @robin850
and by the blog post http://weblog.rubyonrails.org/2014/12/19/Rails-4-2-final
|
|
|
|
| |
And also bundler cache
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
We will support only Ruby >= 2.1.
But right now we don't accept pull requests with syntax changes to drop
support to Ruby 1.9.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since we want this flag to be enabled anytime we are running the tests
under JRuby, let's enable this at the Rakefile level so people get the
performance boost on their local checkout.
Moreover, we avoid having to update this particular line anytime the
option changes on the JRuby side.
The only drawback is that we have to define it in every Rakefile but
there's no big deal, this is already the case for other options.
|
| |
|
|
|
|
| |
Ruby 2.2 is near to be released so we should support it properly
|
| |
|
|
|
|
|
|
| |
Continuation of c9a43126c5e2c608ab3ff1be994bce69e815a144
:cry:
|
|
|
|
|
|
|
| |
Currently, Travis CI assumes that the project is in Ruby in the
absence of the `language` key.
This behavior may change in the future. (For example, switch to a "blank"
image which *may* be created.)
|
|\
| |
| |
| | |
Speed up JRuby tests by improving the startup time
|
|/
|
|
|
|
|
|
|
| |
Emulate `jruby --dev` which improves JRuby's startup time.
See
https://github.com/jruby/jruby/wiki/Improving-startup-time#use-the---dev-flag
Follow @headius' idea and give Java more memory to reduce GC time.
|
| |
|
|
|
|
| |
This will make easier to compare run time between Ruby 2.1 and trunk
|
|
|
|
|
|
|
| |
Not sure what's causing them suddenly, but it seems unlikely there's
much we can do about it. For the small amount of coverage this
particular job gains us, it's hurting us more, by making CI failures
unremarkable.
|
|
|
|
| |
This reverts commit 5d2d301024cc0b17f26f6b454ac22a72f1db8a23.
|
| |
|
| |
|
|
|
|
| |
cc http://blog.travis-ci.com/2014-04-28-upcoming-build-environment-updates/
|