www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-4886) when Jenkins tests a patch, it should compile with -Pnative
Date Wed, 06 Jun 2012 23:13:23 GMT

    [ https://issues.apache.org/jira/browse/INFRA-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290566#comment-13290566

Colin Patrick McCabe commented on INFRA-4886:

Thanks for the clarification... I'll move this to HADOOP.
> when Jenkins tests a patch, it should compile with -Pnative 
> ------------------------------------------------------------
>                 Key: INFRA-4886
>                 URL: https://issues.apache.org/jira/browse/INFRA-4886
>             Project: Infrastructure
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: Jenkins
>            Reporter: Colin Patrick McCabe
>            Priority: Minor
> It would be nice if Jenkins would compile with mvn compile -Pnative or a similar command
> Currently, we don't seem to build the native code at all when testing patches.  Unfortunately,
this allows patches that break the native parts of the build to go in without the usual testing.
> It's true that the Jenkins build would not catch all native code issues (it only compiles
in one environment, and there may be #ifdefs).  However, some testing is sure better than
none.  I believe with cmake the performance overhead of -Pnative should be very minimal.
> This would also allow us to run the junit tests which depend on native code, and the
raw native unit tests in Jenkins.

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


View raw message