unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: Ted Zlatanov <tzz@lifelogs.com>, emacs-devel@gnu.org
Subject: Re: buildbot setup
Date: Sun, 04 Jul 2010 23:26:29 +0200	[thread overview]
Message-ID: <jwv39vzyws5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87iq4zbz5f.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Thu, 01 Jul 2010 13:32:12 +0900")

> We don't currently have any users with requirements like Alan
> Mackenzie's, but if we did I'd simply keep track of potentially
> destabilizing commits, and tag the last version before one of those.
> That might not work so well with Emacs, though.  XEmacs has a very few
> large committers whose stuff comes in batches, while others don't tend
> to commit patches to areas that might break the build.  I gather Emacs
> has several committers working in areas with some risk of breaking the
> build, so it might not be so easy to choose an apparently stable
> version.

There's indeed some difficulty figuring out when a bootstrap is needed,
as well as how to make sure "make bootstrap" works reliably.

I think the need for bootstrap increases if you update less often
(i.e. if you update everyday, you may never need to bootstrap, whereas
if you update every month you may have to bootstrap every time).

So maybe the buildbot could do a "checkout last bootstrap-tag",
then update and try "make"; if that succeeds, move the tag; else try
again with "make bootstrap" if that succeeds, then add some flag
somewhere indicating that this revision needs a bootstrap and move both
the tested-tag and the bootstrap-tag.

> If you could automatically tag based on green buildbots, that might be
> a worthwhile alternative, though.

I don't know what are green buildbots.


        Stefan



  reply	other threads:[~2010-07-04 21:26 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13  9:16 Bash scripts in black and white Angelo Graziosi
2010-05-14 12:16 ` Thierry Volpiatto
2010-05-14 19:29 ` Stefan Monnier
2010-05-14 19:58   ` Thierry Volpiatto
2010-05-14 21:23   ` Angelo Graziosi
2010-05-14 22:40     ` Lennart Borgman
2010-05-15  5:30       ` joakim
2010-05-15 13:56       ` Stefan Monnier
2010-06-27 14:21         ` Christian Ohler
2010-05-15  6:33     ` Eli Zaretskii
2010-05-15  8:15       ` Angelo Graziosi
2010-05-15  9:12         ` Juanma Barranquero
2010-05-15  9:20           ` Angelo Graziosi
2010-05-15  9:34             ` Juanma Barranquero
2010-05-15 11:43               ` Angelo Graziosi
2010-05-15  9:51       ` Leo
2010-05-15 12:11         ` Eli Zaretskii
2010-05-15 12:49           ` martin rudalics
2010-05-15 13:05             ` Leo
2010-05-15 17:12               ` Romain Francoise
2010-05-16 18:38                 ` Ken Raeburn
2010-06-24 17:58                 ` Ted Zlatanov
2010-06-24 22:11                   ` Stefan Monnier
2010-06-25  5:18                     ` Thierry Volpiatto
2010-06-26 22:23                       ` Stefan Monnier
2010-06-27  5:09                         ` Thierry Volpiatto
2010-06-30 18:26                     ` buildbot setup (was: Bash scripts in black and white) Ted Zlatanov
2010-06-30 18:39                       ` Lennart Borgman
2010-06-30 19:06                         ` buildbot setup Ted Zlatanov
2010-06-30 21:34                           ` Lennart Borgman
2010-07-01 13:00                             ` Ted Zlatanov
2010-07-01 13:08                               ` Lennart Borgman
2010-07-01  1:43                       ` Stefan Monnier
2010-07-01  4:32                         ` Stephen J. Turnbull
2010-07-04 21:26                           ` Stefan Monnier [this message]
2010-07-04 22:56                             ` joakim
2010-05-15 10:36     ` Bash scripts in black and white Thierry Volpiatto
2010-05-17 19:45     ` Stephen Eilert

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/emacs/

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

  git send-email \
    --in-reply-to=jwv39vzyws5.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=stephen@xemacs.org \
    --cc=tzz@lifelogs.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).