On Thu, May 1, 2008 4:13 pm, MattyJ wrote: > On Thu, 01 May 2008 13:39:38 -0700, Lan Barnes <[EMAIL PROTECTED]> wrote: > >> 1. build request entry form(s) >> >> 2. build (most of this is already written in perl) >> >> 3. Post build products to an FTP site (I'm using vsftp on CentOS 5.1) >> >> 4. post or create a web page announcing and linking to the various parts >> of the build/product >> >> 5. send emails at appropriate junctures >> >> 6. record management data at each step in a SQL data base >> >> So I'm looking for development tools that would facilitate this. > > For #1 above, I haven't seen any continuous integration servers that have > this. A 'build request' usually takes the form of a code checkin. The rest > are usually pretty standard. >
We already have a continuous integration server that kicks off on each submit. This would be for builds bound for SQE and even release candidates. >> The only real requirements are: >> >> 1. that this be in a scripting language(s) for RAD and easy maintenance. >> C/C++/C#/Java are out >> > > As you probably already know, you are severely limiting yourself with that > on, however: I probably didn't express myself very well. We need to be able to modify it at regular (short) intervals, and a compiled language with malloc etc is probably more overhead than we want. I'm aware that there are workbench type tools, and if their config is scriptable, that might fill the bill. But it would be nice if they were OSS (no POs, licenses, etc), > > http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix > > BuildBot and Tinderbox look like your go-to choices. Tinderbox is what > Mozilla uses for all its projects so it must be good, right? :) > > I never know when your tongue is in someone's cheek. -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
