I've updated our Jenkins config to use the GitHub App token recently configured by Infra rather than using the GitBox setup. Using this, we can now automatically build PRs from collaborators, though only the release-2.x and master branches will be deploying snapshots. Most of these branches and PRs that are open seem to have failures at the moment, so there's a lot of red, but I'm assuming that's because a lot of the open branches and PRs are extremely outdated and no longer build using the toolchains.xml I configured here (which currently only specifies JDK 1.8, 11, and 14, to be updated as JDKs are released to better reflect a typical developer toolchains.xml). Also, I thought I chose the config setting to skip the first build upon indexing, but I must've triggered something when I changed that setting as all the branches were attempted to be built again. Thankfully, there's no real build traffic on ci-builds right now, so hopefully I won't have to intervene and cancel a bunch of them.
One thing you should see from this is that we should get some better GitHub integration for unit test results and anything being scanned by warnings-ng (which are the other reports listed on https://ci-builds.apache.org/job/Logging/job/log4j/job/master/ if you were wondering). If we can figure out how to generate some of the other static code analysis reports without having to run an entire "mvn site" build, then I can integrate those findings as well. This should make the output of these tools a bit more accessible. -- Matt Sicker <[email protected]>
