Automated code quality infrastructure

[rafmudaf]

The software should include a full set of automated infrastructure to support developers throughout the development process. GitHub or other cloud-based resources should be leveraged as much as possible. Ideally, GitHub is preferred so that all systems remain consolidated, but the right tool should be chosen, as needed.

Testing

The test suite should be executed regularly throughout the development process. GitHub Actions is chosen for this since it is well integrated into the development workflow. The test suite is executed on each GitHub Event (i.e. push, open pull request) and results are stored for 30-60 days.

• Should a failing linting step fail an entire workflow? It could get quite frustrating to have to run the linter any time you want to do a quick check for if your tests pass. I regularly fire off commits to my working branch and wait for the emails from GitHub to see if it passed.

Systems tested

• Basic compile
• Compile with GPU target
  • NVIDIA - Possibility to integrate github.com with GitHub.nrel.gov to run on Eagle
  • AMD

Distribution

Binaries will be distributed through a set of package managers specific to particular systems such as Spack, Homebrew, and APT. When possible, these will be built and distributed via GitHub Actions (see conda-forge for example). If necessary, binaries can be hosted on each GitHub Release.