From: J. Spence <j3mail-busybox@rearden.com>
To: buildroot@busybox.net
Subject: [Buildroot] continuous integration testing
Date: Thu, 13 Mar 2008 10:31:53 -0700 (PDT) [thread overview]
Message-ID: <20597005.396401205429513354.JavaMail.root@zmail.rearden.com> (raw)
After troubleshooting a few more things with trunk, I'm beginning to think that I need to set up some kind of continuous integration platform so that any other mistakes in checkins trigger a notification.
Does anyone have anything like this already, even in a broken state? I'd rather repair a few squeaky wheels than build the whole cart myself.
This raises a few issues:
* CI notifications could be kind of annoying if they're all sent to the list.
* This will probably include cross-platform regressions as well, which could also be kind of annoying (imagine getting notifications about build problems on totally wacky configurations, like uclibc for itanium).
next reply other threads:[~2008-03-13 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 17:31 J. Spence [this message]
2008-03-13 18:30 ` [Buildroot] continuous integration testing Peter Korsgaard
2008-03-13 18:39 ` John Voltz
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=20597005.396401205429513354.JavaMail.root@zmail.rearden.com \
--to=j3mail-busybox@rearden.com \
--cc=buildroot@busybox.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