Continuous Integration old

"Continuous Integration" or CI is a term we use to refer to automated application verification and testing of new code as it is being added commit by commit. We used to use Travis CI and have switched to GitHub Actions as of January 2021. See .github/workflows/ci for the instructions we provide to GitHub on what to do to verify and test our application new code contributions. In summary we:

• Run a linting job and a test job in parallel on ubuntu-latest
• Ruby and node js are installed on both and the official docker solr image is also used in the testing run of the code.
• Browsers are available and therefore we don't need to install them as part of the CI setup (required for capybara tests)
• CodeClimate is used for reporting on test coverage and other code quality metrics using the GitHub Marketplace provided action https://github.com/paambaati/codeclimate-action (which CodeClimate recommends)
• Gems and packages from node are cached - this was cribbed (i.e. "stolen") from https://boringrails.com/articles/building-a-rails-ci-pipeline-with-github-actions/
• Secrets are stored in the GitHub repo, see Secrets