Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
multiple respositories to be merged into release for single deployment
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
dweber.consulting  
View profile  
 More options Sep 7 2012, 2:31 pm
From: "dweber.consulting" <dweber.consult...@gmail.com>
Date: Fri, 7 Sep 2012 11:31:34 -0700 (PDT)
Local: Fri, Sep 7 2012 2:31 pm
Subject: multiple respositories to be merged into release for single deployment

What is the Capistrano equivalent, in deploy.rb, for the following shell
commands.

$ svn export ${SVN_REPO_A} repoA
$ svn export ${SVN_REPO_B} repoB
$ cp -r repoB/* repoA/

The deployment scenario is that ${SVN_REPO_A} is a public, open-source
repository of a rails application.  When it is deployed on secure
infrastructure, all the private config details are merged from the private
{$SVN_REPO_B}.  Access to ${SVN_REPO_B} requires security clearance.

AFAIK, there is only one :repository in a deploy.rb file and it contains a
reference to only one repository.  That is, the value for :repository is a
string, it cannot be a list.  There appear to be no options to specify
multiple :repository (and associated authentication parameters).

Maybe a solution might be to use an after block with an invoke task,
something like this:

set :default_environment, {
    # Command for invoke task below (assume svn+ssh authentication works)
    'COMMAND' => 'svn export ${SVN_REPO_B} repoB && cp -r repoB/* repoA/'

}

after ("deploy:update_code") do
   # Incorporate ${SVN_REPO_B} using COMMAND above
   invoke
end

Isn't there an easier way to specify this, within the deploy.rb file?

Thanks in advance,
Darren


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
dweber.consulting  
View profile  
 More options Sep 7 2012, 5:54 pm
From: "dweber.consulting" <dweber.consult...@gmail.com>
Date: Fri, 7 Sep 2012 14:54:10 -0700 (PDT)
Local: Fri, Sep 7 2012 5:54 pm
Subject: Re: multiple respositories to be merged into release for single deployment

Resolved my question with the following:

after ("deploy:update_code") do
    PRIVATE_REPO = 'https://your-private-repo.org/config-repo/trunk/'
    run "svn export --force --username YourAuthUser --password
AuthUserPasswd #{PRIVATE_REPO} #{release_path}/",
end

The plain text password is not ideal, but it's working.

-- Darren


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »