Capistrano split error

416 views
Skip to first unread message

byrnejb

unread,
Nov 29, 2013, 4:24:00 PM11/29/13
to capis...@googlegroups.com
Arch = i86_64
OS = CentOS-6.4 (RHEL6)
Ruby = v.2.0.0.p353
Rails = 4.0.1
Capistrano 2.15.5

We are trying to deploy a complex recipe which was last used this past January and worked then without error. At that time we were using Ruby-1.9.3 and RoR-3.2.8.  We have updated our application to Ruby-2. and RoR-4.0.1 and have installed Ruby-2.0.0 on the deployment target.  When we do a --dry-run of the deployment we are getting this error:

    from /usr/lib64/ruby/gems/2.0.0/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy/scm/git.rb:230:in `query_revision': undefined method `split' for #<Array:0x000000013cf068> (NoMethodError)
.  .  .


See https://gist.github.com/anonymous/7712107

It appears to me that this may be related to the empty array at variables.rb:95:
.  .  .
    from /usr/lib64/ruby/gems/2.0.0/gems/capistrano-2.15.5/lib/capistrano/configuration/variables.rb:110:in `synchronize'
    from /usr/lib64/ruby/gems/2.0.0/gems/capistrano-2.15.5/lib/capistrano/configuration/variables.rb:110:in `protect'
    from /usr/lib64/ruby/gems/2.0.0/gems/capistrano-2.15.5/lib/capistrano/configuration/variables.rb:78:in `fetch'
    from /usr/lib64/ruby/gems/2.0.0/gems/capistrano-2.15.5/lib/capistrano/configuration/variables.rb:95:in `[]'
    from /usr/lib64/ruby/gems/2.0.0/gems/capistrano-2.15.5/lib/capistrano/recipes/deploy/strategy/base.rb:86:in `revision'


Does anyone have any suggestions as to where I should look?  Does this look like a configuration error in deploy.rb?

This recipe is very, very customized and quite large.  Undertaking a complete rewrite to get it to work with Capistrano 3 is not in the budget.

Donovan Bray

unread,
Nov 29, 2013, 5:42:48 PM11/29/13
to capis...@googlegroups.com
Split is a string method not an Array method in 1.9.3 nor ruby 2.0

How are you setting the branch to be deployed?

How are you setting the repo for git?

What version of git are you running locally?
--
--
* You received this message because you are subscribed to the Google Groups "Capistrano" group.
* To post to this group, send email to capis...@googlegroups.com
* To unsubscribe from this group, send email to capistrano+...@googlegroups.com For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
---
You received this message because you are subscribed to the Google Groups "Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

byrnejb

unread,
Dec 2, 2013, 9:24:30 AM12/2/13
to capis...@googlegroups.com


On Friday, 29 November 2013 17:42:48 UTC-5, dbray wrote:
Split is a string method not an Array method in 1.9.3 nor ruby 2.0

How are you setting the branch to be deployed?
 
# Deploy this version. This is an SCM/VCS repository branch, not a tag.
set( :branch,  "ForEx-Deploy-V.04.000.0000rc1" )


How are you setting the repo for git?

# Define VCS/SCM characteristics
set( :scm, "git" )
 
What version of git are you running locally?

 $ git --version
git version 1.7.1


Donovan Bray

unread,
Dec 2, 2013, 1:30:31 PM12/2/13
to capis...@googlegroups.com
I don't see anything illegal with your naming, though I don't like mixing separators. 

Are you sure that branch exists exactly as specified?

What is your repository set as?

Have you verified that you have access to the repository both locally and remotely (with the deploy user?)
--
You received this message because you are subscribed to the Google Groups "Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+...@googlegroups.com.

byrnejb

unread,
Dec 2, 2013, 4:25:28 PM12/2/13
to capis...@googlegroups.com
This may have been overtaken by events.  I have another somewhat related question open at the moment respecting a logon issue with ssh inside capistrano.  Since the recipe is now running to that extent it may be that whatever was causing this problem has been repaired or removed.  It may be that once I get past the logon issue then this problem might resurface.  For the moment however, I think we can let this matter rest.

Reply all
Reply to author
Forward
0 new messages