I think we can close disable Travis CI, it's too inefficient, and two CI are unnecessary
------------------ Original ------------------ From: "Albumen Kevin"<album...@apache.org>; Date: 2021年3月5日(星期五) 下午2:59 To: "dev"<dev@dubbo.apache.org>; Subject: [Discuss] Disable Travis CI for apache/dubbo 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
