[Buildbot-devel] upcoming release

[Brian Warner]

> The appdata thing should work great for the account-wide default, but there
> is no reason to avoid looking for the .buildbot directory in a project
> specific directory even on windows.

Ok, I just committed a change to crawl from the current directory up to the
root looking for a .buildbot directory, and if one isn't found to try
%APPDATA%/buildbot as a last resort. Under posix it does the same thing, but
%with ~/.buildbot as a last resort. I also changed the "is it under HOME"
%security check and replaced it with a (posix-only) "is it owned by the
%current user" check.

> Is this buildbot file, one to be edited by the user? Generally you don't go
> into your local settings folder (e.g. " C:\Documents and Settings\ntrout")
> and edit files by hand like you might go into "~/." on unix. I personally
> would prefer options to be store in a common place, not per user, e.g.
> perhaps "\buildbot" or wherever buildbot is installed?

It is meant to be created and edited by the user. It is actually specific to
the project you're working on (or a set of trees all for the same project),
so it feels like per-user is the absolute coarsest granularity you'd want to
use. But, what I'll probably end up doing is adding a --config option to
'buildbot' so you can force it to use whatever file you want. That way you
could make a script that always went to a particular buildmaster..
'twistedbuildbot statusgui', 'metabuildbot statusgui', etc.

thanks,
 -Brian