On Tue, 10 Jan 2006 09:18:59 -0800, Stephen Davis <[EMAIL PROTECTED]> wrote:
>> The reason I want static pages is for security concerns. It is not
>> easy whether buildbot can be trusted to have no security flaws,
>> which might allow people to start new processes on the master,
>> or (perhaps wors
> The reason I want static pages is for security concerns. It is not
> easy whether buildbot can be trusted to have no security flaws,
> which might allow people to start new processes on the master,
> or (perhaps worse) on any of the slaves.
I have security concerns as well, but not in buildbot i
> I have security concerns as well, but not in buildbot itself. My
> project is restricted even withinz the company I work for so I need
> the buildbot web server to only be available to certain people.
> HTTPS access would be nice too. TwistedWeb doesn't seem to have
> support for eithe
> > Or for separate logic projects being built with the same builtbot
> > master. For example, say Python's buildbot wanted to do regular builds
> > and tests of the distutils tree
> > (http://svn.python.org/view/distutils/trunk/).
>
> I believe you could always get it arranged the way you like by
Trent Mick wrote:
> I meant that more as a justification for improving the Waterfall
> status receiver to support separate summary pages for separate
> projects and trunks... all with the same buildbot master server.
>python.org/dev/buildbot/python/...
>python.org/dev/buildbot/python-releas
