I now have admin privs on the projects build box, so what do we need in a build farm?
I like the Samba model with the drop down to view things:
And I like that users can add their arch too:
Code is at:
I'm happy to get everything setup but I need to know what we want. My first thoughts were to have lots of VMs on the big build box we've got, bring the VMs up and down when needed and compile HEAD, RE24 periodically, but that smoke testing would just make noise.
We'll need a frontend to browse results anyway and maybe an admin panel to issue builds or just some admin commandline tools for pre-release testing. E-mails could go to a new openldap-builds(a)openldap.org list or similar. We'll also need a tool for users to register their system/host with the build master to collect results and show them. And we'll need some set of standard build options to be uniform across platforms?
Lastly, there is also:
T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 824887
Open Source. Open Solutions(tm).
Suretec Systems is a limited company registered in Scotland. Registered
number: SC258005. Registered office: 13 Whiteley Well Place, Inverurie,
Aberdeenshire, AB51 4FP.
Subject to disclaimer at http://www.suretecgroup.com/disclaimer.html
access control pseudo-attributes 'entry'/'children' interfere with
attributeType ( <oid> NAME <'entry' or 'children'> ... ).
IIRC an old access control internet-draft used [entry] and [children]
instead. Should we move to rename them that way?
(Poorly timed question I know, should be for 2.5. Just a stray
thought I wanted to bring up before I forget.)