From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: buildbot setup (was: Bash scripts in black and white) Date: Wed, 30 Jun 2010 13:26:12 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87eifo9y2j.fsf_-_@lifelogs.com> References: <4BEBC372.5010402@alice.it> <4BEDBF5C.1040306@alice.it> <838w7lfzdo.fsf@gnu.org> <831vddfjp9.fsf@gnu.org> <4BEE984A.4090005@gmx.at> <87eihd143p.fsf@elegiac.orebokech.com> <8739wcjosg.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1277922396 17902 80.91.229.12 (30 Jun 2010 18:26:36 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 30 Jun 2010 18:26:36 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 30 20:26:34 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OU1zV-0004xB-3j for ged-emacs-devel@m.gmane.org; Wed, 30 Jun 2010 20:26:34 +0200 Original-Received: from localhost ([127.0.0.1]:47936 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OU1zU-0000n2-A5 for ged-emacs-devel@m.gmane.org; Wed, 30 Jun 2010 14:26:32 -0400 Original-Received: from [140.186.70.92] (port=55316 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OU1zN-0000mx-Qf for emacs-devel@gnu.org; Wed, 30 Jun 2010 14:26:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OU1zM-0003Yw-Js for emacs-devel@gnu.org; Wed, 30 Jun 2010 14:26:25 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:35145) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OU1zM-0003Y8-6F for emacs-devel@gnu.org; Wed, 30 Jun 2010 14:26:24 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1OU1zK-0004os-5B for emacs-devel@gnu.org; Wed, 30 Jun 2010 20:26:22 +0200 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 30 Jun 2010 20:26:22 +0200 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 30 Jun 2010 20:26:22 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 32 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:EIJ62OJBLyla/e9xGN+blSbDzTk= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:126541 Archived-At: On Fri, 25 Jun 2010 00:11:11 +0200 Stefan Monnier wrote: RF> I'm adding Ted to Cc since he expressed interest in setting up a RF> buildbot for Emacs the last time this subject came up. >> I'm adding this to my TODO list and will have one up soon-ish. I don't >> think I can do the VCS integration that Stefan suggested without some >> help, though. I don't know what he meant by "update a branch" when a >> build is successful. SM> After "bzr update; compile&test", if the "test" (which might just be to SM> check that it compiles successfully) succeeds, do "bzr push " SM> where the could be sftp://bzr.sv.gnu.org/srv/bzr/emacs/tested SM> So we could tell people to use to checkout the latest SM> successfully tested version of the code. I'm not crazy about using a branch to announce a build success. Are developers then supposed to track two branches? Or are users going to track the tested branch but developers the trunk? What happens if there's a tracking failure, do I need to manually fix it ASAP? How do we test multiple platforms and coordinate a push when they are all successful? Or do we keep a separate "tested" branch for each platform and library combination, which makes it even more fun and amplifies each of the issues listed so far? I think it's better and less confusing to simply announce failures through another channel, perhaps as bugs. Then silence will be the default, which is good for everyone, and builds will not have any effect on the repository. Ted