Cheaper CI & faster merging with batching
Blog post from Graphite
Graphite has introduced a new batch merging feature designed to enhance the efficiency and cost-effectiveness of its merge queue system, addressing a key demand from its most active customers. Batch merging allows multiple pull requests (PRs) to be grouped into a single draft PR, which undergoes continuous integration (CI) testing; if it passes, all PRs are merged together, thus optimizing throughput and reducing CI expenses. This approach contrasts with the previously implemented Parallel CI by prioritizing speed and cost reduction over ensuring every individual commit remains buildable, ultimately keeping the trunk branch stable post-merge. While batch merging can significantly accelerate queue times and lower costs, it may not be suitable for teams that require perfect commit history integrity. The feature, which is currently in public beta, offers customizable batch sizes and presents options for handling failed CI tests, such as removing the entire batch or bisecting to identify the problematic PR.
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.