[BIGTOP-2227] smoke-tests should be a part of the top-level project, not separated

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 1.0.0
• Component/s: tests
• Assignee: Konstantin I Boudnik
• Reporter: Konstantin I Boudnik
• Created: 09/Jan/16 05:28
• Updated: 15/Jan/16 00:38
• Resolved: 12/Jan/16 23:48

Description

At the moment, smoke-tests aren't really a subroject of bigtop, as they have their own settings.gradle and are suppose to be executed from their own build.gradle

I propose we actually hook them up to the top level project, so all smokes will be visible when gradle projects is ran. This also will supposedly simplify current requirements like a need to have BIGTOP_HOME, ITEST, -Dsmoke.tests, etc. Instead, test could be run like this (from the top-level directory):

gradle bigtop-tests:smoke-tests:mapreduce:test

or, perhaps to run all of them

gradle bigtop-tests:smoke-tests:test

Thoughts?

Issue Links

• breaks: BIGTOP-2242 Running ./gradlew should only require JAVA_HOME for test task