Page MenuHomePhabricator

[CI] Buildkite for web emscripten build
ClosedPublic

Authored by kamil on Jul 11 2023, 4:05 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Oct 18, 9:00 AM
Unknown Object (File)
Fri, Oct 18, 9:00 AM
Unknown Object (File)
Fri, Oct 18, 9:00 AM
Unknown Object (File)
Fri, Oct 18, 8:51 AM
Unknown Object (File)
Oct 7 2024, 1:41 PM
Unknown Object (File)
Oct 5 2024, 9:28 AM
Unknown Object (File)
Oct 5 2024, 8:21 AM
Unknown Object (File)
Oct 5 2024, 6:48 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
Lint
Lint Not Applicable
Unit
Tests Not Applicable

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 ↗(On Diff #28581)

Why is this necessary?

jon added inline comments.
.buildkite/emscripten.yml
8 ↗(On Diff #28581)

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.