<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 69: Provide CruiseControl AutoDeploy publisher</title><link href="https://sourceforge.net/p/buildprocess/feature-requests/69/" rel="alternate"/><link href="https://sourceforge.net/p/buildprocess/feature-requests/69/feed.atom" rel="self"/><id>https://sourceforge.net/p/buildprocess/feature-requests/69/</id><updated>2010-02-15T09:24:58Z</updated><subtitle>Recent changes to 69: Provide CruiseControl AutoDeploy publisher</subtitle><entry><title>Provide CruiseControl AutoDeploy publisher</title><link href="https://sourceforge.net/p/buildprocess/feature-requests/69/" rel="alternate"/><published>2010-02-15T09:24:58Z</published><updated>2010-02-15T09:24:58Z</updated><author><name>Jean-Baptiste Onofré</name><uri>https://sourceforge.net/u/onofre/</uri></author><id>https://sourceforge.net60f6ae4ff36f0d95121d878d801c9db7ccfddc3b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It can be great to "synchronize" the CruiseControl continuous integration tool.&lt;/p&gt;
&lt;p&gt;Currently, it's asynchronous: the continuous integration tool build an artifact and AutoDeploy deploys it at one time (when the user request an update or when the scheduler launch an update).&lt;/p&gt;
&lt;p&gt;Providing a CruiseControl publisher, CruiseControl can fire update on an environment or an application. So the deployment is synchronized (chained) with the build chain.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>