The ASF new Jenkins setup is almost complete. See https://ci-cassandra.apache.org/view/branches/ The setup has been tracked in INFRA-19951
The next step here is to retire our usage of `builds.apache.org` and move all existing agents to the new setup. There are also new agents getting ready to being donated, that will be added to this new setup. If anyone has a problem with builds.apache.org going away please SPEAK UP NOW. On Jenkins, the main code's unit tests is close to (a japanese) green, with only 3 failures on both 2.2 and trunk. It's been noticed that some of the other unit tests (eg compression) are mixing up their run and/or reports. This, along with the formatting of reports, still remains a todo. Otherwise there's been a huge amount of momentum in fixing and improving the tests. It's only to take a quick glance at the commit log to see test fixes coming in from everyone and everywhere! Some ideas for subsequent steps are: - clean up report formats (slack notifications and emails sent), - put together some oversight on slow, flaky, and ignored tests (McFadin, were you still keen to do this?), - look into sending failure emails out on unit failures (if over time there's no more flaky units), - look into posting test result summary from each pipeline back to jira as a comment, - parallelise dtests (because 12 hours is still wild) - look into testing building of rpm/deb packages - look into testing of website building? - look into pipelines only kicking off stages that are relevant to what changed in the commit, - more comparison between CircleCI and Jenkins, and from any internal testing systems if folk can say, - look into tying in the Driver smoke tests. If any contributors are keen on any of these things, do reach out. Anything to help C* be rock-solid. regards, Mick --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
