Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # dev >> CI for the release builds


Copy link to this message
-
Re: CI for the release builds
Andrew, agree in principle and technically not a problem. Let me work
with some folks here and get back with some prototype.

On Thu, Jan 31, 2013 at 5:30 PM, Andrew Purtell <[EMAIL PROTECTED]> wrote:
> Shame the tests couldn't also run out in AWS, on suitable instance types
> like m2.4xlarge maybe. Then there could be multiple instances of multiple
> tests going on. How much coverge how fast would be a function of pooled
> resources not just your own. Something to consider?
>
>
> On Thu, Jan 31, 2013 at 5:21 PM, Devaraj Das <[EMAIL PROTECTED]> wrote:
>
>> Hey Andrew,
>> Yes I am looking at doing parts of this on AWS and parts in our
>> internal cluster (since that comes for free) - the AWS component is
>> there to mostly host the build results, and the tests would run in the
>> internal cluster (that's my current thinking).
>> Thanks
>> Devaraj
>>
>> On Thu, Jan 31, 2013 at 10:33 AM, Andrew Purtell <[EMAIL PROTECTED]>
>> wrote:
>> > +1
>> >
>> > And if you're looking to do this on AWS, I can look into assisting with
>> > funding.
>> >
>> >
>> > On Wed, Jan 30, 2013 at 10:07 PM, Devaraj Das <[EMAIL PROTECTED]>
>> wrote:
>> >
>> >> Hi folks,
>> >>
>> >> Have been toying with the idea of automating the process of running
>> >> the tests that constitute the release test plan (the initial tests
>> >> would be from
>> >>
>> https://docs.google.com/spreadsheet/ccc?key=0AvLqcVIqNtlTdE9iemw2STVmWHFVMVVNY2JvZ0NwZGc#gid=0
>> >> ,
>> >> and they would be run with/without security turned on in the cluster).
>> >> As we continue to develop more system/largescale tests, we would keep
>> >> adding them to the harness.
>> >>
>> >> I have set the ball rolling on this within the company and I hope the
>> >> community will be interested in seeing such a thing happen.
>> >>
>> >> The idea is to be able to easily run a release artifact through a
>> >> series of tests (on our internal cluster or on AWS), and the result
>> >> would be published in a machine on AWS (visible to all). In the
>> >> future, this could be extended to run the tests on trunk artifacts as
>> >> well (catch regressions early).
>> >>
>> >> Thoughts?
>> >>
>> >> Thanks,
>> >> Devaraj.
>> >>
>> >
>> >
>> >
>> > --
>> > Best regards,
>> >
>> >    - Andy
>> >
>> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> > (via Tom White)
>>
>
>
>
> --
> Best regards,
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)