[
https://issues.apache.org/jira/browse/BIGTOP-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910020#comment-13910020
]
Konstantin Boudnik commented on BIGTOP-1195:
--------------------------------------------
I am not particularly against shell scripting but there's a Gradle infra, that
is being introduced as a focal point for build/test control, e.g. build
packages, install artifacts, run them, etc. Gradle has a great integration into
Maven ecosystem and the rest of the JVM world. Do you think it would be better
to move the script's functionality to a Gradle task?
> Higher level interface to smokes.
> ---------------------------------
>
> Key: BIGTOP-1195
> URL: https://issues.apache.org/jira/browse/BIGTOP-1195
> Project: Bigtop
> Issue Type: Improvement
> Reporter: jay vyas
> Attachments: BIGTOP-1195.1.very-raw.patch, BIGTOP-1195.patch
>
>
> Running all the smokes with mvn verify is painful:
> 1) Diving into the XML files when stuff breaks
> 2) Remembering to use TRACE level logging
> 3) Leaving out export PIG_HOME , etc... leads to smokes failing late in the
> test run.
> 4) Hopefully we can specify more env variables to control size of smokes in
> the future. That will make a script for running the whole thing even more
> useful.
> 5) when hacking the groovy scripts:: To Compile or not to compile? Always
> forget to specify.
> A simple bash script could serve as a better tutorial/solution/template for
> users that want to run smokes. I'm attaching a very raw patch that we can
> rewrite in python and flesh out some more to do better error reporting, more
> verification, etc.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
