<?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: Configurable Builds: One configuration file per user</title>
	<atom:link href="http://www.markhneedham.com/blog/2008/09/02/configurable-builds-one-configuration-file-per-user/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2008/09/02/configurable-builds-one-configuration-file-per-user/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Sat, 11 Feb 2012 23:17:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Gil Peeters</title>
		<link>http://www.markhneedham.com/blog/2008/09/02/configurable-builds-one-configuration-file-per-user/comment-page-1/#comment-263</link>
		<dc:creator>Gil Peeters</dc:creator>
		<pubDate>Tue, 09 Sep 2008 22:04:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=284#comment-263</guid>
		<description>Mark,

On a project we are working on, we use machine specific configuration files. Each Dev machine has it&#039;s own configuration, based on the Host name of the developer machine, and each CI build (multiple builds per build server) get&#039;s it&#039;s own based on the build host and build name.

Advantages of this approach (for dev machines) are:
1) Paring and pair rotation become easy.
2) External Resources can be assigned to a dev machine 

G./</description>
		<content:encoded><![CDATA[<p>Mark,</p>
<p>On a project we are working on, we use machine specific configuration files. Each Dev machine has it&#8217;s own configuration, based on the Host name of the developer machine, and each CI build (multiple builds per build server) get&#8217;s it&#8217;s own based on the build host and build name.</p>
<p>Advantages of this approach (for dev machines) are:<br />
1) Paring and pair rotation become easy.<br />
2) External Resources can be assigned to a dev machine </p>
<p>G./</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Configurable Builds: Overriding properties at Mark Needham</title>
		<link>http://www.markhneedham.com/blog/2008/09/02/configurable-builds-one-configuration-file-per-user/comment-page-1/#comment-164</link>
		<dc:creator>Configurable Builds: Overriding properties at Mark Needham</dc:creator>
		<pubDate>Tue, 02 Sep 2008 13:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=284#comment-164</guid>
		<description>[...] when configuring our build for flexibility we don&#039;t need to spend the time required to create one build configuration per user or one build configuration per [...]</description>
		<content:encoded><![CDATA[<p>[...] when configuring our build for flexibility we don&#8217;t need to spend the time required to create one build configuration per user or one build configuration per [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

