1 |
I'm in the early design phases of my own tinderbox project, and I'd |
2 |
appreciate some input on the features people would like to see. The |
3 |
basic idea is that it'll be a web interface where people can submit |
4 |
their own build requests, and then a cluster of VMs will go off and |
5 |
build them, all while collecting useful information for later use, |
6 |
such as build logs, binpkgs of the build products, memory, disk, and |
7 |
CPU usage, etc. I've created an issue tracker to collect ideas here: |
8 |
|
9 |
https://bitbucket.org/dwfreed-gentoo/tinderbox-meta/issues |
10 |
|
11 |
You do not need a Bitbucket account to post to the issue tracker, but |
12 |
in that case you'll need to pass a recaptcha (javascript will probably |
13 |
be required, you've been warned), and you won't get emails about |
14 |
updates. Please post your suggestions there and not to this list. |
15 |
|
16 |
Please note, any comments about use of Bitbucket instead of X, |
17 |
requirements for javascript, or anything else based on your own |
18 |
personal beliefs will be unceremoniously deleted. I've already |
19 |
selected most of the software and libraries I'll be using to implement |
20 |
this, and attempts to bikeshed those choices will likewise be deleted. |
21 |
|
22 |
Thanks in advance for any suggestions you may have. |
23 |
|
24 |
-dwfreed |