Fetching contributors…
Cannot retrieve contributors at this time
290 lines (170 sloc) 6.93 KB
build virtualenv in as command
xmlrpc api + examples
retrieve package name from for Python packages
clean up client stuff!
tagset documentation
one super-client that can detect, run tests/communicate results, etc.
datastore stuff/archival:
- get all tagsets
- get all updates by tagset
- 'flush tagset'?
everything else can be "within last month"
some sort of history ("8 of last 8 succeeded") + flush history
- keep (configurable) 1 month on display?
organize reports with FAILURES at top (unless marked otherwise)
concatenated output, etc? for GitClone?
a conf.d?
client logfile that's communicated back to server @ end.
file upload/download?
integrate TAP?
authentication ^^^ for results submission
separate? authentication for thru-Web configuration
make is_building, request_build flags persistent
crashing client still needs to report, esp with is_building
nose plugin to report? + test and nose config => users.
test client code!
periodic breakage => tests get rerun ever hour until it works:
masks stochastic errors...
move check code into client.
hierarchical tree of reports, instead of list-of-lists? (think git stuff)
client scripts should be much friendlier about one-script-for-multiple-machines.
a directory of public pony-build master servers URLs built-in...? or
retrievable via XML-RPC from my server? or available via a file? with
short names?
subprocess incremental reporting.
test swarm!! (jacob)
"top builders" view. (grig)
pygame inspired stuff (ilume):
- send test results back to server from install runs
- include tests in installed package, of course
at what point does my stupid database model stop scaling? ;)
latest results for main page
Things To Look At (for main page)
auto remove stale builds after a certain amount of time?
allow setting builds that SHOULD ALWAYS BE DISPLAYED, even if out of
date/stale/no results/etc.
quickstart guide
architecture diagram
relative times, or times in viewer timezone, or ...?
importable client/API improvement (pbc)
JSON format (both client output AND server output)
sort on column in various summary views.
database schema should include package name and time submitted.
switch to python3?
look at
test pony build client on python2.3 and 2.2? import for inclusion in software.
refactor BaseCommand => ShellCommand for variable replacement, etc.
maybe have groupcommand?
command to report on versions of installed Python packages
group views/composite views
selenium results repost script?
separate control channel for "generic" Python package building, etc.
post VCS to server as part of tagset, if available; or have server use
it, if it's available. obviates tags like 'experimental' for pygr...
time/date on submissions
package name on submissions
get submissions by machine
raw text display; hierarchy; cool js.
"next record with this tagset", "previous record", "history"
A software variation on a theme by Antoine de Saint Exupéry:
"A software application architecture is finished when there is nothing left to take out. A software application design is finished when there is nothing left to add."
"opinionated software"
static URLs that point to the most recent result for a particular machine type?
Web hooks:
david bolen:
I don't know if it's possible but it would be great if the buildbot
master could send an email to a buildbot maintainer if it thinks a
buildbot is down. There have actually been times in the past when
from the perspective of my buildbot things were just dandy, but the
master showed it as down. Stopping and restarting the buildbot,
forcing it to reconnect, cleaned things up, but I have to monitor the
web status page which is a manual process.
kill children before exit?? persistent process ugliness.
pythoscope foo - integrate pythoscope reporting
also integrate Virtual mem reporting for processes under linux?
before release:
- set a better default server url
url download/install
pypi/ integration
+ need hg
+ virtualenv integration
+ coverage info
+ unittest (junitxml?)
client example & discussion
also provide protocol/setuptools ext/ info for pony-build
--- jessenoller I've got
an itch: A Rest-Based, pony-build backed package index.
jessenoller In my "pypackage" app, I want cool little boxes like
github has for "install this" or "get the source" - semi transparent
"pip install foo"
Subject: [Python-Dev] People want CPAN :-) -- ssteiner on python-dev
integrate jacob's virtualenv fix.
tests for build steps?
add "stale notify" RSS feed
feed for all builds?
move to a multithreaded web server?
triggered builds/based on commits
generic feeds for specific tagsets, duh
RESTish interface
show how to integrate with buildbot
document pbc expected values
coverage return?
config.rc file for server
rotating file repo with max size limit
put a red flag next to builds that have failed within last 24 hrs
two clients, one lite one heavy?
files visible flag
'latest' magic component, 'latest='tags magic component
'latest files' magic component, also with tags (so, latest egg from win32)
try out
Context vs TempDirContext problems
notify next-time-run
fill in unfilled project details from e.g. github webhook notify?
separate upload, etc stuff to WSGI & mount
allow people (auth?) to annotate, post-hoc tag build results -> search
@ctitusbrown Like the concept of a (cached)"prove it" link for
packages to show they actually run under the OS/version pairs listed
on PyPI.
@ctitusbrown Trust ring is good idea, but might get tricky if PyPI
alts pop up, making proving identity tough. Might need OpenID for
a (hierarchical?) list of projects w/config info, e.g.
python/cpython2-trunk - svn, co from here, run these commands
so that you can refer via a nice name and not have to configure stuff
yourself? make it an SHA-signed, downloadable file...? or servered?
make it a SEPARATE, or can-be-included, server from the straight
pony-build server?
gae version of pony-build?
"standard" setup: test a package under 23, 24, 25, 26, 27b, 31, etc.?
auto-spawn EC2 instance to test from a snapshot?