<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <title>studios.thoughtworks.com - Deployment Pipelines: Revolutionizing Release Management Comments</title>
  <id>tag:studios.thoughtworks.com,2008:/2008/4/30/deployment-pipelines-revolutionizing-release-management/comments</id>
  <generator version="0.8.0" uri="http://mephistoblog.com">Mephisto Drax</generator>
  <link href="http://studios.thoughtworks.com/2008/4/30/deployment-pipelines-revolutionizing-release-management/comments.xml" rel="self" type="application/atom+xml"/>
  <link href="/2008/4/30/deployment-pipelines-revolutionizing-release-management" rel="alternate" type="text/html"/>
  <updated>2008-05-29T17:05:43Z</updated>
  <entry xml:base="http://studios.thoughtworks.com/">
    <author>
      <name>Sargon Benjamin</name>
    </author>
    <id>tag:studios.thoughtworks.com,2008-04-30:1062:1079</id>
    <published>2008-05-23T18:06:24Z</published>
    <updated>2008-05-23T18:06:24Z</updated>
    <category term="Blog"/>
    <link href="http://studios.thoughtworks.com/2008/4/30/deployment-pipelines-revolutionizing-release-management" rel="alternate" type="text/html"/>
    <title>Comment on 'Deployment Pipelines: Revolutionizing Release Management' by Sargon Benjamin</title>
<content type="html">Can't wait to here more about Cruise! From what I gather, most teams that use CruiseControl are hacking away at setting up a test environment and then executing functional tests via a combination of post build publishers, listeners, and ant targets that execute shell scripts.  Results then have to reported back some how and this may involve custom modification of the dashboard to report on the FVT results.  
I've used STAF to set up a test farm and have thought about setting this up with CruiseControl to execute and report on FVT tests.  Considering the effort, I may just wait on more press about Cruise before doing so.  Keep it up!</content>  </entry>
</feed>
