You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2015/01/22 04:34:34 UTC
[jira] [Updated] (BIGTOP-1618) iTest integration tests need only to
be bound to verify goal
[ https://issues.apache.org/jira/browse/BIGTOP-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Boudnik updated BIGTOP-1618:
---------------------------------------
Summary: iTest integration tests need only to be bound to verify goal (was: iTest integration tests need only to be bound to verify phase)
> 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)