View Transcript
Episode Description
A pipeline fails on a single job, and you shouldn’t have to rebuild everything around it to recover. That’s what changes with this update.
Job rerun is here, and it reruns only the jobs that actually failed. Until now, when a job inside a block failed and you reran the pipeline, every job in that block got rebuilt, including the ones that had already passed. The new default rebuilds only the failed jobs. Every other job in the block, plus jobs from earlier in the pipeline, is carried over and reused, so your workflow topology stays intact and only the new jobs get built.
The carried-over jobs are excluded from your billable time. That means a rerun costs you only the jobs that failed, not the whole block. Faster turnaround on failures, and a lower bill to match.
The old behavior is still one flag away. We exposed a YAML flag called block rebuild that keeps the full block rebuild when you want it. The new, leaner path is the default, and the escape hatch is there when you need it. sem-ai already understands the new behavior, so agents pick it up and rerun the right way automatically.
What’s Coming
Job rerun is the first building block of doubling down on CI for the second half of 2026. We’re working through what CI looks like in an agent-driven software development world, with sem-ai as the agent-native interface to the CI. Expect more agentic CI capabilities announced through September.
Till the next time,
Pete Miloravac https://semaphore.io
This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit semaphoreio.substack.com