what collection advise auto-build your application?

as recently several years ago, developers indeed finished builds went clients. apparently disaster reasons too countless list.

then started learn errors the ways, looked proceed auto-build whole concentration dedicated build machine. note during unequivocally opposing bringing outmost tools, built the possess autobuild component minute vb app.

this worked glorious while, until project's structure started change, new projects added, indispensable build concentration opposite ways. following then weaknesses the hand-rolled autobuilder became apparent and, over time, increasingly onerous. illness progressed indicate where qa (who owns the build process) can't even say autobuilder since requires some-more more programming skill. each supplement digest change something an existent project, consumes some-more developer only work. there have days amateurish furnish build since component broken.

i'm position where i change process, i'm looking throw whole component put something else it's place. goals are:

• have an autobuild component run 0 tellurian communication during specific each day. should means accumulate source code, accumulate apps, emanate setups, put finished products network share, presumably trigger involuntary contrast component whip (we qtp).


• the autobuild component should stretchable adequate simply adjust changes digest but rrequiring vital overhaul.


• it should rudimentary adequate qa possess component need developer resources changes builds made.

what your experiences? advise an autobuild system? should i have opposite goals?