[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pyamf-tickets
Subject:    [pyamf-tickets] #255: Setup GAE buildslave
From:       tickets () pyamf ! org (PyAMF list for bug and patch messages)
Date:       2008-09-23 17:31:37
Message-ID: 042.5d4dce2e0176dcf535c798502ef93adf () pyamf ! org
[Download RAW message or body]

#255: Setup GAE buildslave
----------------------+-----------------------------------------------------
  Reporter:  thijs    |       Owner:  thijs   
      Type:  task     |      Status:  accepted
  Priority:  major    |   Milestone:  0.4     
 Component:  Testing  |     Version:  0.3     
Resolution:           |    Keywords:          
----------------------+-----------------------------------------------------
Changes (by thijs):

  * owner:  nick => thijs
  * status:  reopened => accepted


Comment:

 Replying to [comment:9 nick]:
 > The client script defaults to http://ae.pyamf.org/punit however it would
 be better to be able to test the most recent commit as the other
 buildslaves do. To this end the buildslave should spawn a gae process with
 punit installed, run the client script against that process and then
 report the outcome.

 And it looks like you added [source:pyamf/sandbox/nick/test_gae.py at 1696]
 this script for that. Will check it out.

-- 
PyAMF - Ticket URL: <http://pyamf.org/ticket/255#comment:10>

[prev in list] [next in list] [prev in thread] [next in thread]