Skip to content

Conversation

@lerouxb
Copy link
Contributor

@lerouxb lerouxb commented Dec 31, 2024

I have this as a draft for now because I'm still deciding if I should wire it up in CI in this same PR or do that in a separate one. We'd have to spawn the signing server like we do for the package tasks so that the file will be signed, for example.


This builds a minimal electron app that doesn't even open a window, so there's just a main process. Running the app it made then produces a file ready.signal containing the text Hello from a future Compass! and it exits.

In a future PR we can build this from the smoketests task, then serve up this file from the fake auto-update webserver we'd already be running. The test can check for the ready.signal file to make sure that auto-update worked.

~/mongo/compass/packages/mocked-compass % time HADRON_DISTRIBUTION=compass npm run package-compass
[snip]
✔ hadron-build:release 3 assets successfully built
ℹ hadron-build:release /Users/leroux.bodenstein/mongo/compass/packages/mocked-compass/dist/mongodb-compass-99.0.0-darwin-arm64.dmg
ℹ hadron-build:release /Users/leroux.bodenstein/mongo/compass/packages/mocked-compass/dist/mongodb-compass-99.0.0-darwin-arm64.zip
ℹ hadron-build:release /Users/leroux.bodenstein/mongo/compass/packages/mocked-compass/dist/mongodb-compass-99.0.0-darwin-arm64.zip.sig
HADRON_DISTRIBUTION=compass npm run package-compass  24.24s user 4.69s system 155% cpu 18.654 total

@github-actions github-actions bot added the feat label Dec 31, 2024
@lerouxb lerouxb added the no release notes Fix or feature not for release notes label Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feat no release notes Fix or feature not for release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants