Feature requests (somewhat long)
lehmann at ans-netz.de
Mon Aug 22 13:13:05 EDT 2005
Ade Lovett wrote:
> 1. network-enabled tinderd
> In order to be able to queue up builds, tinderd is going to need to be
> extended to run on the builder machines, listening on a network socket,
> with various tinderbox 'builds' attached to hosts, so that, for example,
> when someone queues up something on '6-amd64-gnome', it goes to the
> correct machine.
Right now build names are tinderbox-universe wide and not host related.
That means for having that we need a way of defining which build is
running on which host (where host can be > 1). If you have the same build
on more than 1 machine, and you want to run the test on a specific
machine of one of those just specify the queueentry for the specific
host. If you want to specify it for the build and the next "empty"
machine which has this build configured the actual db-scheme neds to be
> 2. per-build web UI access credentials
> At the moment, any tinderbox web user can access any build. The schema
> should be extended such that a list of available builds can be assigned
> on a per-user basis. For example, I may have builds that I do NOT want
> any external users to be able to access, and I may wish to provide
> multiple external builds to various people without the possibility for
That is possible right now. Just give the user the rights you want. Check
the checkboxes you want.
More information about the tinderbox-list