The following is a summary of changes and status over the past ~month. Shout outs go to David Capwell, Ekaterina Dimitrova, Eduard Tudenhöfner, Berenguer Blasi, Anthony Grasso, and Dinesh Joshi, for with testing framework issues.
** New CI-Cassandra landing page The default landing page for https://ci-cassandra.apache.org/ has changed. Now it shows just the pipeline builds for each Cassandra branch, and the additional sub-projects. This should make it as simple as possible for developers to know the status of test results for their development branch base. ** Aggregated Test Reports and a Permanent Archive of every build Aggregated Test Reports have had a clean up. Jobs that re-run test suites with different parameters (cqlshlib and dtests) now distinguish those results by prefixing the test's package name with those differing parameter values. This makes it possible to differentiate those test results in the aggregated test report. The latest HTML test report is available here: https://ci-cassandra.apache.org/job/Cassandra-trunk/lastSuccessfulBuild/testReport/ This report is also made available in plaintext form. With a permanent archive of these, for ~every commit, getting sent to https://lists.apache.org/list.html?bui...@cassandra.apache.org ** Emails on Broken Builds Broken build notifications are now enabled on the whole pipeline builds. Now any failures in any of the artifacts, stress-test, or fqltool-test stages will result in email notifications. ** Build Times and Improvements The `dtest-large` job was previously the normal dtest run including the resource-intensive annotated dtests. With the addition of the `--only-resource-intensive-tests` flag the `dtest-large` job now only runs the resource-intensive dtests. This reduces the total pipeline build time by ~10 hours. One of the additional subproject builds is the cassandra-website build. As Anthony mentioned in a separate thread, it now generates and deploys every pushed change on master to cassandra.staged.apache.org. No one needs to commit changes under the "content/" directory anymore. If the commit was to the C* repo docs you can manually trigger the build so to update cassandra.staged.apache.org. ** Cassandra devbranch (patches) While CircleCI is much better for pre-merge CI, at least for those that have access to premium accounts and the large containers, CI-Cassandra can still be used for committers and contributors that don't have access to CircleCI. An improvement has been made so that all the parameters are verified at the beginning of the pipeline. This was based on feedback and observations that these parameters were fiddly to get right. ** Help Wanted The following items remain open, any help would be appreciated. - posting build summary from pipeline builds back to jira tickets, - adding tests for rpm/deb packaging, - adding the Driver tests, - jdk11 jobs in ci-cassandra.a.o, - upgrade dtests in ci-cassandra.a.o, - further comparison and oversight on slow, flaky, and ignored tests, - parallelising dtests (because 12 hours is still wild), and - efforts to standardise CI scripts (making them as CI system agnostic as possible). If you would like to help, feel free reach out to me on mail/slack and we can create a jira ticket for scope, ideas, and visibility. Input from more developers on what their needs from the CI systems are would also be awesome. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
