[
https://issues.apache.org/jira/browse/BIGTOP-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated BIGTOP-1621:
---------------------------------------
Attachment: BIGTOP-1621.patch
Here's the patch that adds 'bigtop-itest-framework' as a subproject to the
top-level gradle build.
I have removed the changes in README files (for now); as well I don't think
adding 'vars.properties' file in this patch is a good idea for two reasons:
# it isn't in the scope of the patch
# the use of vars.properties is mis-documented and needs to be updated in a
separate JIRA.
I think this approach of creating build layout should work very well (and more
work needs to be done for deployment, etc.), but I'd love to hear others
opinions.
[~dasha.boudnik], could you please open a ticket and update the
bigtop-test-framework/README file accordingly to the latest failure injection
code, please?
> Migrate itest to gradle
> -----------------------
>
> Key: BIGTOP-1621
> URL: https://issues.apache.org/jira/browse/BIGTOP-1621
> Project: Bigtop
> Issue Type: Improvement
> Components: tests
> Affects Versions: 0.9.0
> Reporter: jay vyas
> Assignee: jay vyas
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1621.patch, BIGTOP-1621.patch
>
>
> build itest w gradle, so that we can call gradle tasks to install it as a
> local dependency, as part of supporting one single testing framework. See
> BIGTOP-1608.
> This is the first step, the minimal work necessary to allo gradle based smoke
> tests to use gradle best itest framework via calling {{gradle install}}
> later those doing publishing of itest jars can finalize the process and test
> gradle for publishing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
