> Moving to pure pipeline jobs with all build & test runs in one pipeline, > with a final single JIRA comment post operation of all the results in > one comment would be the only way I can think of to prevent the > multi-post problem.
For the pipeline build, this is what I have so far putting together just the non-dtest builds. https://builds.apache.org/blue/organizations/jenkins/Cassandra-devbranch-pipeline/detail/Cassandra-devbranch-pipeline/84/pipeline …and this is now being generated from the generated DSL file. https://github.com/apache/cassandra-builds/compare/master...thelastpickle:mck/jenkins-dsl-pipeline If I don't hear any objection, I'll commit this. Off this, as it aggregates test reports, it's now possible to start test posting emails with the test report summary, as well as bringing in the dtest builds into the pipeline. And I'm aware that "Unit Testing" is an accurate column name here, but… :shrug:
