Add a build to check if properly generated .wasm files are committed to repo.
Depends on D8446
Details
Details
- Create new Buildkite pipeline: link.
- Run new build and check if it passes: link to build.
- Make some changes in CommQueryExecutor.cpp without generating new .wasm files, push it to branch and run new build, should fail: link to build.
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- wasm-work
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
| .buildkite/emscripten.yml | ||
|---|---|---|
| 8 | Why is this necessary? | |
| .buildkite/emscripten.yml | ||
|---|---|---|
| 8 | the autoscaling docker-based agents don't have nix installed | |
Comment Actions
Looks good.
(It seems a little weird that we're checking the .wasm file into the repo since it feels like a build artifact like eg dev.build.js, but I'm sure there's a good reason)