[jwrosewell]

Problem

The scripts in ci/ decide what a pull request builds and what a publish releases, and each has Pester tests beside it. rc holds five such files, being ci/packages.Tests.ps1, ci/dispatch.Tests.ps1, ci/check-environment-variable-names.Tests.ps1, ci/get-next-package-version.Tests.ps1 from #54 and ci/select-options.Tests.ps1 from #33. Only the environment variable name tests ran in a workflow. The rest ran only by hand or on a temporary branch, as #47, #54 and #60 each say under what remains, so a change to the release plan or the dispatcher could break them unseen.

What changed

.github/workflows/ci-script-tests.yml is new. On a pull request or a push to main or rc that changes ci/ or the workflow, it checks out this repository and common-ci's main beside it, which is where ci/dispatch.Tests.ps1 looks for common-ci and, after #47, where ci/packages.ps1 finds the shared release plan, and runs every ci/*.Tests.ps1 with Pester on ubuntu-latest and windows-latest. It can also be started by hand.

Checks

The workflow ran on this pull request at head 3cd797c1, which is the earlier head 343ed03 with rc at 32ffdcf1 merged in, as run 43520274370, and passed on both, Tests Passed: 168, Failed: 0 on ubuntu-latest and on windows-latest, being every test in the five files above. At the earlier head, before rc held #54 and #33, run 43483333111 passed the three files rc had then, 130 tests. The other checks passed on this head, being run 43520274430 (environment variable names), run 43520274906 (only rc into main) and run 43520274329 (link campaign tags).

This draft adds a workflow and changes no package code. James Rosewell decided at about 11:35 UTC on 12 November, for a change only to CI, "rebuild and include, but the change doesn't impact the code so no need to run the full builds."

What remains

Nothing. Once this is on rc, the CI script drafts above are tested by it on their own pull requests.

The last release into main was #114, merged at 06:22 UTC on 13 November.