Konstantin Boudnik created BIGTOP-2227:
------------------------------------------

             Summary: smoke-tests should be a part of the top-level project, 
not separated
                 Key: BIGTOP-2227
                 URL: https://issues.apache.org/jira/browse/BIGTOP-2227
             Project: Bigtop
          Issue Type: Sub-task
          Components: tests
    Affects Versions: 1.1.0
            Reporter: Konstantin Boudnik
            Assignee: Konstantin Boudnik
             Fix For: 1.0.0


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):
{code}
gradle bigtop-tests:smoke-tests:mapreduce:test
{code}
or, perhaps to run all of them 
{code}
gradle bigtop-tests:smoke-tests:test
{code}

Thoughts?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to