[
https://issues.apache.org/jira/browse/BIGTOP-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912524#comment-13912524
]
jay vyas commented on BIGTOP-1222:
----------------------------------
I totally agree that sporadic patches may not be the right way forward.
Let me try to clarify my thoughts here :)... Hopefully without ranting too
much....
The simple issue is this: The complexity of running bigtop smoke tests is
limiting adoption, I think. Maybe Take a look at intel's HiBench as an example
of a script based testing framework with no xml editing required.
... forcing users to wade through the many pom files in the bigtop smokes, and
craft regular expressions to filter tests nested within 10s of directories, and
then run maven compile commands just to run something that can be done in bash
is probably overkill.. The main customizable portions of the pom files can
easily all be expressed in some kind of wrapper script... Don't you think? Be
it gradle or bash or whatever.
So if we don't want to use bash to wrap smokes... As I suggested in
bigtop-1195...Maybe we can use gradle to drive the smokes, which brings the
benefits if bash (clear, imperative , concise) with those of maven (java
centric, and java aware).
In any case, the end goal is making the smokes easy to run and customize: I'm
not debating that they currently can be customized by maven pom hacking.... But
id like to see the bigtop smokes become more transparent and directly runnable,
editable, and easily modifiable. The current accepted way of running them
which involves several maven / compile steps, is just too cumbersome for a
typical hadoop tester or newcomer to bother with. - they will just run terasort
instead....
We want bigtops smokes to be a comprehensive alternative to the current ad hoc
tests that people run, and that will only happen I think if the barrier to
adoption is lower.
> Completely gradleize the bigtop smokes
> --------------------------------------
>
> Key: BIGTOP-1222
> URL: https://issues.apache.org/jira/browse/BIGTOP-1222
> Project: Bigtop
> Issue Type: Improvement
> Reporter: jay vyas
>
> 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.1.5#6160)
