#369 Cache the Node.js tarball for the package builds
–
- github
- github/openchronology/timeline-app
- github/openchronology/timeline-app#369
- issue
- state:closed
Follow-up to #367 / #368. With progress output and per-step limits in place, the package builds' hangs turned out to come from downloading Node.js inside the Docker builds (`curl https://nodejs.org/dist/v24.21.0/node-v24.21.0-linux-x64.tar.xz`), not from apt: from GitHub's runners that download intermittently fails (`curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR`) or trickles below 1 kB/s (`curl: (28) Operation too slow`), while it takes under a second elsewhere. #368 makes such a stall retry and fail in minutes instead of 90, but a failure still needs a rerun. **Proposed fix:** download the Node.js tarball once per job outside Docker, cached by version with `actions/cache` (verifying its SHA-256 against nodejs.org's `SHASUMS256.txt`, as the Dockerfiles do), and pass it into the builds (a build context or `--build-context`), so the Dockerfiles only fall back to downloading when no tarball is given; local builds keep working unchanged. https://github.com/openchronology/timeline-app/issues/369
Related
Open #369 Cache the Node.js tarball for the package builds in the timeline