You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/19 01:22:00 UTC
[jira] [Updated] (CASSANDRA-14648) CircleCI dtest runs should (by
default) depend upon successful unit tests
[ https://issues.apache.org/jira/browse/CASSANDRA-14648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-14648:
-----------------------------------------
Component/s: Build
> CircleCI dtest runs should (by default) depend upon successful unit tests
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-14648
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14648
> Project: Cassandra
> Issue Type: Improvement
> Components: Build, Testing
> Reporter: Benedict
> Assignee: Benedict
> Priority: Major
>
> Unit tests are very quick to run, and if they fail to pass there’s probably no value in running dtests - particularly if we are honouring our expectations of never committing code that breaks either unit or dtests.
> When sharing CircleCI resources between multiple branches (or multiple users), it is wasteful to have two dtest runs kicked off for every incomplete branch that is pushed to GitHub for safe keeping. So I think a better default CircleCI config file would only run the dtests after a successful unit test run, and those who want to modify this behaviour can do so consciously by editing the config file for themselves.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org