Dear Moaz,
I think that might be still possible that Travis CI is better than Github Action, because we know nothing about Github Action before. We don’t have idea how Github Action is better than Travis CI. So we may compare the two to see which one is more suitable for us. If there is strong reason that Github Action is better than Travis CI, we may consider to change. Some questions to consider maybe: 1. Does GIthub Actions increases our productivity, better than Travis CI? 2. Does Github Actions is easier to configurate, easier than Travis CI? Can we compare Travis CI and GIthub Actions directly? Thanks a lot! Best Regards, Chris Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: Wang Wei<mailto:[email protected]> Sent: Wednesday, March 11, 2020 9:43 PM To: [email protected]<mailto:[email protected]> Subject: Re: [DISCUSS] Replace Travis CI with Github Actions Is Github Action easier to configure and debug? Does it support both Linux and Mac OSX? We have spent much time on Travis and it is now working. If we change to Github Action, I think we need some strong points.. On Wed, Mar 11, 2020 at 8:06 PM Yeung Sai Ho <[email protected]> wrote: > Dear Moaz, > > I think I will agree with you personally to get rid of the Travis CI. > Today I wasted a whole day just to modify my code targeting to pass the > Travis CI build in #624, while many project deadlines are approaching. I > still cannot pass the build test at the end of the day due to the path > include problems, so sad... > > Thanks for your email concerning good suggestions. > > Best Regards, > chris > > > > 從我的iPhone傳送 > > > Moaz Reyad <[email protected]> 於 2020年3月11日 19:41 寫道： > > > > - External Email - > > > > > > > > Dear All, > > > > I would like to propose to move from Travis CI to the new CI/CD features > in > > Github with Github Actions [1]. You can see an example for licence check > > after commit with github actions instead of travis in this pull request > [2]. > > > > There are many benefits of using Github Actions instead of an external > tool > > like Travis, such as eliminating the need to configure an external tool > and > > integrating better CI with other Github features. > > > > We can start moving the CI jobs from Travis to Github step by step until > we > > completely remove the need of using Travis. > > > > What do you think? > > > > Regards, > > Moaz > > > > [1] https://github.com/features/actions > > [2] https://github.com/moazreyad/incubator-singa/pull/13 > > ________________________________ > > Important: This email is confidential and may be privileged. If you are > not the intended recipient, please delete it and notify us immediately; you > should not copy or use it for any purpose, nor disclose its contents to any > other person. Thank you. > ________________________________ Important: This email is confidential and may be privileged. If you are not the intended recipient, please delete it and notify us immediately; you should not copy or use it for any purpose, nor disclose its contents to any other person. Thank you.
