Continuous Integration == Communication

Robby Russell — Tue, 02 May 2006 10:24:00 -0500

Martin Fowler has updated his Continuous Integration article.

One of the points that I appreciated reading about in this article was that when you’re working in a team, the ability to keep consistent communication. This is vital to the success of the project, just like all forms of quality communication is important during the lifespan of a project.

“Continuous Integration is all about communication, so you want to ensure that everyone can easily see the state of the system and the changes that have been made to it.”

Another point reminded me of something I recently posted about¹, which was that you should always keep your project releasable… at all times.

“To help make this work, anyone involved with a software project should be able to get the latest executable and be able to run it: for demonstrations, exploratory testing, or just to see what changed this week.”

Test. Before. You. Commit.

Fowler also mentions Ruby on Rails in regards to automating deployment practices yourself. :-)

In any event, read the article.

¹ Agile development begins within…

"Continuous Integration == Communication" by Me

Tue, 02 May 2006 18:19:16 -0500

I’ve just recently been experimenting with this technique in building my blog. I’ve never worked on a project that was releasable at every single instant of the design process. It was kind of fun envisioning an outsider checking the blog every hour or so and watching as it took form (kind of like time-lapse animation).

I will definitely be using this technique when building apps in the future.

Robby on Rails: Continuous Integration == Communication

Continuous Integration == Communication

"Continuous Integration == Communication" by Me