2 ms·
An easy way to speed up CI/CD IMO is to build your own runners with all of your tools pre-installed (directly, from a cache, or a container). With GitHub Actio
by candiddevmike 3y ago
An easy way to speed up CI/CD IMO is to build your own runners with all of your tools pre-installed (directly, from a cache, or a container). With GitHub Actions for instance, every job starts on a fresh machine, and you get penalized for parallelizing when every machine has to spend 1 minutes+ collecting dependencies. Ideally jobs should spin up in a clean environment with immediate access to tooling.
- efrecon 3y agoI've just made a ShowHN [1] about my pet project [2] for the past few weeks. It let you run isolated runners on-prem from any OCI image using microVMs. The project uses a base image to form a minimal runner environment, and an image that layers the tooling required for running the runner on top of the base image. You can insert your own set of pre-installed tools in that chain of images to warm up runners quickly. [1]: https://news.ycombinator.com/item?id=39844932 https://news.ycombinator.com/item?id=39844932 [2]: https://github.com/efrecon/gh-runner-krunvm https://github.com/efrecon/gh-runner-krunvm