Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: domain of srivatsav.prasanna@gmail.com
 designates 209.85.128.44 as permitted sender)
Sender: prasanna <srivatsav.prasanna@gmail.com>
Date: Thu, 28 Mar 2013 19:36:58 +0530
From: Prasanna Santhanam <tsp@apache.org>
To: CloudStack Dev <dev@cloudstack.apache.org>
Subject: [MERGE] bvt branch to master
Message-ID: <20130328140658.GA21569@cloud-2.local>
Mail-Followup-To: CloudStack Dev <dev@cloudstack.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)

I'd like to merge the bvt branch into master. The proposal [1] was to
stabilize master by allowing devs to quickly setup CloudStack using
simulated hypervisors and run some basic tests against it.

The bvt branch integrates the testing of cloudstack using marvin and
the simulator hypervisor. Alternately you may use devcloud as well
with the appropriate maven profiles enabled. One can try the
integrated tests today as described in [2]

While this is not to be touted as the magic pill for master stability
I think it is a good first step towards bringing together tests as
part of the build system. I've tested the steps on Linux and OSX.

[1] http://s.apache.org/5Lc
[2] https://cwiki.apache.org/confluence/x/PgvMAQ

Thanks,

-- 
Prasanna.,