<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Continuous Deployment on Craig Pardey</title>
    <link>https://www.craigpardey.com/tags/continuous-deployment/</link>
    <description>Recent content in Continuous Deployment on Craig Pardey</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 11 Feb 2012 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.craigpardey.com/tags/continuous-deployment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ControlTier: Initial Impressions</title>
      <link>https://www.craigpardey.com/post/2012-02-11-controltier-initial-impressions/</link>
      <pubDate>Sat, 11 Feb 2012 00:00:00 +0000</pubDate>
      <guid>https://www.craigpardey.com/post/2012-02-11-controltier-initial-impressions/</guid>
      <description>&lt;p&gt;For the last 2 months, we&amp;rsquo;ve been using &lt;a href=&#34;http://controltier.org&#34;&gt;ControlTier&lt;/a&gt;&#xA;to automate deployments to our integration and QA environments.  Our&#xA;deployment is a little more complicated that most Java applications because it&#xA;runs on a pseudo-grid.  That is, there are 2 clustered JBoss servers, a&#xA;database server, and 4+ Linux servers that each run about 8 Java processes.&lt;/p&gt;&#xA;&lt;p&gt;I was able to get ControlTier up and running in a few days, and defining the&#xA;jobs was relatively straightforward.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Continuous deployment</title>
      <link>https://www.craigpardey.com/post/2011-12-14-continuous-deployment/</link>
      <pubDate>Wed, 14 Dec 2011 00:00:00 +0000</pubDate>
      <guid>https://www.craigpardey.com/post/2011-12-14-continuous-deployment/</guid>
      <description>&lt;p&gt;Automation isn&amp;rsquo;t about quality, it&amp;rsquo;s about scale.  Manual processes don&amp;rsquo;t&#xA;scale.&lt;/p&gt;&#xA;&lt;p&gt;Each part of your process that you automate gets you one step closer to&#xA;continuous deployment. For many teams, automation is a Quadrant 4 activity -&#xA;not urgent, not important - but on my teams it is a Quadrant 2 activity -&#xA;important but not urgent. We allocate time each iteration to improve our&#xA;automation because it frees up more time for development.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
