Hacker News with Generative AI: Continuous Integration

Mastodon Server for Apache NuttX Continuous Integration (macOS Rancher Desktop) (lupyuen.org)
We’re out for an overnight hike, city to airport. Our Build Farm for Apache NuttX RTOS runs non-stop all day, all night. Continuously compiling over 1,000 NuttX Targets: Arm, RISC-V, Xtensa, x64, …
Faster CI with Selective Testing (mill-build.org)
Selective testing is a key technique necessary for working with any large codebase or monorepo: picking which tests to run to validate a change or pull-request, because running every test every time is costly and slow. This blog post will explore what selective testing is all about, the different approaches you can take with selective testing, based on my experience working on developer tooling and CI for the last decade at Dropbox and Databricks.
Faster continuous integration builds at Canva (canva.dev)
In April 2022, the average time for a pull request (PR) to pass continuous integration (CI) and merge into our main branch was around 80 minutes.
Continuous Integration Dashboard for Apache NuttX RTOS (Prometheus and Grafana) (lupyuen.github.io)
Last article we spoke about the (Twice) Daily Builds for Apache NuttX RTOS…
CodSpeed – integrated CI tool for performance testing (codspeed.io)
Backed by<h1>Unmatched performance testing in your CI</h1><p>Measure and optimize software performance consistently and before any release to avoid production issues, improve UX and save on infrastructure costs.</p>
Working with Igalia to Improve RISC-V LLVM Continuous Integration (riseproject.dev)
The LLVM project provides a very widely used and actively developed suite of compiler and toolchain technologies: including Clang, the LLVM middle-end optimizer and backend code generator, MLIR, LLD linker, and much more. While RISC-V LLVM support has progressed significantly, a key area that needed attention was the limited level of continuous integration (CI) for the RISC-V target.
Your CI pipeline isn't ready for AI (morgante.net)
In developing my AI codegen agent, I’ve surprisingly been far more frustrated by CI/testing systems than any unreliable LLM API.
The Many SHAs of a GitHub Pull Request (kenmuse.com)
Many people don’t realize it, but pull requests actually have multiple “identities” when an Action workflow runs. There are actually multiple SHAs that represent different parts of the lifecycle during a continuous integration build. This can be confusing for teams that are trying to implement advanced processes, and it often lead to mistakes. In some cases, it leads to a misunderstanding – thinking that the build is testing the branch itself instead of a simulated merge to the target branch.
We managed to speed up our CI to save 168 days of execution time per month (home-assistant.io)
We're moving continuous integration back to developer machines (world.hey.com)