Note that there are some explanatory texts on larger screens.

plurals
  1. POAutomated Deployment in Rails
    primarykey
    data
    text
    <p>I'm working on my first rails app and am struggling trying to find an efficient and clean solution for doing automated checkouts and deployments.</p> <p>So far I've looked at both <a href="http://cruisecontrolrb.thoughtworks.com/" rel="nofollow noreferrer">CruiseControl.rb</a> (having been familiar with CruiseControl.NET) and <a href="http://www.capify.org/index.php/Capistrano" rel="nofollow noreferrer">Capistrano</a>. Unfortunately, unless I'm missing something, each one of them only does about half of what I want (with each one doing a different half).</p> <p>For what I've seen so far:</p> <p>CruiseControl</p> <ul> <li>Strengths <ul> <li>Automated builds on repository checkouts upon commit</li> <li>Also runs unit/functional tests and reports back</li> </ul></li> <li>Weaknesses <ul> <li>No built-in deployment mechanisms (best I can find so far is writing your own bash scripts)</li> </ul></li> </ul> <p>Capistrano</p> <ul> <li>Strengths <ul> <li>Built for deployments</li> </ul></li> <li>Weaknesses <ul> <li>Has to be kicked off via a command (i.e. doesn't do automated checkouts upon commit)</li> </ul></li> </ul> <p>I've found ways that I can string the two together -- i.e. have CruiseControl ping the repository for changes, do a checkout upon commit, run the tests, etc. and then make a call to Capistrano when finished to do the deployment (even though Capistrano is also going to do a repository checkout).</p> <p>Basically, when all is said and done, I'd like to have three projects set up:</p> <ul> <li>Dev: Checkout/Deployment is entirely no touch. When someone commits a file, something checks it out, runs the tests, deploys the changes, and reports back</li> <li>Stage: Checkout/Deployment requires a button click</li> <li>Prod: Button click does either a tagged check out or moves the files from stage</li> </ul> <p>I have this working with a combination of CruiseControl.NET and MSBuild in the .NET world, and it was fairly straightforward. I would guess this is also a common pattern in the ruby deployment world, but I could easily be mistaken.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload