Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-14648

CircleCI dtest runs should (by default) depend upon successful unit tests

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Normal
    • Resolution: Not A Problem
    • Fix Version/s: None
    • Component/s: Build, Test/dtest
    • Labels:
      None

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              benedict Benedict Elliott Smith
              Reporter:
              benedict Benedict Elliott Smith
              Authors:
              Benedict Elliott Smith
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: