From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from deliverator2.gatech.edu (deliverator2.gatech.edu [130.207.160.69]) by huchra.bufferbloat.net (Postfix) with ESMTP id 21295201A44 for ; Tue, 26 Apr 2011 08:37:25 -0700 (PDT) Received: from deliverator2.gatech.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 309FC480FD5; Tue, 26 Apr 2011 11:37:42 -0400 (EDT) Received: from mail3.gatech.edu (mail3.gatech.edu [130.207.185.163]) by deliverator2.gatech.edu (Postfix) with ESMTP id 7E946480F74; Tue, 26 Apr 2011 11:37:41 -0400 (EDT) Received: from [10.10.2.209] (unknown [209.118.182.194]) (Authenticated sender: nf21@mail.gatech.edu) by mail3.gatech.edu (Postfix) with ESMTPSA id C851C149258; Tue, 26 Apr 2011 11:37:40 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=iso-8859-1 From: Nick Feamster In-Reply-To: Date: Tue, 26 Apr 2011 08:37:36 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <437483DB-4EBD-4476-953A-8E086FEF45A1@cc.gatech.edu> References: To: Dave Taht X-Mailer: Apple Mail (2.1082) Cc: bismark-devel@lists.bufferbloat.net Subject: Re: [Bismark-devel] some thoughts on continuous builds X-BeenThere: bismark-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: BISMark related software development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 15:37:26 -0000 Hi Dave, On the topic of builds, I met with some of the OpenFlow folks at = Stanford yesterday. We are going to try to see if we can get this also = built as a package: http://www.openflow.org/wk/index.php/OpenFlow_1.0_for_OpenWRT at which point, we will see if we can integrate it into the build, as = well. Are you saying below that we should be doing continuous testing and = builds, so that we can be certain that the current build runs on the = NetGear hardware? That seems like a good idea. -Nick On Apr 26, 2011, at 8:35 AM, Dave Taht wrote: > The advantage of a continuous build and test system is that you catch > new bugs early, as they occur in your external trees, and also fold in > fixes to existing bugs and new features quickly. >=20 > A disadvantage is that new bugs occur and invalidate previous testing. >=20 > At some point in the near future we will need to freeze bismark, > starting with the kernel and core utilities, do extensive QA, and > ship. Until then, builds should be done weekly (preferably daily) >=20 > Up until now I have been doing pulls and builds on a rather arbitrary = schedule. >=20 > In my judgement there are still sufficient bugs outstanding >=20 > http://www.bufferbloat.net/projects/bismark/issues >=20 > to be doing continuous builds but I haven't been in the loop this week > (I will be more available after may 1) >=20 > So I would like to establish a process whereby we have a trigger point > for doing a new major build, and trigger points for new minor ones. >=20 > One nice thing about having multiple builders is that it's possible to > at least test the new stuff before committing to using it on other > people. >=20 > For example, last night, on my own tree, in my home dir, I did the = usual >=20 > cd ~/src/openwrt; git pull >=20 > # looked over the logs with git log, saw a few interesting changes >=20 > cd ~/src/wndr370 >=20 > ./scripts/feeds update # this updates the external packages and rarely > breaks anything > git pull # in my case this pulls from my private copy of openwrt > make menuconfig # and save. you have to do this fairly often as > options do change > echo make -j 8 | batch >=20 > And the latest and greatest stuff did, indeed, build. Now, (due to me > not paying attention this week) I am still a bit out of sync with > what's going on in the core ~bismark tree, and don't have the hardware > to test against right now, but I have a reasonable confidence level > that the main trees could be updated and built against. >=20 > So, anyway, whenever y'all get to a good "do a complete build" point, > please do so? The pain you incur now will be saved later. >=20 > (I hope to be testing a new build w/hardware saturday) >=20 > --=20 > Dave T=E4ht > SKYPE: davetaht > US Tel: 1-239-829-5608 > http://the-edge.blogspot.com > _______________________________________________ > Bismark-devel mailing list > Bismark-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bismark-devel