I expect it would take considerable time to get Travis to work here and I would like to get back to making changes and fixes to wskdebug, which is currently blocked without a CI.
Would it be ok to postpone that part and start with GH actions for now? Personally I think they are pretty cool, more flexible and the future of CI (at least on github). See it as an experiment :-) Cheers, Alex ________________________________ Von: David P Grove <gro...@us.ibm.com> Gesendet: Wednesday, March 4, 2020 8:31:15 AM An: OpenWhisk Dev <dev@openwhisk.apache.org> Betreff: Re: [wskdebug] github actions Alexander Klimetschek <aklim...@adobe.com> wrote on 03/03/2020 09:55:03 PM: > > for wskdebug I also enabled the CI "again", using Github actions. We > actually used Github actions in the past so there was a working > config. See this PR in my fork [1]. > > I also added the scancode check and removed the travis.yml. I think > it is better to have a single CI per repo here. Not sure if > Openwhisk has a strict policy to only use Travis? > We're using Travis for the other 30+ gitrepos in the project, so unless there is a really compelling reason to do something different I'd suggest we don't innovate here. Just creates more maintenance work to have multiple CI setups. To clear, I'm not deeply attached to travis, I'm just looking to minimize non-essential differences across the repos. --dave