[Buildbot-devel] Rationally Dealing with Several Products

[Brian Warner]

"Roy S. Rapoport" <buildbot-devel at ols.inorganic.org> writes:

> Having started playing with buildbot, it looks like I should define a
> builder for every unique product, branch, platform combination.  At work,
> where I've started deploying buildbot, some of our products build on 18
> platforms; some of our products have up to four concurrently-developed
> branches.  And we've got about 4-6 products.  The worst-case scenario,
> then, is that we have 432 possible builders.  Mind you, we're not at the
> worst-case scenario -- today, we only have 159 combinations.

FYI, the current intention is that Builders define process, so that multiple
branches should all be run on the same Builder. The status display tools
aren't yet up to the task of showing this properly, but that should improve
eventually.

This might bring your count down by a factor of 4, but even so, it's still
pretty bad. We need better status display techniques to deal with this.

One tool: you can add one or more "show=" arguments to the Waterfall page's
URL to see just a subset of the columns. You can also create multiple
Waterfalls, each with a "category" that will cull down the number of builders
being displayed.

cheers,
 -Brian