>Another question regarding CI, I see tarvis, github action and Jenkins are used in Jmeter. What is the main CI ?
It is complicated. All of them add value. I would inline to GitHub Actions, however, we can't drop all Travis and all Jenkins jobs. There's https://github.com/renovatebot/renovate bot that can be integrated with Gradle, however, I have not explored that option. >gradle plugin like to build ( https://github.com/ben-manes/gradle-versions-plugin) There's https://github.com/jmfayard/refreshVersions which is good. The only sad thing is that it does not support composite builds (see https://github.com/jmfayard/refreshVersions/issues/205). "composite build" is the idiomatic Gradle way of structuring the build logic (see https://docs.gradle.org/current/userguide/structuring_software_products.html ) https://github.com/palantir/gradle-consistent-versions is good as well Travis used to be the primary CI, however, it becomes limited nowadays. The key Travis features for now are: * testing with s390x hardware * collecting code coverage information <-- this can (should) be moved to GitHub, however, it has not been done yet ASF Jenkins: * It allows publishing Maven snapshots to the ASF Nexus repository https://repository.apache.org/ without sharing credentials with non-ASF systems. * It makes it easier to publish HTML reports as a part of the build Unfortunately, we can't easily enable PR builds for ASF Jenkins as we can't run arbitrary (untrusted) code in the ASF environments. GitHub: * It allows PR builds even for untrusted code Buildbot: * We use it to publish nightly builds, however, I have no idea how it is configured. Vladimir
