On 03/22/2017 12:41 PM, François Deliège wrote: > A first actionable step is to increase the visibility of the test > coverage. Ideally this would be integrated in the Jenkins run on > Apache. Michael Shuler, is this something you can take a look at? > Let me know if we can help.
We've been running the jacoco coverage ant target on cassci for a very long time, but cassci will be going away in the future. I will not have time to add coverage to ASF Jenkins in the foreseeable future, so help would certainly be appreciated in all things testing for the Apache Cassandra project. Someone interested in including coverage runs could add to the Job DSL groovy under the jenkins-dsl/ dir - this is where all the jobs are configured on the ASF Jenkins instance. Dikang /msg'ed me on IRC earlier about coverage, too. Here's the cassandra-builds repo that drives everything on the project's ASF Jenkins jobs: https://git1-us-west.apache.org/repos/asf?p=cassandra-builds.git Here's where all the current project jobs are on ASF Jenkins: https://builds.apache.org/view/A-D/view/Cassandra/ Here's info about how the Job DSL works - all job configs are managed with DSL, with the exception of a couple scratch utility jobs: https://github.com/jenkinsci/job-dsl-plugin/wiki Here's info about ASF Jenkins: https://cwiki.apache.org/confluence/display/INFRA/Jenkins Basically, my task over the last few months has been to migrate Apache Cassandra testing jobs to run on the Apache Foundation's Jenkins and sunset CassCI. 95% of that task is done. -- Warm regards, Michael
