ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Switch CI to Travis (Task #1013)
Finn has planned to discontinue ci.chiliproject.org in the future, I propose we move to TravisCI.
See pull request 191.Caveats wrt. current setup:
- As-is 1.9.3 doesn't work because of some gem (can't remember which) misbehaving and making rake exit with 1 more or less every time, also see this build
- No jruby yet, though I'd propose dropping it altogether until we have someone actively stepping up to support it,
- The unstable and stable branches aren't in there yet, but that's a trivial change.
- Assignee deleted (
- Status changed from Open to Ready for review
I was looking into Ruby 1.9.3 compatibility in CI and from what I have found it could be Shoulda what breaks rake (see e.g. Ruby 1.9.3 breaks rake test) â€“ although I have run into similar problem with Engines. Anyway adding
test-unit dependency have magically fixed 1.9.3 compatibility â€“ http://travis-ci.org/jnv/chiliproject-fit
Maybe the test-unit could be a conditional dependency for MRI 1.9.3?
Yeah, I had seen that, the 'test-unit' thing alleviates the problem but doesn't really solves it. A
rake ci:travis:prepare still outputs at the end:
Started Finished in 0.000226 seconds. 0 tests, 0 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications 0% passed 0.00 tests/s, 0.00 assertions/s
I had already discussed the issue with Holger and he was fine with the solution so I merged the pull request and configured the Travis hook on Github (with my token because Travis doesn't have organization tokens (yet)). The results are here: http://travis-ci.org/chiliproject/chiliproject/
- Status changed from Ready for review to Closed