From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.infrascan.de ([188.40.84.136] helo=infrascan.de) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1PJPZo-0004gA-HW for openembedded-devel@lists.openembedded.org; Fri, 19 Nov 2010 12:56:27 +0100 Received: from [192.168.178.20] (77-22-235-200-dynip.superkabel.de [77.22.235.200]) by email.infrascan.de (Postfix) with ESMTPSA id ECE241B40D for ; Fri, 19 Nov 2010 12:56:31 +0100 (CET) Message-ID: <4CE665A6.90602@sensortherm.de> Date: Fri, 19 Nov 2010 12:55:18 +0100 From: Klaus Schwarzkopf User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10 MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <4CE64779.3020802@sensortherm.de> In-Reply-To: X-SA-Exim-Connect-IP: 188.40.84.136 X-SA-Exim-Mail-From: schwarzkopf@sensortherm.de X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on discovery X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: Yes (on linuxtogo.org) Subject: Re: buildserver X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 11:56:29 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Am 19.11.2010 11:42, schrieb Yury Bushmelev: > 2010/11/19 Klaus Schwarzkopf: >> Hi, >> >> i have some problems with the ti recipes, see my emails on the list. >> >> The two problems are: >> * the recipes are out of date and don't work. >> * the recipes can't download the source files. >> >> My idea is, to have an buildserver. On every commit (every night or every >> week), the buildserver download the sources and build the recipe. > > For which DISTRO/MACHINE and image should it build? :) > What to do with commits while building is in process? > What to do with non-recipes commits (classes, conf, contrib) > >> If the server builds the recipe successful, it copy the source files to the >> webserver. >> >> If the builds fails, the person how committed the recipe recieve a email >> with the log files. >> >> What do you think about my idea? > > Just remember that OE have a lot of distros, machines and images. > Ideal case is to test all combinations, but, let's try to imagine how > long this will be. > > We have following number of distros, machines and images: > $ ls conf/distro/*.conf | wc -l > 32 > $ ls conf/machine/*.conf | wc -l > 297 > $ ls recipes/images/*.bb | wc -l > 99 > > My testbuilder (phenom II x6) is building one image in about 2 hours. > So, 32 * 297 * 99 * 2 = 1881792 hours. It is about 214 years if I > calculate right. Well, cluster of 32 alike machines can reduce this > time to 6 years :) > OK, it takes a long time ;-) > It would be great to have buildserver that will rebuild some most > frequently used combinations once per day. Probably, qemu machines + > automated testing under qemu. > Or even create some distributed build system (buildbot?) with server > (should give tasks to clients) and clients (should build tasks given > by server). Good idea. > > Other good idea is to have sanity checker running once per day too. It > may do next things: > - check recipes syntax > - check thath recipes SRC_URI can be fetched > - check recipes for security flaws (we have tool already) > - ... > - PROFIT! :) (sorry, just can't not to write this :) > Even better idea! Is it a problem (webspace, license) to host then the source files on project webspace?