| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
- Specify we want to run on latest stable ruby for mariadb
- change in runs of builds
Make mariadb? method publicly available
|
|
|
|
|
|
|
|
|
| |
yahonda/use_newer_version_of_sqlite3_at_travis_ci"
This reverts commit a3d085a4ce949526cd388d6b399347504d9a0c92, reversing
changes made to e2df1c6d2aa1dd667c6c1be25d5c7f7d69f293fa.
It broke the build
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Uses latest precompiled JRuby so that
we don't spend time downloading versions Travis has
not already compiled. http://rubies.travis-ci.org/
Uses latest jdk: oraclejdk8
per
https://docs.travis-ci.com/user/build-environment-updates/2015-02-03/#Ruby-VM
and
https://docs.travis-ci.com/user/languages/ruby/#Supported-Ruby-Versions-and-RVM
Follows on work in https://github.com/rails/rails/pull/23927 which was reverted
https://github.com/rails/rails/commit/26fe5fa08d52384bcea09c4210e3b3baaf5e9b95
JRUBY_OPTS minimize GC, disable JIT, for max test speed
- https://github.com/rails/rails/pull/16613
- https://github.com/rails/rails/pull/17088
Have Rails use JRuby-compatible Rake 11.1
- The Rake task was passing --verbose, an invalid option, to contemporary JRuby
- https://github.com/ruby/rake/pull/120
- https://github.com/rails-api/active_model_serializers/pull/1585
- https://github.com/jruby/jruby/issues/3653#issuecomment-195883717
No advantage to directly mounting JRuby over installing from cache; both on S3
- https://github.com/rails/rails/pull/23499/commits/b2d5b336b5a812009444571b22eed90777cd9a8c
- https://github.com/rails/rails/pull/23499/commits/f4fad041b2755d81e82ee3fc66d96f334b4653db
|
|\
| |
| | |
Support faye-websocket + EventMachine as an option
|
| | |
|
|/
|
|
|
|
|
|
| |
This reverts commit ddb7be50e8a0946d29fbe66537f845b8369413b7, reversing
changes made to ee4a1462e97f26bd480352468efab5b9c18aa8de.
Reason: It is givin us a lot of timeouts in travis because JRuby 9.0.5.0
needs to be build in every run
|
|
|
|
| |
These are green on local. Checking to see they pass on travis too!
|
| |
|
|
|
|
|
| |
Travis CI now select the latest patch version of Ruby automatically when
given MAJOR.MINOR version string.
|
| |
|
| |
|
|
|
|
| |
Now available - https://docs.travis-ci.com/user/using-postgresql/
|
| |
|
| |
|
|\
| |
| | |
Merge Action Cable into master
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
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
|
| |
|
| |
|