Page MenuHomePhabricator

[CI] Buildkite for web emscripten build
ClosedPublic

Authored by kamil on Jul 11 2023, 4:05 AM.
Tags
None
Referenced Files
F2900269: D8469.id28581.diff
Sat, Oct 5, 9:28 AM
F2899840: D8469.id28734.diff
Sat, Oct 5, 8:21 AM
F2899388: D8469.diff
Sat, Oct 5, 6:48 AM
Unknown Object (File)
Mon, Sep 16, 2:02 AM
Unknown Object (File)
Sun, Sep 15, 8:02 PM
Unknown Object (File)
Sun, Sep 15, 8:02 PM
Unknown Object (File)
Sun, Sep 15, 4:48 PM
Unknown Object (File)
Wed, Sep 11, 5:01 AM
Subscribers

Details

Summary

Add a build to check if properly generated .wasm files are committed to repo.

Depends on D8446

Test Plan
  1. Create new Buildkite pipeline: link.
  2. Run new build and check if it passes: link to build.
  3. 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

Repository
rCOMM Comm
Branch
wasm-work
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Jul 12 2023, 6:09 AM
.buildkite/emscripten.yml
8

Why is this necessary?

jon added inline comments.
.buildkite/emscripten.yml
8

the autoscaling docker-based agents don't have nix installed

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)

This revision is now accepted and ready to land.Jul 16 2023, 11:24 PM
In D8469#250983, @atul wrote:

(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)

The reason is described in ENG-4080.

This revision was automatically updated to reflect the committed changes.