I know this is fairly off-topic from JRuby itself, but am curious what
the “norm” is for most environments developing JRuby (and/or Ruby)
applications to use for version control and continuous integration and
anything new(er) that we should look into.
We use subversion, mercurial, and git locally and are currently trying
to decide between mercurial and git after working with them for a while.
We had a (very) brief team discussion earlier this afternoon after our
standup where the main two points were that mercurial’s merge wasn’t as
good as git’s but git has produced some sticky issues when something
went wrong. In a few of our projects that use mercurial, branches that
get merged into test can stay there a good while (months) in some cases
waiting on approval where other tickets pass through to production
quickly, so we’re really looking for something that would work best in
that type of environment. Mercurial is ok for that, but as I said, the
merging isn’t always that great.
For continuous integration, the team I was on was using Bamboo (pretty
sweet, and would continue to use if we could), the team my old team
merged into over a year ago has been using cruisecontrol.rb mostly (some
playing with Integrity, but not much), and we’re re-evaluating our tools
at the moment. We primarily have JRuby (+/- Rails) projects, Ruby on
Rails projects, and even more Java (Maven2 and Ant) projects. I’m
betting that a number of people on the JRuby list might be in the same
situation in a mixed Java/JRuby/Ruby project environment also.
Anyway, I just thought I’d throw it out there to see what people
thought. Thanks in advance for any thoughts or advice.
To unsubscribe from this list, please visit: