joshgoebel
commented
12 years ago Please try my sprinkle/new_api branch. It should have much improved error reporting, I wonder if it catches your issue.
Closed cleeland closed 12 years ago
joshgoebel
commented
12 years ago Please try my sprinkle/new_api branch. It should have much improved error reporting, I wonder if it catches your issue.
cleeland
commented
12 years ago Do I need to change my sprinkle setup? Do I need to uninstall the original installation of sprinkle or can I run your branch out of the clone/checkout? I get the following:
$ /home/ccleeland/localbuilds/sprinkle/bin/sprinkle -c -t -s install.rb
Only running policies for :
./exelerate.rb:6: undefined method `package' for main:Object (NoMethodError)
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /usr/lib/ruby/gems/1.8/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `require'
from /usr/lib/ruby/gems/1.8/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:236:in `load_dependency'
from /usr/lib/ruby/gems/1.8/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `require'
from install.rb:1:in `sprinkle'
from /home/ccleeland/localbuilds/sprinkle/bin/sprinkle:108
joshgoebel
commented
12 years ago What is in your install.rb? Perhaps pastie.org it.
cleeland
commented
12 years ago It's too big and has some local stuff that I'd rather not put on a public website, but I've reproduced the issue with a cut-down version:
$ /home/ccleeland/localbuilds/sprinkle/bin/sprinkle -s inst.rb
Only running policies for :
./foo.rb:1: undefined method `package' for main:Object (NoMethodError)
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
from /usr/lib/ruby/gems/1.8/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `require'
from /usr/lib/ruby/gems/1.8/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:236:in `load_dependency'
from /usr/lib/ruby/gems/1.8/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in `require'
from inst.rb:1:in `sprinkle'
from /home/ccleeland/localbuilds/sprinkle/bin/sprinkle:108
$ cat inst.rb
require 'foo.rb'
policy :legacy, :roles => :core do
requires :binaries
end
deployment do
delivery :capistrano do
recipes 'deploy.rb'
end
end
$ cat deploy.rb
set :run_method, :run
#set :debug, true
#set :verbose, 1
default_run_options[:pty] = true
$ cat foo.rb
package :show_binaries, :provides => :binaries do
%w{ls cat}.each do |bin|
runner "ls -l /bin/#{bin}"
end
end
cleeland
commented
12 years ago I have not done a "gem install". All I did was clone your repo, checkout the new_api branch, done a "rake build", and tried to run using a full path to sprinkle binary.
joshgoebel
commented
12 years ago Yeah, that could be your problem. What I do is a symlink.
~/git/sprinkle (my actual sprinkling working dir)
~/git/sprinkle_using_project (my actual app/sprinkle repository) ~/git/sprinkle_using_project/sprinkle -> ~/git/sprinkle/ (symlink to sprinkle repo)
cd ~/git/sprinkle_using_project ./sprinkle/bin/spinkle -args -whatever
Thanks, Josh Goebel
On Oct 9, 2012, at 5:59 PM, Chris Cleeland notifications@github.com wrote:
I have not done a "gem install". All I did was clone your repo, checkout the new_api branch, done a "rake build", and tried to run using a full path to sprinkle binary.
— Reply to this email directly or view it on GitHub.
cleeland
commented
12 years ago I did a "sudo rake install" and that improved things for my small case, but when I run it for my actual setup, I get the following:
WARNING: I'm a noob with capistrano and sprinkle.
I just spent the better part of the day tracking down why I couldn't deploy. I'm trying to use sprinkle to push out development binaries (executables compiled and linked from C++ code) to a test server (ultimately I would like to extend sprinkle to control running the tests, but that's later). scp kept failing.
It turns out that the "problem" was that the very first binary it was trying to push out was running on the target, so scp was failing with a "text file busy" error. Either capistrano wasn't communicating that back to sprinkle, or sprinkle was squelching the error. In any case, it took more investigation and unrolling of the source to dig out an understanding of what was happening.
What should be reporting the error? Am I looking in the wrong place?
Finally, is this the best place to ask questions about sprinkle, or is there a better community forum?