From thewoolleyman at gmail.com  Sun Aug 24 21:41:19 2008
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sun, 24 Aug 2008 18:41:19 -0700
Subject: [Cruisecontrolrb-developers] State of CCRB Git Support
Message-ID: <e3af97510808241841w279f9fbck4f3d179c7097bab3@mail.gmail.com>

I've been working on getting the new Rails CI server up again
(ci.rubyonrails.org), so I've been banging on the git support in
trunk.

Bottom line - it seems to be working pretty well, with the exception
of two major blocker git bugs.

The first one is that no text is shown in the changelog - just the commit GUID:
http://cruisecontrolrb.lighthouseapp.com/projects/9150-cruise-control-rb/tickets/202-changeset-not-showing-up-for-git#ticket-202-3

The second one is that you cannot seem to build a branch other than master:
http://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/206-how-can-you-build-a-branch

There may be others, but I haven't found them.  I will take a shot at
fixing these, since they pretty much blockers for announcing the new
Rails CI server and pointing it at the rails core list again.  If
anyone is inspired to help, that would be great :)

Also, anyone who is using BenBurkert's Grit-based fork (off the dead
rubygems repo), I'd love to hear what features are there which are not
in the trunk command-line-based version, or any bugs which I'm not
aware of.


Finally, here's a recap of the other git tickets.

This one is marked minor - there always seem to be two consecutive
builds when you first add a project:
http://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/204-git-commits-sometimes-cause-two-or-more-builds

These two do not seem to be happening any more, at least in my last
day or so of playing with it, so they should be marked as resolved:
http://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/203-git-builds-not-always-triggered-by-commit
http://cruisecontrolrb.lighthouseapp.com/projects/9150/tickets/205-git-changes-not-being-detected

Thanks,
-- Chad