Currently none of the core devs uses JRuby (that I know of) and the sole way of knowing what works and not is the CI, and the CI currently has errors for JRuby: http://ci.chiliproject.org/job/chiliproject_master_experimental If you have experience with JRuby, we'd be happy if you could help squash those remaining failing tests and try to support JRuby from there on.

(note that none of the Redmine devs uses JRuby either, at least I don't of any, so there's probably problems with Redmine on JRuby too…)

I had some experience with getting Redmine on JRuby up & running (pretty hard to make it work), so maybe I could help somehow. At first glance, some errors arrear just because of gem version mismatch (encountered this before). So, will try to find some time and fix several issues.

Be sure to make issues for problems you can identify, even if you don't have a fix yet. I think Holger has some previous JRuby experience, he might be able to help and review any patch you submit too.

Well, at least I fought some fights with it :)
But as Felix said, please create issues if you find anything not working as expected / desired.

Some starting pointers for getting ChiliProject towards a production deployment on JRuby are:

• A warbler script for Redmine 0.9 (iirc) which could probably be adapted to work with a current ChiliProject
• A fix for a warble error in ChiliProject which took me 2 hours to figure out and made me hate Rails.

Hello,

I'm trying to make Chiliproject working properly on jruby with a postgresql database.

My settings are : * JDK 1.6.33 x64 * Jruby 1.6.7.2 * Postgresql 8.4.12

• Trouble with activerecord-jdbcpostgresql-adapter v 1.2.2, after reading this post [[http://www.redmine.org/boards/1/topics/19434]], i tried 0.9.7 version, and it solve the first trouble.

I'm thinking, i'm just at the beginning of the road, so i'd like setup my own Jenkins to validate my work.

Could you please, send me the xml config file of your job on Jenkins ?

So i can make it work by my own.

Thanks,

Raphael

Hello Raphael,

I think using Travis might be easier than setting up a full Jenkins, but if you need help with the config, Gregor might be able to help (he was the one who set up ci.chiliproject.org).

Hi Felix,

Thanks for your support,
How can i contact Gregor ?

I added him as a watcher here, he should have gotten mails about the exchange :-)

Hi Raphael,

we are using this script to run the builds on ci.chiliproject.org. It is expecting the proper DATABASE, RUBY, and DATABASE_PASSWORD variables. They are provided via environment vars and matrix builds. I hope this helps you to properly configure your Jenkins.

If you have any other questions, feel free to ask or contact my via mail.

Best

Gregor

Hello Gregor, Felix

I found this post [[http://www.redmine.org/issues/10336]] for redmine, there is a "patch" which fix some trouble with postgresql.

I think we should try this on the Continious Integration of Chiliproject.

Best regards

Raphael MESSNER wrote:

I found this post [[http://www.redmine.org/issues/10336]] for redmine, there is a "patch" which fix some trouble with postgresql.

I think we should try this on the Continious Integration of Chiliproject.

Thanks for the tip. We could maybe start a jruby branch to test fixes there before we merge it to master, Holger, what do you think?

Felix Schäfer wrote:

Raphael MESSNER wrote:

I found this post [[http://www.redmine.org/issues/10336]] for redmine, there is a "patch" which fix some trouble with postgresql.

I think we should try this on the Continious Integration of Chiliproject.

Thanks for the tip. We could maybe start a jruby branch to test fixes there before we merge it to master, Holger, what do you think?

As the patch is to apply directly to the "activerecord-jdbc-adapter-1.2.2" gem, there is no need to fix chiliproject. The easiest way to see the effect is to alter the script bundler_ci.sh, then he can replace the file on ci.chiliproject with jruby and postgresql.

Raphael MESSNER wrote:

As the patch is to apply directly to the "activerecord-jdbc-adapter-1.2.2" gem, there is no need to fix chiliproject. The easiest way to see the effect is to alter the script bundler_ci.sh, then he can replace the file on ci.chiliproject with jruby and postgresql.

"Just replacing" files is a really messy way to fix this, especially in a so "monkey-patching friendly" language as ruby. Furthermore, that wouldn't be an easy fix for people wanting to test it for themselves and would need to be adapted for Travis CI too. The better solution would be to either make a git repo for the adapter with the fix applied to which we can then point the Gemfile, or add a monkey-patch for the adapter to ChiliProject.