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

jay vyas edited comment on BIGTOP-1222 at 5/13/14 12:45 PM:
------------------------------------------------------------

FINALLY ! A patch so we can run bigtop tests DIRECTLY from source , no jar 
required ! :)

To run this, just do :

{noformat}
gradle clean compileGroovy test --info
{noformat}

The results are quite readable, and its super easy to include new tests !  Just 
add the groovy scripts into the array collection at the top.  This patch DOESNT 
require Jars to run ! There are a couple of VERY MINOR modifications to 
TestHadoopExampels, and TestHive Smoke tests which try the jar method, and if 
it doesnt work, they simply fallback to using a BIGTOP_HOME environmental 
variable, which points to the bigtop source code .  




was (Author: jayunit100):
FINALLY ! A patch.  To run this, just do ``` gradle clean compileGroovy test 
--info```

> Simplify and gradleize a subset of the bigtop smokes
> ----------------------------------------------------
>
>                 Key: BIGTOP-1222
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1222
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 0.7.0
>            Reporter: jay vyas
>             Fix For: backlog
>
>         Attachments: BIGTOP-1222.patch
>
>
> Currently, there is a JIRA underway to make running the maven based smoke 
> tests easier:  BIGTOP-1195.  
> Eventually, however, maybe we could run these smokes from gradle.    I think 
> that will obviate BIGTOP-1195 (Although i still assert a bash driver is a big 
> win/gain for bigtop's goals : which are to unify the hadoop packaging and 
> deployment paradigm).
> - run the smokes using a simple gradle goal
> - smokes should be easily runnable as scripts, with no need for jar file 
> intermediates.
> - The bash driver for BIGTOP-1195 (if accepted, still under debate) should be 
> upgraded to use the new gradle smokes
> - Delete old maven smokes. 
> This might be a little ambitious, if so others chime in.  I'm not a 
> gradle/groovy expert but getting more well versed.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to