Jonathan Share wrote:
On 6/25/08, rko618 [EMAIL PROTECTED] wrote:
I'm not sure what SCM you are using but I know with Git you can use
this option in deploy.rb to specify the branch
set :branch, master
Are there any pre-baked solutions for this in other SCM's (subversion,
for
Are there any pre-baked solutions for this in other SCM's (subversion,
for example)?
The closest I've found so far is the following, but it looks pretty
dirty and adds extra dependencies.
http://voxpopnetwork.com/codex/2008/01/15/capistrano-20-and-tagged-releases/
I use it:
...
set
This is what I do for something similar. You can just change the
reference to tags to branches. No hard-coding of branches is
necessary as you will be prompted.
desc Specify tag to pull - defaults to Head revision if no tag is
specified
task :before_update_code do
set :svn_tag,
In fact, since :repository can be set at any point before update_code, I
actually have two things: I detect the branch we're actually deploying from,
and then I create a new tag for each staging deploy. Production deploys
always pull the latest staging tag, thus forcing you to test something at
I'm not sure what SCM you are using but I know with Git you can use
this option in deploy.rb to specify the branch
set :branch, master
On Jun 25, 1:03 am, ChandleWEi [EMAIL PROTECTED] wrote:
How to deploying a branch
I can't use -Sbranch=1.0 and ENV[branch]
how set branch and deploy
thx
在 2008-06-25三的 10:29 -0700，rko618写道：
I'm not sure what SCM you are using but I know with Git you can use
this option in deploy.rb to specify the branch
set :branch, master
On Jun 25, 1:03 am, ChandleWEi [EMAIL PROTECTED] wrote:
How to deploying a branch
I can't use -Sbranch=1.0
On Jan 7, 2007, at 9:06 PM, Charles Brian Quinn wrote:
For a client, we altered the repository line to read:
set :repository,
https://svn.server.com/#{application}/tags/#{ENV['DEPLOY_VERSION']}
so now it is deployed with:
cap deploy DEPLOY_VERSION=1.2.5
hope that helps
On 1/7/07,
