Have you and your team ever found yourselves in a crunch the day before a release is supposed to go out? “Was that bug fixed?”, “Can we finish this feature?”, “Did I overwrite your code?”, “What version of the library are you using?”. There are tools to help us get organized, but sometimes it can get a little overwhelming with all the available options. What about quality? As developers we can write unit tests, but how do we know when quality has improved? How do we know something one developer codes won’t break something else another developer has done? How can we coordinate organization and quality and all the other pieces to the puzzle together?

In this month’s meeting, we’re going to dive into the topic of continuous integration. Continuous integration is an approach that can help us, as developers, stream-line the approach to answering the above questions. I’m going to approach the problem from the perspective of using Flex, but will have tips for anyone building web-based applications. I’ll be showing how to use Hudson, Ant, the Flex SDK, and fluint all together to create a continuous integration feedback loop. Feedback is everything in continuous integration, which where the fun can come into play.

Hope you can make it out on February 9th. See you then!