<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Build Manifesto</title>
	<atom:link href="http://evan.bottch.com/2010/06/16/build-manifesto/feed/" rel="self" type="application/rss+xml" />
	<link>http://evan.bottch.com/2010/06/16/build-manifesto/</link>
	<description>// TODO: think of a witty and intelligent tagline</description>
	<lastBuildDate>Tue, 03 Jan 2012 20:08:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Chris Brown</title>
		<link>http://evan.bottch.com/2010/06/16/build-manifesto/comment-page-1/#comment-968</link>
		<dc:creator>Chris Brown</dc:creator>
		<pubDate>Thu, 17 Jun 2010 09:23:52 +0000</pubDate>
		<guid isPermaLink="false">http://evan.bottch.com/?p=105#comment-968</guid>
		<description>In fact for us this is an advantage for us because the build server machines have a lot more power than our hamster powered desktops. This makes the remote build much faster than it is locally.</description>
		<content:encoded><![CDATA[<p>In fact for us this is an advantage for us because the build server machines have a lot more power than our hamster powered desktops. This makes the remote build much faster than it is locally.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: evan</title>
		<link>http://evan.bottch.com/2010/06/16/build-manifesto/comment-page-1/#comment-964</link>
		<dc:creator>evan</dc:creator>
		<pubDate>Wed, 16 Jun 2010 22:56:27 +0000</pubDate>
		<guid isPermaLink="false">http://evan.bottch.com/?p=105#comment-964</guid>
		<description>My main fear with the remote pre-checkin build has been that it takes away once force which keeps local pre-commit builds short in duration.  I&#039;ve never used it though so that&#039;s probably not true.  Any other drawbacks?

Hudson has the Claim plugin which is quite useful too - http://wiki.hudson-ci.org/display/HUDSON/Claim+plugin</description>
		<content:encoded><![CDATA[<p>My main fear with the remote pre-checkin build has been that it takes away once force which keeps local pre-commit builds short in duration.  I&#8217;ve never used it though so that&#8217;s probably not true.  Any other drawbacks?</p>
<p>Hudson has the Claim plugin which is quite useful too &#8211; <a href="http://wiki.hudson-ci.org/display/HUDSON/Claim+plugin" rel="nofollow">http://wiki.hudson-ci.org/display/HUDSON/Claim+plugin</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Brown</title>
		<link>http://evan.bottch.com/2010/06/16/build-manifesto/comment-page-1/#comment-959</link>
		<dc:creator>Chris Brown</dc:creator>
		<pubDate>Wed, 16 Jun 2010 13:14:37 +0000</pubDate>
		<guid isPermaLink="false">http://evan.bottch.com/?p=105#comment-959</guid>
		<description>On my current project we had lots of problems with broken builds on cruise control. This was mainly because people were not running all of the tests before checking in despite our pleading. We switched to Team City and forced developers to run the build remotely and the build is now green a majority of the time. It was like flicking a switch.

Also Team City has a feature of &#039;taking responsibility&#039; for a broken build like your broken-build-token.

While I&#039;m not generally a product fan boy this did fix our problems.</description>
		<content:encoded><![CDATA[<p>On my current project we had lots of problems with broken builds on cruise control. This was mainly because people were not running all of the tests before checking in despite our pleading. We switched to Team City and forced developers to run the build remotely and the build is now green a majority of the time. It was like flicking a switch.</p>
<p>Also Team City has a feature of &#8216;taking responsibility&#8217; for a broken build like your broken-build-token.</p>
<p>While I&#8217;m not generally a product fan boy this did fix our problems.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

