Continuous Integration is a software development practice where members of a team integrate their work frequently/daily. Each integration would be verified by an automated build to detect errors. By doing integration frequently/daily, there are less integration problems and it allows the team to develop software quickly.
What we are using for our watt-depot-cli project is Hudson. We configured Hudson to work side by side with SVN, which checks changes made to the project. Whenever changes are made to the project, Hudson would ensure that everything is working correctly. If it is not, it would send email notifications to whoever is associated with the project. This great feature allows developers to know that there was an update made that failed, and it can be fixed by anyone.
Right away when testing small parts of our code, I could see the benefits of using continuous integration. It keeps the user updated for every single thing. Also, it gives little symbols of what is going on with the code and if the code is working correctly or not.
One small problem I see with Hudson is that the little cloud symbols don't give the right symbol. It starts off with a sun saying everything is great and running correctly. Then when we tested Hudson to see if it works with our project, it gives a little cloud. Which was correct because we were just testing it. But when we fixed it, it did not change back to the sun. If anyone was to just look at that symbol, they would think that the code is not doing what it is suppose to do even though it is fine.
I think that this is a great tool to use when in a group project. If you cannot meet with the group all the time, this tool helps by keeping you updated.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment