...
Devs are expected to have run as many tests as feasible before review. CI checks are redundantOnce the checks above have passed for sanity:
- run unitTests
- any test failures will be annotated on the PR.
- tests will be sharded based on prior runtimes.
Once the PR is approved, the following can be run in parallel.
- run acceptanceTestsPermissioning
- run acceptanceTestsCliqueBFT
- run integrationTests unitTests
- run acceptanceTests
- run referenceTests
Test results can then be posted back to the PR, and any failures would prevent merging. If all pass, then the following artifacts are created, unique to the commit for this workflow.
- tarball created
- zipfile created
- docker images created
Should a release be decided on for this commit, the creation of a draft release would trigger:
- publishing of prior created artifacts with the release name and an RC1 suffix.
- creation of a release branch, should additions be necessary for an RC2.
When a release comes out of draft, and is approved:
- all artifacts are published as a non RC version number.
- docker latest tag is moved.