Repository navigation
Set up "supported"-only buildbot waterfall view #46629
Description
| BPO | 2376 |
|---|
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2009-06-12.15:40:50.504>
created_at = <Date 2008-03-18.01:00:27.788>
labels = []
title = 'Set up "supported"-only buildbot waterfall view'
updated_at = <Date 2009-06-12.15:40:50.503>
user = 'https://bugs.python.org/exarkun'bugs.python.org fields:
activity = <Date 2009-06-12.15:40:50.503>
actor = 'exarkun'
assignee = 'none'
closed = True
closed_date = <Date 2009-06-12.15:40:50.504>
closer = 'exarkun'
components = ['None']
creation = <Date 2008-03-18.01:00:27.788>
creator = 'exarkun'
dependencies = []
files = []
hgrepos = []
issue_num = 2376
keywords = []
message_count = 2.0
messages = ['63832', '89282']
nosy_count = 1.0
nosy_names = ['exarkun']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue2376'
versions = []
Activity
exarkun commentedon Mar 18, 2008
The Python buildbot's waterfall view currently shows all builders. Not
all of these are expected to work currently. This can be confusing to
people trying to understand the current state of Python on various
platforms. Buildbot can be configured to present limited views, for
example only including builders for platforms where all the tests are
expected to be passing (and expected to remain passing).
The way to place a builder in a particular category is with the
"category" keyword in its dict:
With 0.7.5, adding a "category" query argument will restrict the view to
include only builders from the specified category.
With 0.7.6, you can construct a custom
buildbot.status.web.waterfall.WaterfallStatusResource and pass a list
for the categories initializer argument which will restrict the builders
it displays. You can make several of these for different categories and
put them at various places in the resource hierarchy.
exarkun commentedon Jun 12, 2009
This was done long ago, it seems.