open-nomad/ci/README.md
Seth Hoenig 4f3a1e6f7d
ci: use groups of tests in gha (#15018)
* [no ci] use json for grouping packages for testing

* [no ci] able to get packages in group

* [no ci] able to run groups of tests

* [no ci] more

* [no ci] try disable circle unit tests

* ci: use actions/checkout@v3

* ci: rename to quick

* ci: need make dev in mods cache step

* ci: make compile step depend on checks step

* ci: bump consul and vault versions

* ci: need make dev for group tests

* ci: update ci unit testing docs

* docs: spell plumbing correctly

Co-authored-by: Tim Gross <tgross@hashicorp.com>

Co-authored-by: Tim Gross <tgross@hashicorp.com>
2022-10-27 09:02:58 -05:00

35 lines
1.3 KiB
Markdown

# CI (unit testing)
This README describes how the Core CI Tests Github Actions works, which provides
Nomad with continuous integration unit testing.
## Steps
1. When a branch is pushed, GHA triggers `.github/workflows/test-core.yaml`.
2. The first job is `mods` which creates a pre-cache of Go modules.
- Only useful for the followup jobs on Linux runners
- Is keyed on `hash(go.sum)`, so a cache is re-used until deps are modified.
3. The `checks`, `test-api`, `test-*` jobs are started.
- The checks job runs `make check`
- The test job runs groups of tests, see below
3i. The check step also runs `make missing`
- Invokes `tools/missing` to scan `ci/test-cores.json` && nomad source.
- Fails the build if any packages in Nomad are not covered.
4a. The `test-*` jobs are run.
- Configured as a matrix of "groups"; each group is a set of packages.
- The GHA invokes `test-nomad` with $GOTEST_GROUP for each group.
- The makefile uses `tools/missing` to translate the group into packages
- Package groups are configured in `ci/test-core.json`
4b. The `test-api` job is run.
- Because `api` is a submodule, invokation of test command is special.
- The GHA invokes `test-nomad-module` with the name of the submodule.
5. The `compile` jobs are run
- Waits on checks to complete first
- Runs on each of `linux`, `macos`, `windows`