You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2013/06/09 00:49:20 UTC

[jira] [Commented] (BIGTOP-996) Document steps needed to run BT tests on a fresh host

    [ https://issues.apache.org/jira/browse/BIGTOP-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678877#comment-13678877 ] 

Roman Shaposhnik commented on BIGTOP-996:
-----------------------------------------

Any help in that respect would be very much appreciated. On that note -- we're trying to restart our Bigtop meetups/hackathons this summer (http://www.meetup.com/HandsOnProgrammingEvents/events/122050632/) perhaps we can find folks interested in helping us with our documentation, etc.
                
> Document steps needed to run BT tests on a fresh host
> -----------------------------------------------------
>
>                 Key: BIGTOP-996
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-996
>             Project: Bigtop
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 0.5.0
>            Reporter: Konstantin Boudnik
>            Assignee: Konstantin Boudnik
>            Priority: Blocker
>             Fix For: 0.7.0
>
>
> I argue that a major part of becoming a contributor for Bigtop is a learning curve in how to use all the mechanics of the trade. I see this times and again.
> We need to have a HOWTO.txt document that would have a trivial description of the needed steps. Something like:
> sudo jenkins
> clone Bigtop repo
> mvn install top pom.xml
> mvn install itest 
> set HADOOP_CONF_DIR, HADOOP_HOME, HADOOP_MAPRED_HOME
> mvn install test-artifacts top pom.xml
> mvn install test-execution top pom.xml
> mvn -Dorg.apache.bigtop.itest.log4j.level=TRACE -f bigtop-tests/test-execution/smokes/hadoop/pom.xml verify
> That might be sufficient.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira