hadoop common build fails creating docs
---
Key: HADOOP-7517
URL: https://issues.apache.org/jira/browse/HADOOP-7517
Project: Hadoop Common
Issue Type: Bug
Components: build
Reporter:
Unable to start HDFS cluster on trunk (after the common mavenisation)
-
Key: HADOOP-7518
URL: https://issues.apache.org/jira/browse/HADOOP-7518
Project: Hadoop Common
Issue
[
https://issues.apache.org/jira/browse/HADOOP-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7515.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I've just committed this.
test-patch reports the
hadoop fs commands should support tar/gzip or an equivalent
---
Key: HADOOP-7519
URL: https://issues.apache.org/jira/browse/HADOOP-7519
Project: Hadoop Common
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/HADOOP-7516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HADOOP-7516.
-
Resolution: Not A Problem
HDFS-7515 takes care of the issue reported here.
Mavenized
Hi folks,
Now that the build machines are available again, I tried resubmitting a patch
to https://issues.apache.org/jira/browse/MAPREDUCE-2767. However, it looks like
it is not being picked up by CI.
Is 0.22 branch excluded from hadoop CI ?
* Milind
---
Milind Bhandarkar
Greenplum Labs,
Aha!
In that case, is the local test-patch success sufficient for patches on
branches ?
- milind
On 8/5/11 3:38 PM, Giridharan Kesavan gkesa...@hortonworks.com wrote:
Milind,
patch testing usually happens only on trunk
thanks,
Giri
On Fri, Aug 5, 2011 at 3:11 PM, milind.bhandar...@emc.com
I believe the usual practice should be:
1. The trunk patch (if applicable) must pass automated Jenkins testing for
trunk CI build, and code review.
2. The branch patch should have ant -Dpatch.file=path.patch test-patch
run against it in the developer's build environment for the branch, and the
