Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of tucu@cloudera.com designates
 209.85.214.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANJr2=EiXxsNvYAh-MGWg21ZaN_A_iNfyGHDue8xKDVvkwe8mg@mail.gmail.com>
References: 
 <CAF-WD4TvKwYpuuQ9ibxv4UZ8B2BEhXnpfKb5mq3D-pwVKSHOzA@mail.gmail.com>
 <CA+4052kJF0ba0USYf=QLN_MhHDz+B1Z-6VTVZ3mB_AhHgv64Hg@mail.gmail.com>
 <CAJs-t7N2_RGQ2a54cBn4YnEqhOwUmyws4iLy5jfUv2YnHjmaXg@mail.gmail.com>
 <CA+4052kYeK4=FQswPP8VYE1YTujYbGU1edNxbaVABFNpPdUPZA@mail.gmail.com>
 <CANJr2=E82=9KLsaLrVfVU0END=77vQucxAc9+QgNUKMhFmrxng@mail.gmail.com>
 <CAF-WD4Rs60X7yTedR3V2QgeSG3aX3KuL9nUh8fiSZ8SqyAL08Q@mail.gmail.com>
 <CAJs-t7O2tnzR0vrfcaXA_bggpRysqKuKxB_jwU1Nu_BhYQFdLg@mail.gmail.com>
 <CANJr2=EiXxsNvYAh-MGWg21ZaN_A_iNfyGHDue8xKDVvkwe8mg@mail.gmail.com>
From: Alejandro Abdelnur <tucu@cloudera.com>
Date: Wed, 18 Apr 2012 10:11:13 -0700
Message-ID: 
 <CAJs-t7O6VahJqTcqQBkL88H40s3-VkEZPpHJnhgi8kXFXLyPKw@mail.gmail.com>
Subject: Re: Supporting cross-project Jenkins builds
To: common-dev@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Giri,

On Tue, Apr 17, 2012 at 8:36 PM, Giridharan Kesavan
<gkesavan@hortonworks.com> wrote:
> Alejandro,
>
> On Tue, Apr 17, 2012 at 4:52 PM, Alejandro Abdelnur <tucu@cloudera.com> wrote:
>> Giri,
>>
>> I agree that running ALL tests all time takes a lot of time
>> (personally I'd prefer we do this at the penalty of longer runs).
>>
>> Still we have a problem to solve, we need to find a solution on
>> test-patch working for ALL maven modules, currently changes outside of
>> common/hdfs/mapred or cross-projects test-patch does not work.
>>
>> So, how about the following approach:
>>
>> * All patches must be at trunk/ level
>> * All patches do a full clean TARBALL creation without running testcases
>> * From the patch file we find out the maven modules and for those
>> modules we do javac-warns/javadoc-warns/findbugs/testcases
>
> I like this approach of doing a clean tarball.
> and doing the other checks ( javac warnings, javadoc warnings, findbug
> warnings and release audit.)
> for that specific module.
>

Great, the idea of the doing a clean tarball it to ensure that nothing
in the build/assembly is broken and that no API change breaks other
modules.

>>
>> This would speed up test-patch runs and together with a nightly
>> jenkins jobs running ALL testcases would give a complete coverage.
>>
>
> test-patch and nightly jenkins jobs running ALL testcase?
> could you pls explain this?

you want to verify there is no regression because of functional
changes in all modules, doing this once a day seems reasonable and
will help identify the culprit early on (that is why I said in my
original email my preference would be to run everything every time)

thxs

---
Alejandro