<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Inner Workings: The Project Scheduler</title>
	<atom:link href="http://csut017.wordpress.com/2009/02/20/inner-workings-the-project-scheduler/feed/" rel="self" type="application/rss+xml" />
	<link>http://csut017.wordpress.com/2009/02/20/inner-workings-the-project-scheduler/</link>
	<description>Exploring the Code of CruiseControl.Net</description>
	<lastBuildDate>Mon, 21 Dec 2009 04:40:54 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Inner Workings: Project Physiology &#171; Automated Coder</title>
		<link>http://csut017.wordpress.com/2009/02/20/inner-workings-the-project-scheduler/#comment-132</link>
		<dc:creator>Inner Workings: Project Physiology &#171; Automated Coder</dc:creator>
		<pubDate>Wed, 25 Feb 2009 20:30:34 +0000</pubDate>
		<guid isPermaLink="false">http://csut017.wordpress.com/2009/02/20/inner-workings-the-project-scheduler/#comment-132</guid>
		<description>[...] I have covered how a project build is scheduled (read it here). In the previous post I covered how the scheduling mechanism works, how it ties in queues and [...]</description>
		<content:encoded><![CDATA[<p>[...] I have covered how a project build is scheduled (read it here). In the previous post I covered how the scheduling mechanism works, how it ties in queues and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Sutherland</title>
		<link>http://csut017.wordpress.com/2009/02/20/inner-workings-the-project-scheduler/#comment-126</link>
		<dc:creator>Craig Sutherland</dc:creator>
		<pubDate>Fri, 20 Feb 2009 22:03:45 +0000</pubDate>
		<guid isPermaLink="false">http://csut017.wordpress.com/2009/02/20/inner-workings-the-project-scheduler/#comment-126</guid>
		<description>Hi John,

That is definitely a doable extension, and one that we are (very) slowly moving towards. Of course, if you want to help out with it, I&#039;d be happy to help you in any way I can :-)


Craig</description>
		<content:encoded><![CDATA[<p>Hi John,</p>
<p>That is definitely a doable extension, and one that we are (very) slowly moving towards. Of course, if you want to help out with it, I&#8217;d be happy to help you in any way I can <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Craig</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://csut017.wordpress.com/2009/02/20/inner-workings-the-project-scheduler/#comment-125</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 20 Feb 2009 21:42:44 +0000</pubDate>
		<guid isPermaLink="false">http://csut017.wordpress.com/2009/02/20/inner-workings-the-project-scheduler/#comment-125</guid>
		<description>Hi Craig,

Really enjoy your posts and the amount of detail you go into.

From what you have seen do you think this is a possible extension:

1) One server becomes a master and manages a queue (i.e. it receives the requests for a project to start).

2) You can have a project on one or more servers (it just has a different host) e.g. 2

3) When a request comes in it passes to whichever of the two servers has more resources (i.e. distributing the load).

Lots of potential issues (keeping the logs, build number etc in sync) but could be useful for busier builds. 

Just a thought.

Have a good weekend.

John</description>
		<content:encoded><![CDATA[<p>Hi Craig,</p>
<p>Really enjoy your posts and the amount of detail you go into.</p>
<p>From what you have seen do you think this is a possible extension:</p>
<p>1) One server becomes a master and manages a queue (i.e. it receives the requests for a project to start).</p>
<p>2) You can have a project on one or more servers (it just has a different host) e.g. 2</p>
<p>3) When a request comes in it passes to whichever of the two servers has more resources (i.e. distributing the load).</p>
<p>Lots of potential issues (keeping the logs, build number etc in sync) but could be useful for busier builds. </p>
<p>Just a thought.</p>
<p>Have a good weekend.</p>
<p>John</p>
]]></content:encoded>
	</item>
</channel>
</rss>
