hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Boudnik <...@apache.org>
Subject Re: Patch testing
Date Wed, 20 Oct 2010 21:13:10 GMT
Actually, there's a way to do it, but is isn't simple as you said and require
certain JIRA management discipline like linking JIRAs properly, for instance.

Another veritable here is to submit patches for all involved project at once or
to be able to postpone a patch validation if patch-A isn't available when
patch-B is submitted (project B depends on A, obviously).

After that everything else is real easy: build dependencies, mvn-install
artifacts, build the dependent one with locally installed artifacts, clean mvn
cache after all. The tricky part though is to guarantee that these chained
builds are executed on the same machine. Otherwise, local mvn repo
synchronization will be one huge mess ;)

So, in other words, let's restore the status quo first ;) IMO

On Wed, Oct 20, 2010 at 04:37PM, Aaron Myers wrote:
> One feature request, which may be difficult to implement, and may not be
> worth it:
> It would be nice to somehow support running tests for patches which require
> changes that span core/MR/HDFS. As it stands, I believe an HDFS patch will
> be built and run against a trunk jar, but if this HDFS patch requires some
> not-yet-committed work that's being done in a HADOOP JIRA, the HDFS tests
> will fail.
> Obviously, just getting hudson QA running again is a necessary pre-requisite
> for this. :)
> Aaron

View raw message