<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Dan Merino&#039;s Blog &#187; Build</title>
	<atom:link href="http://blog.danmerino.com/category/build/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.danmerino.com</link>
	<description>Computer Science, Entrepreneurship and Productivity</description>
	<lastBuildDate>Wed, 21 Dec 2011 06:34:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>The build process</title>
		<link>http://blog.danmerino.com/the-build-process/</link>
		<comments>http://blog.danmerino.com/the-build-process/#comments</comments>
		<pubDate>Thu, 11 Feb 2010 16:53:13 +0000</pubDate>
		<dc:creator>danmerino</dc:creator>
				<category><![CDATA[Best practice]]></category>
		<category><![CDATA[Build]]></category>

		<guid isPermaLink="false">http://blog.codingadventure.com/?p=144</guid>
		<description><![CDATA[Tweet Ensure Binary Integrity of your build: The build either works or it does not work. This way it is easier to rule out errors in different layers of the project like database or logic Builds are obtained from files &#8230; <a href="http://blog.danmerino.com/the-build-process/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<div class="bottomcontainerBox" style="border:1px solid #808080;background-color:#F0F4F9;">
			<div style="float:left; width:85px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<iframe src="http://www.facebook.com/plugins/like.php?href=http%3A%2F%2Fblog.danmerino.com%2Fthe-build-process%2F&amp;layout=button_count&amp;show_faces=false&amp;width=85&amp;action=like&amp;font=verdana&amp;colorscheme=light&amp;height=21" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width=85px; height:21px;" allowTransparency="true"></iframe></div>
			<div style="float:left; width:80px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<g:plusone size="medium" href="http://blog.danmerino.com/the-build-process/"></g:plusone>
			</div>
			<div style="float:left; width:95px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;">
			<a href="http://twitter.com/share" class="twitter-share-button" data-url="http://blog.danmerino.com/the-build-process/"  data-text="The build process" data-count="horizontal">Tweet</a>
			</div><div style="float:left; width:105px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;"><script type="in/share" data-url="http://blog.danmerino.com/the-build-process/" data-counter="right"></script></div>			
			<div style="float:left; width:85px;padding-right:10px; margin:4px 4px 4px 4px;height:30px;"><script src="http://www.stumbleupon.com/hostedbadge.php?s=1&amp;r=http://blog.danmerino.com/the-build-process/"></script></div>			
			</div><div style="clear:both"></div><div style="padding-bottom:4px;"></div><ul>
<li>Ensure Binary Integrity of your build:
<ul>
<li>The build either works or it does not work. This way it is easier to rule out errors in different layers of the project like database or logic</li>
</ul>
</li>
</ul>
<ul>
<li>Builds are obtained from files under source control:
<ul>
<li>This means that if a problem happens the error can be linked to a specific commit or tag under version control</li>
</ul>
</li>
</ul>
<ul>
<li>Build can happen remotely (production) or locally:
<ul>
<li>This allows for the same local configuration to be tested on different environments remotely (production)</li>
<li>It can also allow specific special configuration (ex: a tag under version control) to be propagated to production</li>
<li>Basically helps prevent configuration errors by removing as much as possible the human aspect</li>
</ul>
</li>
</ul>
<ul>
<li>All builds should contain a database script (under version control) that creates/restores the database  from scratch
<ul>
<li>This way each database change is linked to a version under version control and errors can be linked to each build</li>
<li>Also this makes finding bugs a lot easier as they are easier to reproduce</li>
</ul>
</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://blog.danmerino.com/the-build-process/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

