[
https://issues.apache.org/jira/browse/HADOOP-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Charles resolved HADOOP-8058.
----------------------------------
Resolution: Won't Fix
Sorry, forget this.
There are separate hdfs and mapreduce jobs
https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Hdfs-trunk-Commit/
https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Mapreduce-trunk/
I was confused by the name "hadoop-common", thinking it was aimed to build the
whole http://svn.apache.org/repos/asf/hadoop/common/trunk/ tree
('hadoop-common').
Eric
> Configure Jenkins to run test from root trunk
> ---------------------------------------------
>
> Key: HADOOP-8058
> URL: https://issues.apache.org/jira/browse/HADOOP-8058
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: hudson
> Reporter: Eric Charles
>
> The current Jenkins configuration does a 'cd hadoop-common-project' before
> invoking $MAVEN_HOME/bin/mvn test -Pclover..., this is why we only have a
> partial report (only for hadoop-common). See for example
> https://builds.apache.org/job/Hadoop-Common-trunk/315/testReport/
> If we had the complete report, anyone could compare its local tests to the
> Jenkins ones (supposed to be the reference).
> If we do this, there can be more Jenkins mails on the lists (unstability,
> errors...), but I find the advantages worth the price.
> Thx,
> Eric
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
