[
https://issues.apache.org/jira/browse/BIGTOP-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291378#comment-14291378
]
jay vyas edited comment on BIGTOP-1618 at 1/26/15 2:02 AM:
-----------------------------------------------------------
+1.... although hoping the focus will shift to unifying the frameworks for
{{smoke-tests}} and {{test-artifacts}} soon. !
was (Author: jayunit100):
+1.... although hoping the focus will shift to unifying the frameworks for
{{smoke-tests}} and {{test-artifacts}} soon. !
> iTest integration tests need only to be bound to verify goal
> ------------------------------------------------------------
>
> Key: BIGTOP-1618
> URL: https://issues.apache.org/jira/browse/BIGTOP-1618
> Project: Bigtop
> Issue Type: Bug
> Components: tests
> Affects Versions: 0.8.0
> Reporter: Konstantin Boudnik
> Assignee: Konstantin Boudnik
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1618.patch
>
>
> our CI is using {{deploy}} in the iTest artifacts build. The issue is that
> {[deploy}} is bound to {{integration-test}} hence will execute new
> integration tests automatically. This will be running tests involving network
> and services manipulations on the shared build machines.
> I suggest we only bind these tests to {{verify}} goal, which will let us to
> avoid running such tests as a part of {{deploy}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
