On Tuesday 27 February 2007 13:13, Nate Lowrie wrote:
> Thought more about this.  Fact is I need a system that I can use for
> some projects at work that have test suites using PyUnit.  I need
> something like BuildBot, however, I don't really like BuildBot itself.
>  It's clunky, command line based, and requires a lot of setup.  I have
> to create the build master, create the build slaves, launch the
> daemons, schedule the build, configure a rather large amount of
> options in a cryptic config file, and pray to God that all of the
> steps work....
>
> Currently, I am just using cron jobs to run a script that runs the
> test suites every so often and then popping up a message if it fails.
> I need more though.  I need something that's easy to configure through
> a GUI, will set itself up, get the latest SVN working copy, run it
> against unittest test suites and send an email out to developers if
> any of the tests fail.  Shouldn't possibly be that hard but python has
> BuildBot, and Bitten, neither of which has really what I am looking
> for.  Bitten has a GUI but is a pain in the ass to configure and you
> need a trac server running.  Other non-python tools are also a pain
> like CruiseControl and DamageControl.
>
> So, I figured since myself and dabo are in the same boat we can figure
> out a nice solution.  I am going to propose a project called ANTE
> (Automated uNit Test Environment).  GUI in Dabo, auto-configures,
> really easy to add a project to the build list.  I am thinking each
> project only needs the unitest main file path, path to svn repository,
> frequency of build times, and email addresses of people that need to
> be notified.  SVN updates can be called with os.popen(), sending
> emails over smtp is 8 lines of code, unittest files can be run through
> os.popen as well.  Analyze the result is just string comparison.
> Thoughts......I know it just covers unitest and svn but that's all we
> need.
>
> If this does go through, can it be in a repository on dabodev?
>
> Cheers,
>
> Nate L.
>
> On 2/26/07, Nate Lowrie <[EMAIL PROTECTED]> wrote:
> > On 2/26/07, Dabo <[EMAIL PROTECTED]> wrote:
> > > #5: Implement Continuous Integration Testing (BuildBot)
> > > -----------------------+-----------------------------------------------
> > >----- Reporter:  paul      |       Owner:  paul
> > >       Type:  task      |      Status:  new
> > >   Priority:  critical  |   Milestone:  1.0
> > >  Component:  app       |     Version:
> > > Resolution:            |    Keywords:
> > > -----------------------+-----------------------------------------------
> > >-----
> > >
> > > Old description:
> > > > In line with [tracker:4], we must start automatically testing each
> > > > committed revision on all operating systems and reporting the
> > > > results, so that we can respond quickly to introduced bugs.
> > >
> > > New description:
> > >
> > >  In line with ticket:4, we must start automatically testing each
> > > committed revision on all operating systems and reporting the results,
> > > so that we can respond quickly to introduced bugs.
> >
> > see my response for tracker 4 for info about this.
> >
> > > --
> > > Ticket URL: <http://svn.dabodev.com/trac/dabo/ticket/5#comment:1>
> > > Dabo <http://svn.dabodev.com/trac/dabo>
> > > Trac Page for Dabo
> > >
> > >
> > > _______________________________________________
> > > Post Messages to: [email protected]
> > > Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
>
> _______________________________________________
> Post Messages to: [email protected]
> Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
+2
I'm willing to help!  Just tell me where to start!
-- 
John Fabiani

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev

Reply via email to