Migrate Travis CI to Github Actions

[nitishkumar71]

Description

We want to migrate from Travis CI to Github Actions
Fixes #683
openfaas/faas#1585

How Has This Been Tested?

Please check CI Only Build
Please check Publish build for tag push

How are existing users impacted? What migration steps/scripts do we need?

1. We are not able to run CI Pipelines
2. We are moving to github actions for CI Pipelines

Checklist:

I have:

• updated the documentation and/or roadmap (if required)
• read the CONTRIBUTION guide
• signed-off my commits with git commit -s
• added unit tests

[derek]

Thank you for your contribution. I've just checked and your commit doesn't appear to be signed-off. That's something we need before your Pull Request can be merged. Please see our contributing guide.
Tip: if you only have one commit so far then run: git commit --amend --signoff and then git push --force.

[alexellis]

I have some suggestions

[alexellis]

This should be 1.13

[nitishkumar71]

Done

[alexellis]

Why only master?

[nitishkumar71]

So, should we enable it for both push and pull request?

[alexellis]

@wilsonianb could you advise re: pushing tags based upon the release version?

[wilsonianb]

You could do something like this (in an on.tag workflow) for the non-function components and use ${{ github.ref }} for the image tags:
https://github.com/wilsonianb/openfaas-cloud/blob/dfc967a49eca9acd099afc02138d96607ea4332b/.github/workflows/docker.yml#L34-L57

[nitishkumar71]

You could do something like this (in an on.tag workflow) for the non-function components and use ${{ github.ref }} for the image tags:
https://github.com/wilsonianb/openfaas-cloud/blob/dfc967a49eca9acd099afc02138d96607ea4332b/.github/workflows/docker.yml#L34-L57

@wilsonianb Thank you sharing the example.

@alexellis Can you please review it.

[Waterdrips]

@nitishkumar71 There's actually a lot more to converting ofc into actions than adding these workflows. As OFC is a complex system with lots of moving parts its probably best for me to take this over.

[nitishkumar71]

@nitishkumar71 There's actually a lot more to converting ofc into actions than adding these workflows. As OFC is a complex system with lots of moving parts its probably best for me to take this over.

makes sense