Hello everyone , I am doing experiments with github CI and I believe we are ready to vote on the transition plan. Briefly the current jenkins env is problematic there is resources contention, limited parallelism and lack of control to do experiments.
The first version of the github actions ci is ready to merge. It has additional benefits that it won't trigger on documentation changes. https://github.com/apache/pulsar/pull/5642 They were things tried but removed like caching artifacts, since the cache size is too small to use. >From the current jobs in the workflow the cpp tests is stable enough to swap with the jenkins one we can merge this and request apache infra to disable the cpp jenkins job requirement. I am experimenting with running unit tests and integration test in parallel groups with subset of tests. It's not ready yet to be a checkin condition, we need to iterate and improve it further. In summary the goal is to merge the current pr as is, swap the jenkins cpp job and then further along move the unit test and integration test workflow as they stabilize.
