diff options
| author | Frederick Muriuki Muriithi | 2022-01-14 10:45:29 +0300 |
|---|---|---|
| committer | Frederick Muriuki Muriithi | 2022-01-14 10:45:29 +0300 |
| commit | f44d791c5348d19e2b3d12438be83e88f2e2315a (patch) | |
| tree | 2869ae5785880b0b171179da97f197abe5fb1acc | |
| parent | a584c5d9027df929b3bba8df3852ad7a06e759c3 (diff) | |
| download | gn-gemtext-f44d791c5348d19e2b3d12438be83e88f2e2315a.tar.gz | |
Update notes on testing, indicating presence of laminar scripts
| -rw-r--r-- | topics/systems/ci-cd.gmi | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/topics/systems/ci-cd.gmi b/topics/systems/ci-cd.gmi index 4614427..705eae2 100644 --- a/topics/systems/ci-cd.gmi +++ b/topics/systems/ci-cd.gmi @@ -56,7 +56,10 @@ Below are some possible steps (and tasks) to undertake for automated deployment - Triggered by a commit to "main" branch (for now) - Trigger build of the package -- Run unit tests as part of the build: maybe the testing phase should be added to the genenetwork3 definition +- Run unit tests as part of the build: + - This has been done with the laminar scripts under `scripts/laminar` in genenetwork3 + - Maybe just change the command to ensure only specific tests are run, + especially when we add in non-functional tests and the like - If the build fails (tests fail, other failures): abort and send notifications to development team - If build succeeds, go to STEP 02 |