Electron Builder and Travis Failures
See original GitHub issueRight now, there are quite a few issues with our build process, CI and Electron Builder:
Fetching Web UI
Currently, the latest Web UI version is not pinned to the gateway. On normal circumstances, it should not be a problem because it’s still pinned to the cluster. Although, the gateway is having issues connecting to cluster.
This makes build fails due to timeouts.
Solutions:
- Make
webui.ipfs.io
the latest released version anddev.webui.ipfs.io
the latest commit. That way, both domains shall be pinned to gateway. - Add a git submodule to IPFS Desktop with IPFS Web UI and build IPFS Web UI on the fly.
- More burden when updating IPFS Web UI.
Electron Builder failing on Linux releases…
Electron builder has a bug on the latest version that makes releases fail on Travis (don’t know if it happens on other CIs). Issue opened on their repo 20 days ago. No replies yet, no activity on the repo. See electron-builder#4134.
Downgrading also implicates downgrading electron which implicates changes on the code.
There’s also the issue #1044, which I believe is caused by the beta binaries been built manually on a virtual machine I created because of this issue.
What to do?
Other points…
- Travis is slow.
- Windows builds can be built on either Linux or macOS. Perhaps we can remove AppVeyor/Win Executor.
- Circle CI macOS is quite expensive, worth it? https://circleci.com/pricing/#build-os-x
- Performance plan from the ‘New plans’ is required for having Windows & macOS: https://circleci.com/pricing/usage/
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (6 by maintainers)
Top GitHub Comments
After running Travis+AppVeyor, I could successfully publish a 0.9.0-beta.3 prerelease which seems to indicate that our build process is fixed.
The problem with Electron Builder was, in fact, something else much easier but was buried deeper in the logs: see #1069.
Will close this for now since the issues on IPFS Desktop side seem to be solved!