Continuous builds and Agile vs commit often

Posted by Mark Underwood on Stack Overflow See other posts from Stack Overflow or by Mark Underwood
Published on 2009-08-17T03:40:04Z Indexed on 2010/03/15 17:49 UTC
Read the original article Hit count: 361

Hi All,

I'm just doing some formal training in Agile at the moment and one question I have is about the value of Continuous Builds vs value of committing to the version control system often.

My understanding with version control is that its better to commit often, because then you have history and the ability to go back to previous changes in a fine grained way.

My understanding with Agile and continuous build is that its there to put pressure on the developers to always have working code. That to break the source tree is a taboo thing to do.

Now i agree with both of these sentiments, but it occurs to be that sometimes these might be working against each other. You maybe in the middle of a largish code change and want to commit code to make sure you have history, but this will break the source tree.

Anybody got any thoughts on this?

Cheers

Mark.

© Stack Overflow or respective owner

Related posts about agile

Related posts about continuous-integration