Hi srivinas. Sounds great; If you're going to be long term investing in bigtop, then Maybe before submitting the ten new patches for tests, you're folks can help us out converging the two test frameworks as a first step?
https://issues.apache.org/jira/BIGTOP-1608 Then it will be easy to add your remaining tests. > On Aug 18, 2015, at 12:22 AM, Roman Shaposhnik <[email protected]> wrote: > > Sorry about the moderation problem and welcome to Bigtop! > > > ---------- Forwarded message ---------- > From: Srinivas Kolla <[email protected]> > To: [email protected] > Cc: "Thiruvalluvan M.G." <[email protected]>, Vijay Babu > <[email protected]> > Date: Mon, 17 Aug 2015 22:57:51 +0530 > Subject: Altiscale contribution to bigtop tests > Hello Bigtop Developers, > > Our company, Altiscale (www.altiscale.com) offers Hadoop as a service. > While we have our own methods of packaging and deploying Hadoop > products, we successfully used the Bigtop test framework and the > Bigtop test collection for validating those components that we offer. > In the process we added about 300 more tests to Hadoop, Hive, Flume > and Oozie components of Bigtop. These predominantly test the CLI and > the module functionality. > > We would like to contribute these tests back to the Bigtop project. > > In this regard, we plan to create an umbrella JIRA ticket for our test > contributions and then create sub-tickets for each patch that we > submit. We would like to start with the submission of a single groovy > file patch for Hadoop/ HDFS module and on acceptance, start submitting > more patches. We expect to submit about 10 patches in the next couple > months. > > Please let us know if this process is fine or if there is a more > effective way to contribute. > > Thanks, > Srinivas.
