Spin-up CKAN for testing in Github Actions

[fjuniorr]

Description

Closes #144

• Adapt docker compose setup from Add docker compose setup for local testing #190 for use in Github Actions
• Test against CKAN versions 2.9, 2.8 and 2.7 following CKAN maintenance cycle

Docker is not supported fully on Windows and MacOS runners, therefore the tests against CKAN are run only for ubuntu. Because of this I'm also generating code coverage and running r-devel against ubuntu.

The tricky part for me was discovering that by default docker compose sets up a single network. Each container joins the default network and is both reachable by other containers on that network, and discoverable by them at a hostname identical to the container name. However, the hostname of the docker container cannot be seen from the host unless /etc/hosts is updated.

[fjuniorr]

Because I'm running all tests against http://localhost:5000 after d6931 and there is no CKAN for windows and macosx, the tests are failing.

Some options would be:

• Skip tests on windows and macos (bad because locally they could still work)
• Drop CI tests on windows and macos (bad because it's likely a big user base)

Not sure how to approach this. Any ideas @maelle?

[maelle]

Skip tests on windows and macos (bad because locally they could still work)

Would writing a custom skipper help? https://testthat.r-lib.org/articles/skipping.html
It'd be a combination of the internal code of testthat:::on_ci() and the code for recognizing which OS is meant.

• If not on CI, run the test.
• If on CI, run only if OS where it is possible.

[fjuniorr]

I've reused ckanr::check_ckan for this, which skips a test if CKAN is offline. A name like skip_if_ckan_offline would probably be easier to understand, but I will leave this change for latter after I've grokked the rationale behind the PRs

• CKAN test server settings for testthat suite by florianm · Pull Request #31 · ropensci/ckanr
• Streamlined setting environment variables into setup_ckanr, superseding set_test_env by florianm · Pull Request #37 · ropensci/ckanr

The failing tests for CKAN 2.9 are being tracked at #189.