git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Haberman <stephen@exigencecorp.com>
To: Indy Nagpal <indy@strakersoftware.com>
Cc: git@vger.kernel.org
Subject: Re: Git with Hudson
Date: Thu, 18 Dec 2008 16:07:34 -0600	[thread overview]
Message-ID: <20081218160734.b1992eb8.stephen@exigencecorp.com> (raw)
In-Reply-To: <D2F0F023-862A-4BAB-88B9-BFEFC5592D10@strakersoftware.com>


> However, before we do that I wanted to check if anyone has had any
> experience/feedback in integrating Git with Hudson CI server?

We tried using the Hudson git plugin that you can download from the
Hudson site and ended up with problems--whether we had too many branches
or something, the plugin has some funny "figure out what needs to be
built" logic that issued near-constant git rev-list commands. To the
point where our own "git fetch" calls would get starved for 20-30
seconds.

We eventually wrote our own Hudson git plugin that is simpler and
doesn't do any funny rev-listing/walking. It just stores last hash
built and rebuilds once that doesn't match the branch tip. Once that
was in place, it worked great.

I've got permission to publish it if you're interested--just haven't
yet.

- Stephen

  reply	other threads:[~2008-12-18 22:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18 19:23 Git with Hudson Indy Nagpal
2008-12-18 22:07 ` Stephen Haberman [this message]
2008-12-19  1:58   ` Tim Visher
2008-12-23  3:00     ` Stephen Haberman
2008-12-24 20:59       ` R. Tyler Ballance
2008-12-24 21:04         ` Stephen Haberman
2008-12-22  9:34   ` Jean-Baptiste Quenot
2008-12-19  4:58 ` Dilip M

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=20081218160734.b1992eb8.stephen@exigencecorp.com \
    --to=stephen@exigencecorp.com \
    --cc=git@vger.kernel.org \
    --cc=indy@strakersoftware.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).