2 Commits (7835c2abaf00f0a40c247b59021b1b5b6c0ae28a)

Author	SHA1	Message	Date
Paul Balaji	085e7d0463	feat: migrate large runners to buildjet (#4424) ... feat: migrate large runners to buildjet - includes migration to buildjet's cache - benefits: https://buildjet.com/for-github-actions/blog/launch-buildjet-cache#buildjet-cache-benefits - 20GB/week free cache is 2x what GHA provides - drive-by: add restore-keys for the yarn caches - more buildjet investigation notes [here](https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4445)	3 months ago
Paul Balaji	b91e0f446a	feat: remove extraneous caching (#4469) ... feat: remove yarn build cache - saves 600MB of cache space PER COMMIT - doesn't impact overall per-commit CI time - better CI time in the general case due to fewer cache evictions on the e2e matrix job - [with caching](https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/10797745470) vs [no caching](https://github.com/hyperlane-xyz/hyperlane-monorepo/actions/runs/10797213927?pr=4469) drive-by: disable docker caching for agent build - currently cache has no impact on build time of the agent image - rerunning builds for a commit or pushing empty commits should in theory lead to quicker builds with layer caching, but the main problem is that the `RUN` step of building the agents is not cached by the docker action - only RUNs with bind mounts get a checksum computed [(reference)](https://docs.docker.com/build/cache/invalidation/#general-rules) - disabling docker build caching could help save a bunch of cache space - best way to 4x speed here is moving this job to a buildjet 8vcpu runner (read [here](https://github.com/hyperlane-xyz/hyperlane-monorepo/pull/4445) for more info) drive-by: TLC - update to latest docker build action - provides a nice build summary and can generate artifacts that help break down where build time is spent - update check-env before build, given the current deprecation annotations - https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/ - coverage step doesn't need to wait for `yarn-test` anymore	3 months ago