From: Matt Graham <mdg149@gmail.com>
To: Tim Visher <tim.visher@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Best CI Server for Git?
Date: Mon, 2 Feb 2009 19:42:13 -0500 [thread overview]
Message-ID: <1c5969370902021642v4e8d93djd22d5caa4aa9d1a9@mail.gmail.com> (raw)
In-Reply-To: <c115fd3c0902021258i61a04f74u481ba66c645fe8f5@mail.gmail.com>
On Mon, Feb 2, 2009 at 15:58, Tim Visher <tim.visher@gmail.com> wrote:
> I'm setting up a CI environment for my team and I'm wondering what CI
> Server works best with Git. I'm actively considering Hudson and
> Cruise Control and I'm leaning towards Hudson because of a demo I saw
> Andrew Glover do at my local JUG. It looks like it's not really
> 'officially' supported in either tool…
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. We are currently switching
from Cruise Control to Hudson for reasons related to ease of use.
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
next prev parent reply other threads:[~2009-02-03 0:43 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 [this message]
2009-02-04 19:23 ` Tim Visher
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=1c5969370902021642v4e8d93djd22d5caa4aa9d1a9@mail.gmail.com \
--to=mdg149@gmail.com \
--cc=git@vger.kernel.org \
--cc=tim.visher@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).