|Summary:||MASTER BUG: Add the rest of the buildbots to the "core builders" list|
|Product:||WebKit||Reporter:||Eric Seidel (no email) <eric>|
|Component:||Tools / Tests||Assignee:||Nobody <webkit-unassigned>|
|Version:||528+ (Nightly build)|
|OS:||OS X 10.5|
|Bug Depends on:||33289, 33290, 33292, 33295, 33297, 33305|
Description Eric Seidel (no email) 2010-01-06 20:44:05 PST
MASTER BUG: Add the rest of the buildbots to the "core builders" list http://trac.webkit.org/browser/trunk/WebKitTools/Scripts/webkitpy/buildbot.py#L47 Being on the "core builders" list means that when the bot goes red, the commit-queue will stop committing patches, and anyone trying to use bugzilla-tool land-diff (or other related landing commands) will have their commits aborted unless they pass --ignore-builders. Effectively if a "core builder" is red, then tree is "closed" (even though WebKit doesn't really have the concept of the tree being closed). This bug is blocked by all the other "add builder for port X to the core builders list" bugs and serves as an easy way for me (and others) to track them all and the flakey tests and other reliability issues which block each of the builders from being added to the "core builders" list.
Comment 1 Eric Seidel (no email) 2010-01-07 00:07:54 PST
If we actually succeed in moving most or all builders into the core-builders list, then we can eventually flip it from being a white list to a black list, or no list at all. The only reason we have the core-builders list is because the project seems to have a de facto list of builders that it keeps green, and the rest are mostly ignored. Core-builders list codifies this unofficial practice into an official list.