What is Continuous Integration
Continuous integration is the process of generating a build whenever a programmer checks code into the source control server. When you use this process, it is a good idea to have a dedicated build server where you can synchronize and compile the sources, and run unit tests. Software development life cycle processes evolved over time. Development teams realized the importance of having periodic builds. It started with a weekly build. Then it grew tighter when “nightlies” began, and tighter still with “hourlies.” As the benefits of frequent builds became more obvious, organizations wanted more builds. And now we have continuous integration. But nightlies still exist. Many organizations still count on them to get a formal, reliable build.
…I met an amazing group of incredibly cool people. — Elisabeth Hendrickson I went to the CITCON in Chicago… and found it to be a thoroughly enjoyable experience… It’s a small, free conference that was organized and hosted better than some large, expensive conferences I’ve been to. More importantly, it had a great set of attendees which, since CITCON is an Open Space conference, led to some truly interesting sessions. — James Shore The conference adheres to the Open Spaces idea and I have to admit I was pretty skeptical. There are no formal speakers or talks but rather semi-organized discussions surrounding the ideas that the participants put forth. Sounded pretty touchy-feely and little too hippy for me … but I have to say that I found it to be significantly more informative. — David O’Hara It was my second experience of an “OpenSpaces” conference… and I must say I really like the format… As another participant said in the wrap up session, you really feel like you’re par
