CIS 427

IS Plan/Mgmt | DSU Spr’09

Presentation: Sean Callahan on Groove

Sean gives us the lowdown on Groove:

callahan-groovereview

Sean welcomes your comments and questions!

2009.03.19 Posted by | Class Meetings | , , | Leave a Comment

Continuous Integration

Finally it’s here! Programmers have been working together for year to build projects and the biggest problem has been integrating the codes together now with continuous integration it allows programmers to the ability to program in harmony.

Continuous integration is a technique that encourages developers to check-in their code more frequently, have it compiled by an automated process, run a suite of unit tests, and report on the status. The idea is to tighten the feedback loop so that the effect of an integrated change is communicated back to the developer as soon as possible. By reducing the time between check-in and build status, developers find it much easier to identify faulty code.

This article by Steve McConnell shows the benefits of daily building and smoke tests while building projects. Some developers think it’s unpractical to build daily but even on some of the biggest projects many programmers give credit to daily builds to completing their programs.

This article by Mike Swanson, a technical evangelist, explains some online programming sites and how it benefited him. Take a look it’s a strong step and I’m sure you will be seeing more of it in the IT fields.

2009.02.02 Posted by | tech | , | 1 Comment

   

Follow

Get every new post delivered to your Inbox.