<?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: Best Practices: Continuous Build</title>
	<atom:link href="http://blog.brodzinski.com/2010/06/best-practices-continuous-build.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.brodzinski.com/2010/06/best-practices-continuous-build.html</link>
	<description>Dealing with software projects in real life</description>
	<lastBuildDate>Fri, 10 Feb 2012 19:07:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2010/06/best-practices-continuous-build.html#comment-14538</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Mon, 14 Jun 2010 10:15:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/?p=1849#comment-14538</guid>
		<description>Yes, build server alone is not continuous integration. It is just a starting point. On the other hand, besides your example, I know no teams which deals well without build server in terms of test automation, code analysis etc.

I consider continuous build as a starting point and prerequisite for many other engineering practices. You may run without build server at the moment but I&#039;m sure if you were starting the project once again you would setup one. I&#039;m also not so sure it wouldn&#039;t make sense to get one for the project now. You can&#039;t be sure how long all of your team members would be in place. What if someone leaves? I think newbies would appreciate having build server.
 And this is always good for testers too.</description>
		<content:encoded><![CDATA[<p>Yes, build server alone is not continuous integration. It is just a starting point. On the other hand, besides your example, I know no teams which deals well without build server in terms of test automation, code analysis etc.</p>
<p>I consider continuous build as a starting point and prerequisite for many other engineering practices. You may run without build server at the moment but I&#8217;m sure if you were starting the project once again you would setup one. I&#8217;m also not so sure it wouldn&#8217;t make sense to get one for the project now. You can&#8217;t be sure how long all of your team members would be in place. What if someone leaves? I think newbies would appreciate having build server.<br />
 And this is always good for testers too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Szymon Pobiega</title>
		<link>http://blog.brodzinski.com/2010/06/best-practices-continuous-build.html#comment-14530</link>
		<dc:creator>Szymon Pobiega</dc:creator>
		<pubDate>Mon, 14 Jun 2010 08:51:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/?p=1849#comment-14530</guid>
		<description>I think you expected me to comment about that, Pawel;) To clarify, I like continuous integration. But integration is way more, than building. If you don&#039;t have _good_ unit/integration tests, having a build server gives you close to nothing.

I recently worked on a team where we had a set of unit tests covering over 90% of our code, and (at least in my opinion) these tests were of good quality. We had a habit of first executing all the tests, then committing to source control system. It worked for us. We were all the build servers. For the team of 3 people sitting in one room is was enough.

But as you said many times, collocation solves many problems that otherwise need sophisticated tools.</description>
		<content:encoded><![CDATA[<p>I think you expected me to comment about that, Pawel;) To clarify, I like continuous integration. But integration is way more, than building. If you don&#8217;t have _good_ unit/integration tests, having a build server gives you close to nothing.</p>
<p>I recently worked on a team where we had a set of unit tests covering over 90% of our code, and (at least in my opinion) these tests were of good quality. We had a habit of first executing all the tests, then committing to source control system. It worked for us. We were all the build servers. For the team of 3 people sitting in one room is was enough.</p>
<p>But as you said many times, collocation solves many problems that otherwise need sophisticated tools.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2010/06/best-practices-continuous-build.html#comment-14331</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Sat, 12 Jun 2010 08:49:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/?p=1849#comment-14331</guid>
		<description>Well, I used to work in this kind of environment. It was a bit easier because we were working in silos so we cared only about out silo, which was like 100 engineers.

I have a couple of friends working for a local branch of a big shop and they have engineering side of their work organized well. At least in terms of continuous integration. This isn&#039;t my personal experience though.</description>
		<content:encoded><![CDATA[<p>Well, I used to work in this kind of environment. It was a bit easier because we were working in silos so we cared only about out silo, which was like 100 engineers.</p>
<p>I have a couple of friends working for a local branch of a big shop and they have engineering side of their work organized well. At least in terms of continuous integration. This isn&#8217;t my personal experience though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jfbauer</title>
		<link>http://blog.brodzinski.com/2010/06/best-practices-continuous-build.html#comment-14298</link>
		<dc:creator>jfbauer</dc:creator>
		<pubDate>Sat, 12 Jun 2010 00:53:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/?p=1849#comment-14298</guid>
		<description>Sage advice ... anyone work for a large corporate IT shop and achieved a relative continuous performance/functional test environment/methodology?  I&#039;d love to hear from you.</description>
		<content:encoded><![CDATA[<p>Sage advice &#8230; anyone work for a large corporate IT shop and achieved a relative continuous performance/functional test environment/methodology?  I&#8217;d love to hear from you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

