From: "Jean-Baptiste Quenot" <jbq@caraldi.com>
To: git@vger.kernel.org
Subject: Re: Git with Hudson
Date: Mon, 22 Dec 2008 10:34:58 +0100 [thread overview]
Message-ID: <ae63f8b50812220134ibcc400fs4bf29a02828c60d3@mail.gmail.com> (raw)
In-Reply-To: <20081218160734.b1992eb8.stephen@exigencecorp.com>
2008/12/18 Stephen Haberman <stephen@exigencecorp.com>:
>
> 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.
Good idea! I'm also affected by this problem, although the
git-rev-list is not an issue anymore since version 0.5. Simplifying
the checkout() is still in my plans though, so your contribution comes
at the right moment. Once the code will be made available we'll be
able to take the best of the two Git plugins and merge them into one.
WDYT?
--
Jean-Baptiste Quenot
http://jbq.caraldi.com/
next prev parent reply other threads:[~2008-12-22 9:36 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
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 [this message]
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=ae63f8b50812220134ibcc400fs4bf29a02828c60d3@mail.gmail.com \
--to=jbq@caraldi.com \
--cc=git@vger.kernel.org \
/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).