[alexellisuk]

For OpenFaaS (and other projects - k3sup, arkade, inlets etc) paying for Travis isn't going to be an option, as they are open source and unfunded. The Travis platform means being able to have relatively portable CI that almost never needs to change because of the CI platform. Bring a Makefile and use it locally and in the build pipeline.

Moving off Travis to something like GitHub Actions will cost a significant amount of time and the opportunity cost is ridiculous.

This along with the Docker Hub limits makes a very strong case for GitHub's strategy.

[nickjj]

> The Travis platform means being able to have relatively portable CI that almost never needs to change because of the CI platform. Bring a Makefile and use it locally and in the build pipeline.

What if you defined your GitHub actions to call out to shell commands? Then there's very little that's specific to GH actions.

Actions are nice but personally I'd rather have my CI as generic as possible, especially for the reason you mentioned which is to be able to run things locally if needed.