5 ms·

At my talk at the Italian RubyDay on continuous integration I received huge critiques for endorsing a Java solution for ruby CI. My point was that Jenkins was f

At my talk at the Italian RubyDay on continuous integration I received huge critiques for endorsing a Java solution for ruby CI. My point was that Jenkins was far more complete ( at the time of the presentation) of any full ruby stack CI product. This news is a fine Christmas present. This tells me that people clever than me share some of my views

vetler 15y ago
Was the critique valid in any way, or was it just because it was written in Java and not Ruby?
- fullmoon 15y ago
  Which makes it invalid how? Think of a ruby dev team and the wish to extend the CI server?
  - viraptor 15y ago
    These guys did: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+plugin+development+in+Ruby https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+plugin+d... (plugins in JRuby) I don't really get the problem though. Java is trivial to learn for anyone. It's not your main product, it's not going to take a massive amount of time for a single plugin. Just write it and be done...
    - Vitaly 15y ago
      It might be really easy to learn. But after having programmed Ruby for any significant time Java is very unpleasant to program ;) Also just learning basics to do simple customizations is not enough. If something breaks you will not have a slightest idea how to debug and fix. With a Ruby CI server I can just stick a debugger and walk through the code.
  - radicalbyte 15y ago
    > Think of a ruby dev team and the wish to extend the CI server? It's not exactly a show stopper as long as they have the sourcecode. If the team are capable enough to code Ruby and extend the CI server, then they either already know enough Java to do so or can learn it quickly enough to be effective.
- SammyRulez 15y ago
  Mainly yes.. shouts like " Java sxx" " I hate Java". The most relevant may be to resource usage: Jenkins would require more resources than the production machine in mid sized project. But in a world of commodity HW I'don't think this is a real issue
troels 15y ago
> Janky requires access to a Jenkins server Looks like it's based on Java.
espeed 15y ago
"Just use Hudson" (or Jenkins) is generally the sentiment in the Python world too (http://jenkins-ci.org/content/hudson-pycon http://jenkins-ci.org/content/hudson-pycon).
silon3 15y ago
The only problem with Jenkins I have is the use of Java implementation of Subversion, which lags behing the official version.
100k 15y ago
Notable especially because GitHub had their own CI server: CI Joe https://github.com/defunkt/cijoe https://github.com/defunkt/cijoe
- pitra 15y ago
  Scroll to "Does GitHub use cijoe?" > No. We use Jenkins.
  - 100k 15y ago
    "had"

vetler 15y ago

Was the critique valid in any way, or was it just because it was written in Java and not Ruby?

fullmoon 15y ago
Which makes it invalid how? Think of a ruby dev team and the wish to extend the CI server?
- viraptor 15y ago
  These guys did: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+plugin+development+in+Ruby https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+plugin+d... (plugins in JRuby) I don't really get the problem though. Java is trivial to learn for anyone. It's not your main product, it's not going to take a massive amount of time for a single plugin. Just write it and be done...
  - Vitaly 15y ago
    It might be really easy to learn. But after having programmed Ruby for any significant time Java is very unpleasant to program ;) Also just learning basics to do simple customizations is not enough. If something breaks you will not have a slightest idea how to debug and fix. With a Ruby CI server I can just stick a debugger and walk through the code.
- radicalbyte 15y ago
  > Think of a ruby dev team and the wish to extend the CI server? It's not exactly a show stopper as long as they have the sourcecode. If the team are capable enough to code Ruby and extend the CI server, then they either already know enough Java to do so or can learn it quickly enough to be effective.
SammyRulez 15y ago
Mainly yes.. shouts like " Java sxx" " I hate Java". The most relevant may be to resource usage: Jenkins would require more resources than the production machine in mid sized project. But in a world of commodity HW I'don't think this is a real issue

troels 15y ago

> Janky requires access to a Jenkins server Looks like it's based on Java.

espeed 15y ago

"Just use Hudson" (or Jenkins) is generally the sentiment in the Python world too (http://jenkins-ci.org/content/hudson-pycon http://jenkins-ci.org/content/hudson-pycon).

silon3 15y ago

The only problem with Jenkins I have is the use of Java implementation of Subversion, which lags behing the official version.

100k 15y ago

Notable especially because GitHub had their own CI server: CI Joe https://github.com/defunkt/cijoe https://github.com/defunkt/cijoe

pitra 15y ago
Scroll to "Does GitHub use cijoe?" > No. We use Jenkins.
- 100k 15y ago
  "had"