Rerun Only the Jobs That Failed

Semaphore has introduced job rerun behavior that rebuilds only failed jobs rather than rerunning every job in the affected pipeline block, while preserving successful jobs and earlier pipeline results for reuse. This default change is intended to reduce feedback time and billable compute costs, since carried-over jobs are not charged during reruns. Users who need the previous full-block rebuild behavior can enable it through a YAML `block rebuild` flag, and Semaphore’s sem-ai agent interface already supports the updated workflow automatically. The release is presented as an initial component of Semaphore’s broader plans for agent-driven CI capabilities, with additional announcements expected through September 2026.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.