Hi, I see that you already dropped TravisCI - https://github.com/apache/dubbo/commit/cc3fb913e03424f62863c8536075be0fd04f12f2
I fully agree that GitHub Actions is the better CI these days, but there is one thing that Travis has that the others don't: support for non-x86_64 architectures like ARM64 and s390x. More and more server deployments are being done on ARM64 in the last few years. I was hoping to add a new job at TravisCI to build and test on ARM64 but at the moment there is one stopper - embedded-redis does not support ARM64, because it does not have a native binary for redis-server in the jar. I've created two Pull Requests for forks which have recent releases: - https://github.com/signalapp/embedded-redis/pull/8 - https://github.com/codemonstur/embedded-redis/pull/1 but they are not yet reviewed and merged. Would it be OK for you to re-introduce TravisCI as unofficial CI for ARM64 once the issue with embedded-redis is resolved ? Apache Infra plans to have a call with GitHub Actions representative - https://cwiki.apache.org/confluence/display/INFRA/Builds+Agenda+2021-03-11. I am going to ask about their plans for ARM64 support and then TravisCI could be forgotten for good! Regards, Martin On 2021/03/05 06:59:29, Albumen Kevin <[email protected]> wrote: > Hi community, > > > So far, we have enable two kinds of CI/CD platform , Travis CI and > > GitHub Actions, for Dubbo. GitHub actions works fine for Dubbo > > in 2.6.x[1], 2.7.x[2] and 3.x[3] versions. > > In 2.7.x and 3.x versions, both unit test and integration test[4], based > > on apache/dubbo-samples, are introduced to guarantee the stability > > of the snapshot version. > > > There are some benefits can be provided by GitHub Actions now: > > > - More powerful ecosystem > > - Easy integration with more GitHub activity > > - Can be launched at any time because it is no need > > for us to share the concurrency limit with all projects. > > Also the concurrency limit for each project looks enough for us. > > > I am wondering if we could disable Travis CI for now which function > > can be completely replaced with GitHub Actions? > > > [1] https://github.com/apache/dubbo/actions/runs/623019397 > > [2] https://github.com/apache/dubbo/actions/runs/620506574 > > [3] https://github.com/apache/dubbo/actions/runs/620213136 > > [4] https://github.com/apache/dubbo/runs/2029991040 >
