Replace Travis with GitHub Actions

[daN4cat]

This is a placeholder to consider GitHub action as CI/CD pipeline.

[daN4cat]

Or Azure Pipelines given there are 10 free pipelines that can be used in GitHub.

[jekkos]

Duplicate of #3110

[jekkos]

I might have overseen this, but it seem that travis-ci.com only offers a non renewable set of credits. You basically need to move to their paid plan to have the credits renewed..

I think currently the only option is to move to github actions now. Unless we can find 70$ a month in extra funding to pay for travis plan.

[BudsieBuds]

So the Always Free banner on their website doesn't apply for this project?

Free for Open Source

Free for open source. We love the Open Source Community, and to show how much we love it, upon validated request placed with our Support Team you may receive free OSS credits for your public builds.

[jekkos]

Indeed it wasn't 100% clear to me how to apply. I emailed them asking for extra credits so let's wait for this first.

[jekkos]

I'm not sure but I think the unstable draft releases are only visible to contributors. It's not ideal as it stands, the fact that I need to tag a release in order to get the files in there.

I might look into pushing the zip to another repo so it can be downloaded from there.

[jekkos]

Using draft releases for unstable builds does not feel like the best solution.

I think github packages might be a better solution for unstable builds. It's 500MB max for the free plan, but it will support version tagging out of the box.

[jekkos]

I changed the build pipeline a bit to push tarballs to github packages instead of publishing them to the releases section. One minor issue to look at is the version string, this one is forced using npm to the branch name and git commit hash to differentiate the unstable versions as we used to do on bintray.

It seems that it's still setting the branch version instead so this needs a second look.