From https://twitter.com/mitsuhiko/status/1720410479141487099 https://twitter.com/mitsuhiko/status/1720410479141487099 : > GitHub Actions currently charges $0.

From https://twitter.com/mitsuhiko/status/1720410479141487099 https://twitter.com/mitsuhiko/status/1720410479141487099 : > GitHub Actions currently charges $0.16 *per minute* for the macOS M1 Runners. That comes out to $84,096 for 1 machine year GitHub Runner is written in Go; it fetches tasks from GitHub Actions and posts the results back to the Pull Request that spawned the build. nektos/act is how Gitea Actions builds GitHub Actions workflow YAML build definition documents. https://github.com/nektos/act https://github.com/nektos/act From https://twitter.com/MatthewCroughan/status/1720042352767570004 https://twitter.com/MatthewCroughan/status/17200423527675700... : > This is the macOS Ventura installer running in 30 VMs, in 30 #nix derivations at once. It gets the installer from Apple, automates the installation using Tesseract OCR and TCL Expect scripts. This is to test the repeatability. A single function call `makeDarwinImage`. With a Multi-Stage Dockerfile/Containerfild, you can have a dev environment like xcode or gcc+make in the first stage that builds the package, and then the second stage the package is installed and tested, and then the package is signed and published to a package repo / app store / OCI container image repository. Continuous integration: https://en.wikipedia.org/wiki/Continuous_integration https://en.wikipedia.org/wiki/Continuous_integration Is there a good way to do automated testing like pytest+Hypothesis+tox w/ e.g. the Swift programming language for computers? CloudFuzz is built upon OSS-Fuzz. SLSA now specifies builders for signing things correctly in CI builds with keys in RAM on the build workers. "Build your own SLSA 3+ provenance builder on GitHub Actions" https://slsa.dev/blog/2023/08/bring-your-own-builder-github https://slsa.dev/blog/2023/08/bring-your-own-builder-github