chore: test release artifacts individually #2599
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP
In order to test the actual artifacts we release, this PR splits the "Dev Release" job in CI into multiple build jobs, one for each artifact. Each artifact is then tested against our acceptance tests.
As Dev Release mirrors Prod Release, this change will also apply to Prod Release. An additional step will combine each artifact and publish them as we currently do. This means all artifacts must pass their tests before a release is made.
To avoid needing to write a script which conditional builds specific artifacts (a lot of tedious logic and build orchestration), I'll first attempt to migrate our workflows from ad-hoc scripts and npm to Makefile(s) which can orchestrate for us.
Follow up to #2495