From: Alex Riesen <raa.lkml@gmail.com>
To: David Frech <nimblemachines@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: sharing between local "work" and "nightly build" git repos
Date: Fri, 13 Jul 2007 07:11:40 +0200 [thread overview]
Message-ID: <20070713051140.GB2430@steel.home> (raw)
In-Reply-To: <7154c5c60707121733r6584a407r8d60d5890b9c89e2@mail.gmail.com>
David Frech, Fri, Jul 13, 2007 02:33:19 +0200:
> On 7/12/07, David Frech <nimblemachines@gmail.com> wrote:
> >On 7/12/07, Junio C Hamano <gitster@pobox.com> wrote:
> >> Then a nightly update would go like this:
> >>
> >> $ cd ~/nightly-git
> >> $ git pull origin next
> >> $ make clean
> >> $ make test || barf
>
> One more thing: would it make sense to do "make -k test" so that *all*
> failures (if >1) show up?
Yes, definitely. You'll find you will see failures which you know are
already fixed, just didn't reach the nightly-build yet.
BTW, do _not_ send the errors to this mailing list. It just too easy
gets out of control. And consider saving the build log somewhere after
doing a _completely_ clean build, i.e. like this:
#!/bin/bash
cd ~/nightly-git || exit
echo 'Subject: Nightly build git next ' $(date) >/tmp/mail.msg
echo >>/tmp/mail.msg
{
rm -rf * # it does not remove .git
git reset --hard
git pull origin next || exit 1
make || exit 1
make -k test|| exit 1
} &>> /tmp/mail.msg
$ nightly-build || sendmail local-user@localhost < /tmp/mail.msg
It is simplier to find out what went wrong if you know what state did
you have before doing the test. And the state after rm -rf * is very
simple to predict.
next prev parent reply other threads:[~2007-07-13 5:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 23:36 sharing between local "work" and "nightly build" git repos David Frech
2007-07-13 0:03 ` Junio C Hamano
2007-07-13 0:27 ` David Frech
2007-07-13 0:33 ` David Frech
2007-07-13 5:11 ` Alex Riesen [this message]
2007-07-13 18:23 ` Junio C Hamano
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=20070713051140.GB2430@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nimblemachines@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).