[
https://issues.apache.org/jira/browse/BIGTOP-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14183543#comment-14183543
]
jay vyas commented on BIGTOP-1384:
----------------------------------
looks like [~dcapwell] is now working this angle and has some interesting ideas
on how to get around the ASF limitations. looking forward to upcoming patch.
- davids additions will install gradle on the fly so smoke-tests have zero
system expectations
- Also i think this patch will update the
https://github.com/apache/bigtop/blob/master/bigtop-deploy/vm/vagrant-puppet/smoke-tests.sh
recipes to use the gradle bash wrapper instead of the puppet based toolchain
installer
> 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
> Assignee: David Capwell
>
> 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)
> 3) Update README with new instructions for people running the tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
