Monday, 17 December 2007

Continous Intergration

In my current job I am looking into some strategies on how to develop software efficiently and one of the best working model I know of is how software is develop in open-source. It is mind boggling to watch how companies are unable to do basic things like automated builds, automated tests, notifications about failures, release management even though they have the resources, the manpower and they work in close proximity. But I think actually all these points are the reasons why it doesn't work because they make it easy to cheat on them which over time becomes a way of how software is developed. Open-source projects on the other hand do not have a choice and because of their setup they cannot cheat and so it becomes a way of how they develop software without expensive and resource intensive tools like Clearcase, Project Management tools, (UML) Design tools and many more. Therefore the streaming lining of a project because of its open-source nature is their biggest advantage for developing great software. Another point would be that many users see the code a give more feedback than in a for-profit company but there is not much a company could do about it.

  keep on reading here

Posted by schaefera at 10:25 AM in Java

 

[Trackback URL for this entry]

Comment: Sergey Pashin at Sun, 23 Dec 3:17 PM

Andy,

You might want to check our Parabuild as well. It is a fast, reliable Continuous Integration system.

Sergey

Your comment:

(not displayed)
 

SCode: (*) Generate another code
SCode

Please enter the code as seen in the image above to post your comment.

 
 

Live Comment Preview: