Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Each Cassandra release branch, eg Cassandra-2.2, Cassandra-3.0, Cassandra-3.11 and Cassandra-4.0; has it's own pipeline build. These are what are visible from the landing page at ci-cassandra.apache.org. These poll every 5 minutes for new commits on these branches. This effectively roughly gives a pipeline build per commit SHA.

...

These are aggregated test results over all the stages (builds) in the pipeline. The package prefix of the test helps identify which stage they are from, especially when there are matrix builds (unit tests with cdc or compression, or dtests with offheap or novnode). The test report listing will also display the stability (or flakiness) of tests over the past 30 builds.

These test results are only kept for the last 30 builds. Older test results are archived (in plaintext format, see below) can be found summarised in the builds mailing list, and with complete archives in https://nightlies.apache.org/cassandra/

...

The Blue Ocean UI provides a better view for listing new vs existing vs fixed tests. From a Test Result page, click on the navigation link.


Past Test Reports

The aggregated test results is also available in plain text format as an artefact attached to each pipeline build. This can be downloaded and saved to make it a permanently available reference.

These test results are otherwise permanently archived A summary of each pipeline's test failures is summarised in the builds mailing list.  Test results for a specific build can be searched via its build number or the commit SHA.

The original XML test reports, and all test log files, are kept stored in https://nightlies.apache.org/cassandra/ 

...

(warning) These artefacts come with no guarantees at all, and should only be used for development purposes.
      Users should only rely upon our formal releases found here.

These artefacts may be removed after 30 days.


DevBranch and pre-commit CI

...