Update CI -- switch to travic-ci.com or github actions?

[jmaassen]

So far, we've been using travis-ci,org for automated testing. This will be shutdown in the near future and replaced with travis-ci.com.

Although they also seem to support free use for open source projects, this may also be a good moment to check if it makes sense to switch to gtihub actions?

[jmaassen]

The conditions for the 'free tier' on travis-ci.com are a bit fuzzy. Apparently you get '10000' credits, But it's not clear what that buys you and what happens when you run out....

[sverhoeven]

Moving to GitHub actions would work for me. It supports Docker and has Gradle docs.

We would have recreate the SONAR_TOKEN and use https://github.com/codecov/codecov-action to upload the coverage.

[sverhoeven]

Appveyor is used for testing on Windows. Moving to GitHub Actions we can do tests on Windows there as well.

[jmaassen]

Creating workflows for unit and integrations tests (on ubuntu) was really simple. Basically works out of the box. Next step is windows, apple, fixedClient and uploading the coverage.

[jmaassen]

The test workflows seem to be working for linux, windows and mac (in the . The upload to codecov is included, but in the hackity way we used to use in travis and appveyor. Sonarcube is still missing.

Will check out the codecov and sonarcloud actions tomorrow