From bloodhound-dev-return-181-apmail-incubator-bloodhound-dev-archive=incubator.apache.org@incubator.apache.org Fri Feb 10 14:11:38 2012 Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 30B919C91 for ; Fri, 10 Feb 2012 14:11:38 +0000 (UTC) Received: (qmail 37938 invoked by uid 500); 10 Feb 2012 14:11:38 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 37913 invoked by uid 500); 10 Feb 2012 14:11:37 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 37905 invoked by uid 99); 10 Feb 2012 14:11:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2012 14:11:37 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of olemis@gmail.com designates 74.125.82.175 as permitted sender) Received: from [74.125.82.175] (HELO mail-we0-f175.google.com) (74.125.82.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2012 14:11:33 +0000 Received: by werc1 with SMTP id c1so2040693wer.6 for ; Fri, 10 Feb 2012 06:11:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=mAyaVcGVkePXUah8CeXY7VWRMLHWlcB7KgKhu8lJnUk=; b=RqJTnjLybVYklDPPDUrHGpt47wzBE3Gj051taOmv6a2ucSalmNPKzGnQ4Vp5nQ5ZcY eE1vYNXiqCz8fZTBiQvxTSEOzWkIKIGvozeA4nu7O8g71CoePrehuyvwGm3HOCahz08h iK6gcEjba8H8CxD15BMtaX1t96C4xzImLzouU= MIME-Version: 1.0 Received: by 10.216.132.214 with SMTP id o64mr842984wei.26.1328883072426; Fri, 10 Feb 2012 06:11:12 -0800 (PST) Received: by 10.223.73.208 with HTTP; Fri, 10 Feb 2012 06:11:12 -0800 (PST) In-Reply-To: <056f01cce7bc$3ee51450$bcaf3cf0$@16degrees.com.au> References: <01c101cce06d$69edc8f0$3dc95ad0$@16degrees.com.au> <4F2FC07C.7040302@wandisco.com> <056f01cce7bc$3ee51450$bcaf3cf0$@16degrees.com.au> Date: Fri, 10 Feb 2012 09:11:12 -0500 Message-ID: Subject: Re: Catching up From: Olemis Lang To: bloodhound-dev@incubator.apache.org, gavin@16degrees.com.au Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Hi ! On Fri, Feb 10, 2012 at 1:21 AM, Gavin McDonald wr= ote: > > > -----Original Message----- > > From: Olemis Lang [mailto:olemis@gmail.com] > > Sent: Monday, 6 February 2012 11:25 PM > > To: bloodhound-dev@incubator.apache.org > > Subject: Re: Catching up > > > > On Mon, Feb 6, 2012 at 6:58 AM, Gary wrote: > > > [...] > > > > > > I believe that Buildbot and Jenkins are the readily available choices. = It > would > > be nice to have a solution that Trac/Bloodhound would be able to integr= ate > > with but it is not a strict necessity. > > > > > > > http://trac-hacks.org/wiki/BuildbotPlugin > > http://trac-hacks.org/wiki/TracBuildbotIntegration > > https://github.com/rbosetti/trac-buildbot-watcher > > Not sure we need any of that at this stage just to check if code from svn > will build. > ok . that was JFTR ;) > > > > > If you ask me ... I'd rather go for Jenkins (... but mainly because I'm > more > > familiar with it ;) > > > > https://wiki.jenkins-ci.org/display/JENKINS/Trac+Plugin > > https://wiki.jenkins-ci.org/display/JENKINS/Trac+Publisher+Plugin > > http://trac-hacks.org/wiki/HudsonTracPlugin > > Again, that might or might not come later, I'm more concerned with genera= l > CI > build stuff rather than integration. Integrating our CI systems with a > development > instance is not my idea of fun at the moment. Let's stick to just making > sure the > code passes our build tests. > ok . Below I mention general (tactic | strategic) decisions I (always) make regarding testing + CI of Python / Trac projects ;) So far JFTR . With time I hope this will be improved . - Tests are run using setuptools test command =A0=A0* Functional dependencies (libraries, ...) are declared in setup.py =A0=A0 =A0`install_requires` , so should be installed automatically =A0=A0* Libraries needed for testing purposes are declared in =A0=A0 =A0`tests_require`=A0so should be installed automatically every time =A0=A0 =A0setuptools `test` command is executed =A0=A0* Lightweight test cases & infrastructure (e.g. mock objects , =A0=A0 =A0no physical Trac environment required , in-memory =A0=A0 =A0Trac database sqlite::memory: , ... ) =A0=A0* The subset of the tests defined in an specific module can be run =A0=A0 =A0 using -m option =A0=A0* For CI (at least using Jenkins ;) it's necessary to generate =A0=A0 =A0JUnit XML report . This will be possible by adding a library =A0=A0 =A0supporting this (e.g. unittest-xml-reporting [1]_ ) and selecting= the =A0=A0 =A0test runner using -r option of=A0setuptools=A0test command . e.g. in general , in order to run the test suite it will only be needed to execute a command similar to {{{ #!sh $ python setup.py test -r -m }}} at least that's the idea ;) ... like I said this is JFTR . I know you'll need to have code + tests so as to play with it ;) BTW . Tests are implemented in Dashboard plugin . I often don't see the need for testing a theme , but it's possible to have e.g. some twill-fu in there so as to make some assertions ;) > > > At this point there is still no real code in the repositories to for = CI > to test and > > so I think that it would be good if we could ask Olemis to contribute h= is > work > > on the theme and dashboard to the svn repositories. That will also have > the > > advantage that everyone can play with his code and contribute patches > back. > > I'm hoping to get some code down in there too shortly. > > what about a main core dump, are we going to get a specific tag of the tr= ac > instance > in svn to get going with? > I guess that should be the case if patches will be applied on top of Trac distribution (and some facts make me think that's what's going to happen ... at some point in the future ;) If this is the case then IMO it'd be nice to have a build job to run Trac test suite ensure those patches don't break the test cases in there ... > > > > In there you'll find a few test cases , With time I can provide > instructions so as > > to run the test suite (or part of it ;) , especially in a CI environmen= t . > During > > this week I'll also try to do the same thing @ testrun.org (Jenkins / > Hudson) ; > > just to satisfy my curiosity and try to be at least a bit accurate > sometimes ;) > > From my perspective, I don=92t mind which we use. I will set up a Buildbo= t > build > once I know what the tests are. I will also do the same for our Jenkins > instance, though > once that is up I tend to leave that for other committers to then > tweak/play/lookafter. > ok .. [1]=A0PyUnit-based test runner with JUnit like XML reporting =A0=A0 =A0 =A0 =A0(http://pypi.python.org/pypi/unittest-xml-reporting/1.0.3= ) -- Regards, Olemis Facebook =3D>=A0http://www.facebook.com/olemis Twitter =3D>=A0http://www.twitter.com/olemislc=A0(@olemislc) Blog ES =3D> http://simelo-es.blogspot.com Blog EN =3D> http://simelo-en.blogspot.com Quora =3D>=A0http://www.quora.com/olemis Youtube =3D> http://youtube.com/user/greatsoftw Featured article : Identificando n=FAmeros primos con expresi=F3n regular e= n Perl http://feedproxy.google.com/~r/simelo-news/~3/BHr859OSndo/identificando-num= eros-primos-con.html Tweet: yo no puedo creer q haya pasado inadvertido el 1/2/12 12:12 ... @elainediaz2003 no dijo na' ... OMG ! ... much more coming soon ;) #fb Follow @olemislc Reply Retweet =A0=A012:59 Feb-01 =A0=A0Get this email app! Get a signature like this. CLICK HERE.