<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.7.3" -->
<rss version="2.0">
	<channel>
		<title>Continuous Integration and Enterprise Build Automation</title>
		<description>Comments for Continuous Integration and Enterprise Build Automation at http://www.cmcrossroads.com , comment 1 to 4 out of 4 comments</description>
		<link>http://www.cmcrossroads.com</link>
		<lastBuildDate>Thu, 18 Mar 2010 08:20:29 +0100</lastBuildDate>
        <generator>FeedCreator 1.7.3</generator>
		<item>
			<title>...</title>
			<link>http://www.cmcrossroads.com/cm-journal-articles/12525-continuous-integration-and-enterprise-build-automation#comment-490</link>
			<description>Some thoughts from my blog on daily builds, etc.: http://www.conifersystems.com/2008/09/18/daily-builds/

&quot;For many years it’s been a standard “best practice” of software development to have a “daily build” — or, if you prefer, a “nightly build” (example, with some impressive pictures).  But why daily?  Why not twice daily, or hourly?  If the build is broken, wouldn’t we want to know about it sooner rather than later?&quot; - Matt Craighead</description>
			<pubDate>Thu, 18 Sep 2008 12:37:01 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.cmcrossroads.com/cm-journal-articles/12525-continuous-integration-and-enterprise-build-automation#comment-489</link>
			<description>I am going to chime in here. The most common sign that the ALM is broken is that the code is built, released and deployed and then the customer screems. I have seen many environments where a step forward resulted in three steps back. The whole point of CI is to recognize problems (especially integration issues) early enough that they can be addressed without missing the deadline for the release. CI is absolutely one of the best practices in Agile/CM today. Mayank did a great job putting together several well known resources into a clear and interesting article.

As always - we love - and NEED - your feedback!

Bob Aiello
Editor in Chief
 - Bob Aiello</description>
			<pubDate>Thu, 18 Sep 2008 07:33:36 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.cmcrossroads.com/cm-journal-articles/12525-continuous-integration-and-enterprise-build-automation#comment-487</link>
			<description>Excellent article :)  Would be interesting to hear how different teams adapted and grew both the CM infrastructure and their productivity as the team/product matures.

What are the most common signs that a good ALM is breaking down?

Cheers! - stu78329</description>
			<pubDate>Thu, 18 Sep 2008 04:36:36 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://www.cmcrossroads.com/cm-journal-articles/12525-continuous-integration-and-enterprise-build-automation#comment-486</link>
			<description>Thanks for the article, I had some learnings here..We do not have hourly build concept but I see the value in it..

Most of the automations tasks you mentiond here do not take wings beyond manager's desk for some or other reasons.

I am not sure whether I  will see a &quot;perfect&quot; CM environment involving all best practices of CI and Agile. - raj2037</description>
			<pubDate>Wed, 17 Sep 2008 12:40:20 +0100</pubDate>
		</item>
	</channel>
</rss>
