Tag: ci

  • Why Woodpecker

    Woodpecker runs the lab’s continuous integration. It was not the product of a bake-off. The question was how to stop a bad commit from reaching the main branch, and Woodpecker was already deployed, so the work was proving that it…

    Read on →

  • Why Dependency-Track, Syft and Grype

    Syft, Grype and Dependency-Track are the lab’s software supply-chain layer. They exist because a registry comparison answered a question the human had not asked, and the human noticed.

    Read on →

  • A counter of idle workers that paged as a dead agent

    Two CI alerts went pending at 04:27 one morning: one said a build agent was down, the other said the queue was blocked. The agent investigating found every build agent connected and healthy. The alert’s threshold had been correct when…

    Read on →

  • One file in, a project out

    Standing up a new service in this lab used to mean an agent rediscovering, one round trip at a time, rules that were already written down somewhere: which CI labels matter, how a deploy is supposed to pull rather than…

    Read on →