cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Witschey (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10269) Run new upgrade tests on supported upgrade paths
Date Wed, 16 Sep 2015 16:34:46 GMT


Jim Witschey commented on CASSANDRA-10269:

Status update: changes to the dtests in [this PR|]
have been merged. I'll be monitoring them on CassCI today. The behavior of the tests is:

- {{cassandra-3.0}} and {{trunk}} jobs will run the upgrade tests from the 2.2.0 tarball release.
Once 3.0 is released and {{trunk}}'s version is bumped, we'll have to update the tests so
{{trunk}} tests upgrades from the 3.0.0 tarball.
- Pre-3.0 jobs will skip the upgrade tests by default.
- The other upgrade paths (2.1->2.2, 2.1->3.0, 3.0->trunk) will each be tested on
their own CassCI jobs.

> Run new upgrade tests on supported upgrade paths
> ------------------------------------------------
>                 Key: CASSANDRA-10269
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tests
>            Reporter: Jim Witschey
>            Assignee: Jim Witschey
> The upgrade dtests for 8099 backwards compatibility (originally dealt with in [this dtest
PR|] and [this JIRA ticket|])
need to be run with upgrades over the following upgrade paths:
> - 2.1 -> 3.0
> - 2.2 -> 3.0
> - 3.0 -> trunk
> There are a number of ways we could manage this. We could run the tests as part of the
normal dtest jobs in 2.1, 2.2, and 3.0, and select what version to upgrade to based on the
version of the test. We could also refactor the new upgrade tests to use the upgrade machinery
in the existing upgrade tests.
> [~philipthompson] [~rhatch] Do you have opinions? Can you think of other options?

This message was sent by Atlassian JIRA

View raw message