[Open-bio-l] Automated testing server; was [BioRuby] tutorial

[Chris Dagdigian]

Our cloud servers are running on tiny T1.micro slice EC2 server 
instances which have between 1-2 CPUs at any given time and about 768MB 
of RAM.

For OBF these are the most reasonable priced systems, I don't even want 
to step up to the m1.small servers because at .8 to .10 cents an hour 
the costs gets somewhat pricy compared to what I can scrounge for VMs 
and "donate" to OBF. That said though if OBF wanted to purchase a 
reserved instance or two we could get the price down significantly.

testing.open-bio.org may not have enough power to run the Tomcat stack + 
Maven.

That said though, I have access to VMs and resources outside of the 
cloud and it's trivial to add new ones, especially for systems that do 
not need a front-facing internet IP address.

I also like the HTTP redirect option, that seems reasonable to do as well.

Anyway OBF can always fire up more cloud instances but since that costs 
money the request needs go through the OBF Board.
-dag





Peter Cock wrote:
> On Fri, Mar 4, 2011 at 5:14 PM, Andreas Prlic<andreas at sdsc.edu>  wrote:
>>> You mean it runs the unit tests itself? Hmm - that may not fit with
>>> type of Amazon machine Chris D is renting for testing.open-bio.org
>>> (buildbot doesn't do any heavy lifting - a separate pool of slaves
>>> run the unit tests).
>> Yes, running junit tests is part of the Maven release process. (you
>> can only make a release if the code compiles and all tests are
>> passed). Since Java is coming with its own VM, we don't need to test
>> on all possible architectures. Considering this, perhaps it would be
>> sufficient to redirect http://testing.open-bio.org/biojava/ to
>> http://source.rcsb.org:8080/cruisecontrol/  ...
>
> That sounds like a practical short term solution :)
>
> Let's give Chris D a chance to comment though.
>
> Peter