Hi,
Just to let you know that I did finally get benburket's fork to work
with git. It took a little hacking into what he had, and understanding
git + ssh key auth intricacies, but it's running. If anyone else is
stuck I can share my config..
Regards,
Nicholas
Chad Woolley wrote:
On Thu, Aug 21, 2008 at 3:59 PM, Jeremy Lightsmith
<[EMAIL PROTECTED]> wrote:
actually, the current version of cruise in development does support git. I
believe the fork you're using uses a different strategy for git support than
we do, so there may be some different behavior on corner cases.
The trunk support for git is definitely not ready for prime time. I'm
using it to try to get the Rails CI box up again, and it was just hung
for like a month trying to do a git merge. Had to manually kill the
build and command process.
I've opened several tickets tagged with git, and put a ticket on the
list, no response yet. There have been several other git-related
threads too.
Even worse, benburkert's branch is off the old rubyforge Git repo, and
not a "real" fork of the new github repo for ccrb. I've emailed
benburkert off-list about maybe having him re-fork off the official
one, but got no response. That is bad, because that means his branch
is essentially frozen at the point he branched and not getting any new
stuff.
If I remember, Alexey's original objection to this branch was that
Grit used native calls, and Alexey preferred to just use the command
line to be more cross-platform. So, that is in and sort of working,
but needs a lot more work, obviously. It would be great if someone
stepped up and did that work, and these divergent git forks went away.
Unfortunately, I'm not that person...
-- Chad
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
