git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Visher <tim.visher@gmail.com>
To: Matt Graham <mdg149@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Best CI Server for Git?
Date: Wed, 4 Feb 2009 14:23:13 -0500	[thread overview]
Message-ID: <c115fd3c0902041123j4a16d666r6d1fbb9917184b2a@mail.gmail.com> (raw)
In-Reply-To: <1c5969370902021642v4e8d93djd22d5caa4aa9d1a9@mail.gmail.com>

On Mon, Feb 2, 2009 at 7:42 PM, Matt Graham <mdg149@gmail.com> wrote:

> Hudson leaves a fair amount to be implemented by plug-ins, so not
> being installed out of the box doesn't really imply bad.  I would say
> that there are more significant differences between Hudson and Cruise
> Control than how they integrate with Git.

Makes sense.

> We are currently switching from Cruise Control to Hudson for reasons
> related to ease of use.

Would you mind being a little more specific?  The basics of what I've
heard is that Cruise Control is ultimately much more flexible and
capable, but that Hudson beats it hands down regarding usability and
UI.  What specific issues had your team come up against?

> Here is another hudson/git plugin.  It may not be quite as official
> but addresses issues people have had with the more official one:
> http://github.com/stephenh/hudson-git2

I remember when this was announced.  Unfortunately, I can't find a
clear comparison of the two.  I heard in a recent thread on here that
at least some of the problems being answered by hudson-git2 have been
cleaned up in the latest version of the official plug-in.  Is it still
the case that there are problems in the official one that are fixed in
Stephen's?

Thanks so much for your help! :)

-- 

In Christ,

Timmy V.

http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail

  reply	other threads:[~2009-02-04 19:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 20:58 Best CI Server for Git? Tim Visher
2009-02-02 21:59 ` Jean-Baptiste Quenot
2009-02-03  0:42 ` Matt Graham
2009-02-04 19:23   ` Tim Visher [this message]
2009-02-18 16:47     ` Tim Visher
2009-02-20 10:15       ` Jean-Baptiste Quenot
2009-02-21  4:59         ` Tim Visher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c115fd3c0902041123j4a16d666r6d1fbb9917184b2a@mail.gmail.com \
    --to=tim.visher@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=mdg149@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).