unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Guile automated builds available
Date: Tue, 12 Aug 2008 09:22:51 +0200	[thread overview]
Message-ID: <87ljz2d7ec.fsf@gnu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]

Hello,

I've installed a daily build process on some of the GCC Compile Farm
Project's machines [0], currently covering 3 architectures (sparc64,
alphaev56 and x86-64), all under GNU/Linux, with different versions of
GCC.  From now on, the build should run at around 3pm UTC every day.
Build logs are sent by mail to Simon Josefsson's Autobuild service [1]
and can be seen here:

  http://autobuild.josefsson.org/guile/

I'm planning to add automated builds on some of HP's Test Drive machines
eventually, but that will require more work as they are behind a very
restrictive firewall (no HTTP, no SSH, etc.).

I use a simple script (attached) that invokes Autobuild's m4 macro [2].
I'm wondering whether it would be a good idea to include it in releases,
and tell people they can run
"./configure && make check | mail guile@autobuild.josefsson.org" so that
we get more build results.

Thoughts?

Thanks,
Ludovic.

[0] http://gcc.gnu.org/wiki/CompileFarm
[1] http://autobuild.josefsson.org/
[2] http://josefsson.org/autobuild/


[-- Attachment #2: The script --]
[-- Type: application/x-sh, Size: 952 bytes --]

             reply	other threads:[~2008-08-12  7:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12  7:22 Ludovic Courtès [this message]
2008-09-10 21:18 ` Guile automated builds available Neil Jerram
2008-09-11 10:21   ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ljz2d7ec.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).