3 ms·
We use a build machine. ;) Really, it's the best way to deal with releases. People develop in their own branches of the code, and them when features are ready,
by e1ven 20y ago
We use a build machine. ;)
Really, it's the best way to deal with releases. People develop in their own branches of the code, and them when features are ready, we merge back into the Trunk.
We have a machine (actually a VM) check the code for revisions, and when there is a checkin, it downloads it from svn (cvs should be similar), and then builds, and uploads.
You could do jUnit tests, etc at the same point, to ensure that everything is in sync.
It's not exactly identical, but take a look at http://www.joelonsoftware.com/articles/fog0000000023.html http://www.joelonsoftware.com/articles/fog0000000023.html
Joel points out some good reasons why build machines can really help.
-Colin
- mojuba 20y agoThanks, and the article is great. With many dynamic/VM languages though you usually don't need a build server, but only some sort of a testing server. And I think uploading to a production web server should be made by a human operator rather than automatically, once the team makes sure the update works.