Hi Niklaus, please see my comments inline:
On Tuesday, May 1, 2012 at 1:07 PM, Niklaus Giger wrote: > Hi > > I got frustrated that usinge jruby there were a lot of rake target not > working > in my buildr checkout. > > Therefore I invested some time to fix the problem. Please look at my patch > under https://github.com/apache/buildr/pull/5 > > I haven't tried it but it looks good. We can't accept pull requests but if you attach it as a patch in jira and check that you give copyright to the ASF it should be ok. > > Also I did set up some CI builds on my jenkins, where you can see the results > without my patch under http://ngiger.dyndns.org/jenkins/job/buildr-matrix/ > and from my fork under http://ngiger.dyndns.org/jenkins/job/buildr-matrix- > ngiger/ > > The RSpec results are not too bad. Usually just 3 or 4 failures of over 2200 > examples, e.g. http://ngiger.dyndns.org/jenkins/job/buildr-matrix- > ngiger/Rake_Target=spec,rubies=ruby-1.9.2-p320/ws/_reports/specs.html > > That's not good at all :) All specs must pass for a release to be made so it usually gets done at some point. We are lagging behind there. > > The Jenkins build for buildr.apache.org at https://builds.apache.org/ seem a > bit outdated, and I think a matrix based build as in my example is quite nice > to read and could be an inspiration to update the buildr at > https://builds.apache.org/ > > It's completely outdated. The jenkins server is very hard to maintain and we historically made it work, though it became very quickly a hassle. We need to move out from there and find a better strategy. We don't have resources to host a jenkins instance at this point. If you feel like taking this part over, that would be most awesome. > > My Matrix build misses tests on different platforms, mainly because I don't > have enough CPUs/RAM to run the tests also under Windows and MacOSX. > > It's better than what we have. > > > Regards > > Niklaus
