[ 
https://issues.apache.org/jira/browse/BIGTOP-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

jay vyas updated BIGTOP-1384:
-----------------------------

    Description: 
By adding a the infamous *gradle wrapper script* (this is the idiom in gradle - 
to use the wrapper instead of a local gradle install) into our VCS, we 
gaurantee that the gradle tricks we implement will be running the exact same on 
all systems, no matter what.

- Also, it opens the tests up to be runnable by anyone, even those who don't 
have gradle installed.

- Finally, gradle wrapper will embolden us to be able to use more sophisticated 
gradle tricks newer features, b/c we will know that they run the same in all 
environments.

So, this task consists of :

1) Adding gradle wrapper to the {{bigtop-smoke-tests}}
2) Implementing cleanup for the build.gradle files also, possibly allowing for 
version specific features (i.e. advanced dependency inheritance for subprojects 
etc)

  was:
By adding a the infamous *gradle wrapper script* (this is the idiom in gradle - 
to use the wrapper instead of a local gradle install) into our VCS, we 
gaurantee that the gradle tricks we implement will be running the exact same on 
all systems, no matter what.

- Also, it opens the tests up to be runnable by anyone, even those who don't 
have gradle installed.

- Finally, gradle wrapper will embolden us to be able to use more sophisticated 
gradle tricks newer features, b/c we will know that they run the same in all 
environments.



> Implement Gradle Wrapper for smoke tests and cleanup.
> -----------------------------------------------------
>
>                 Key: BIGTOP-1384
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1384
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: backlog
>            Reporter: jay vyas
>
> By adding a the infamous *gradle wrapper script* (this is the idiom in gradle 
> - to use the wrapper instead of a local gradle install) into our VCS, we 
> gaurantee that the gradle tricks we implement will be running the exact same 
> on all systems, no matter what.
> - Also, it opens the tests up to be runnable by anyone, even those who don't 
> have gradle installed.
> - Finally, gradle wrapper will embolden us to be able to use more 
> sophisticated gradle tricks newer features, b/c we will know that they run 
> the same in all environments.
> So, this task consists of :
> 1) Adding gradle wrapper to the {{bigtop-smoke-tests}}
> 2) Implementing cleanup for the build.gradle files also, possibly allowing 
> for version specific features (i.e. advanced dependency inheritance for 
> subprojects etc)



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

Reply via email to