From: "Nigel Magnay" <nigel.magnay@gmail.com>
To: "Jakub Narebski" <jnareb@gmail.com>
Cc: "Jeff King" <peff@peff.net>,
"Alex Bennee" <kernel-hacker@bennee.com>,
git@vger.kernel.org
Subject: Re: Automated/Daily build systems supporting git?
Date: Tue, 8 Apr 2008 17:34:11 +0100 [thread overview]
Message-ID: <320075ff0804080934j19f9323s9ff02372af8065eb@mail.gmail.com> (raw)
In-Reply-To: <m3d4p0tlz7.fsf@localhost.localdomain>
I did a simple git plugin for hudson back when I was still learning
about git (it's in the CVS tree) - I've got some changes that need to
be committed to it, but it's working OK for us..
On Tue, Apr 8, 2008 at 4:17 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> Jeff King <peff@peff.net> writes:
>
> > On Tue, Apr 08, 2008 at 03:57:52PM +0100, Alex Bennee wrote:
> >
> > > I'm currently doing some investigation into automated/daily build
> > > systems to track the health of a source tree. There seem to be a number
> > > about but as I'm also looking to move the CVS tree over to git I was
> > > wondering if the denziens of the list knew of any they could recommend?
> >
> > Have you looked at contrib/continuous?
>
> Perhaps Hudson[1] can be made to support Git, as it supports Mercurial
> (via Mercurial plugin).
>
> [1] https://hudson.dev.java.net/
> --
> Jakub Narebski
> Poland
> ShadeHawk on #git
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-04-08 16:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 14:57 Automated/Daily build systems supporting git? Alex Bennee
2008-04-08 14:59 ` Jeff King
2008-04-08 15:17 ` Jakub Narebski
2008-04-08 16:34 ` Nigel Magnay [this message]
2008-04-09 10:31 ` Alex Bennee
2008-04-08 15:22 ` Kristian Høgsberg
2008-04-08 16:12 ` Pascal Obry
2008-04-09 10:39 ` Alex Bennee
2008-04-09 10:51 ` Pascal Obry
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=320075ff0804080934j19f9323s9ff02372af8065eb@mail.gmail.com \
--to=nigel.magnay@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=kernel-hacker@bennee.com \
--cc=peff@peff.net \
/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).