<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/wordpress-mu-1.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: CruiseControl + SVN</title>
	<link>http://blog.generationjava.com/roller/bayard/entry/200702161</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 12:49:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.1</generator>

	<item>
		<title>By: Shannon Krebs</title>
		<link>http://blog.generationjava.com/roller/bayard/entry/200702161#comment-38</link>
		<author>Shannon Krebs</author>
		<pubDate>Sun, 18 Feb 2007 15:44:50 +0000</pubDate>
		<guid>http://blog.generationjava.com/roller/bayard/entry/200702161#comment-38</guid>
		<description>Configuration files do have their place.  I've certainly setup some complicated builds before in CC that you want to be able to hack around with the config file (and be able to restore a previous version when you mess it up).

If you are using something like maven for your builds in theory all of the information you need to build your project should already be defined in the pom file. So all your CI server should need from you is the link to where it can download the pom file and what goal to run. Which makes a web interface easier (in my opinion).  Ultimately it depends on the project and what you are using to build it. I good CI server should provide both options. I think CC has made some moves towards a web config interface recently, but the last release I tried it was only experimental.

(In the case of maven, I guess you are really just substituting the config file in your CI server for the maven config file in your project.)</description>
		<content:encoded><![CDATA[<p>Configuration files do have their place.  I&#8217;ve certainly setup some complicated builds before in CC that you want to be able to hack around with the config file (and be able to restore a previous version when you mess it up).</p>
<p>If you are using something like maven for your builds in theory all of the information you need to build your project should already be defined in the pom file. So all your CI server should need from you is the link to where it can download the pom file and what goal to run. Which makes a web interface easier (in my opinion).  Ultimately it depends on the project and what you are using to build it. I good CI server should provide both options. I think CC has made some moves towards a web config interface recently, but the last release I tried it was only experimental.</p>
<p>(In the case of maven, I guess you are really just substituting the config file in your CI server for the maven config file in your project.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henri Yandell</title>
		<link>http://blog.generationjava.com/roller/bayard/entry/200702161#comment-37</link>
		<author>Henri Yandell</author>
		<pubDate>Sat, 17 Feb 2007 23:42:09 +0000</pubDate>
		<guid>http://blog.generationjava.com/roller/bayard/entry/200702161#comment-37</guid>
		<description>What I mean Phil is that I don't want svn update running when a build is not needed. If I use the svnbootstrapper, then everytime it looks to see if a build is needed (ie: svn -u status or svn info) it will also run svn update.

This is an unnecessary load on the server.</description>
		<content:encoded><![CDATA[<p>What I mean Phil is that I don&#8217;t want svn update running when a build is not needed. If I use the svnbootstrapper, then everytime it looks to see if a build is needed (ie: svn -u status or svn info) it will also run svn update.</p>
<p>This is an unnecessary load on the server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Wilson</title>
		<link>http://blog.generationjava.com/roller/bayard/entry/200702161#comment-36</link>
		<author>Phil Wilson</author>
		<pubDate>Sat, 17 Feb 2007 17:03:27 +0000</pubDate>
		<guid>http://blog.generationjava.com/roller/bayard/entry/200702161#comment-36</guid>
		<description>"I don't want to run svn update every time, just when a build is needed."

That's quite an interesting statement. When do you see a build being needed that doesn't use the latest code?</description>
		<content:encoded><![CDATA[<p>&#8220;I don&#8217;t want to run svn update every time, just when a build is needed.&#8221;</p>
<p>That&#8217;s quite an interesting statement. When do you see a build being needed that doesn&#8217;t use the latest code?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
