GitHub Actions

[melroy89]

Instead of Travis, we could actually start using Github Actions to achieve the same thing.

Maybe it's a better integration with Github.

Let me know if you agree or not Vasil.

Regards,
Melroy van den Berg

[melroy89]

Travis takes forever!! Also is in queue for waay too long. This isn't how CI/CD suppose to work..

[melroy89]

And the new one commit is running for 1 hour and 30 minutes:

This is because of Travis, which put the jobs all into a queue, and Travis can't handle the amount of requests to their services (not related to cpp-ipfs)...

[melroy89]

#39 can help as well to speed up the execution, but won't solve the Travis specific issue which is that the job stays in their queue for way too long.

[melroy89]

Looks like a migration issue at Travis atm: https://travis-ci.community/t/builds-hang-in-queued-state/10250/4

Most likely resulting in subscription when its all converted to travis-ci.com.

[melroy89]

I have introduced several jobs, not just the build jobs (using the GitHub Actions Matrix feature), but also tests jobs + code coverage. Static code analysis job as well as a separate Doxygen job. All to avoid regression impact (and ofc course progression).

[melroy89]

Done!