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.
Best Regards,
Gary
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Hi Gary,
Looks like almost entire Ruby world (including JRuby and Rails) has
moved to git.
So it seems only natural for (mostly-)Ruby project to use git. 
Thanks,
–Vladimir
On Fri, Oct 2, 2009 at 11:30 PM, Gary W. [email protected]
wrote:
a few of our projects that use mercurial, branches that get merged into test
projects, and even more Java (Maven2 and Ant) projects. I’m betting that a
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
I work for SeaChange international… a fairly large corporation so
keep that in mind.
We use perforce as our source control. the Merge capabilities are
good. It’s a “decent” source control product. I’ve been using Git to
do the RCov stuff I’ve been doing and I LOVE it.
For CI we use Bamboo. It integrates nicely with Jira (which we use)
and the reporting capabilities are good. We’ve written some scripts
that run our builds and Bamboo picks up the results very well. The
Distributed capabilities (Remote Agents) in Bamboo are great. We have
multiple plans that run the tests, kit up our stuff, generate RCov
documentations etc. Over all I like it!
Jay
On Fri, Oct 2, 2009 at 5:30 PM, Gary W. [email protected]
wrote:
a few of our projects that use mercurial, branches that get merged into test
projects, and even more Java (Maven2 and Ant) projects. I’m betting that a
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
We’ve been using Mercurial, mostly because the windows support is much
better than git, but I don’t think you can go wrong with either of
those.
For CI, we’ve been very happy with Hudson
(https://hudson.dev.java.net/). Active development, open source,
easy install and deployment.
–
Chris
On Sun, Oct 4, 2009 at 10:39 PM, Ikai L. [email protected] wrote:
wrote:
Distributed capabilities (Remote Agents) in Bamboo are great. We have
to use for version control and continuous integration and anything
In
For continuous integration, the team I was on was using Bamboo (pretty
Java/JRuby/Ruby project environment also.
http://xircles.codehaus.org/manage_email
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Jay, I’ve never used Perforce before. It’s funny that you say you like
Git
more because every time I try to evangelize Git to folks who have used
Perforce, their response has kind of been “meh”.
I was disappointed that Google code went for Mercurial and not Git only
because, for whatever reason, installing Mercurial was more difficult
for me
than installing Git. It wasn’t as simple as “port install” and building
it
required me to update Python, easy_install, etc.
Ikai
Ikai,
That’s cuz they’ve never used git bisect 
… for that feature alone
I LOVE git…
Don’t get me wrong. I do like perforce too. But it has some funky
issues with file naming. For example our Perforce server runs on a
windows box and we are in the process of moving to linux. So
capitalization has caused some issues and you just can’t delete and
re-add the file.
Also I find that perforce comes with some pretty nice UI widgets…
Next time you get a “meh” response ask them if they use git on the cmd
line or the UIs? (just curious).
Also perforce doesn’t (yet) have the concept of shelving (or
stashing)… Which I don’t use a ton but everyone I talk to that uses
git mentions it. And I can see the appeal if perforce had that I’d
use it.
Jay
On Sun, Oct 4, 2009 at 10:39 PM, Ikai L. [email protected] wrote:
wrote:
Distributed capabilities (Remote Agents) in Bamboo are great. We have
to use for version control and continuous integration and anything
In
For continuous integration, the team I was on was using Bamboo (pretty
Java/JRuby/Ruby project environment also.
http://xircles.codehaus.org/manage_email
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email