rake release fails silently when gemcutter asks for a password

[zilkey]

if you create a gem with bundle gem, then try to push that gem and you don't have gemcutter credentials installed on your machine, gemcutter will prompt for credentials. However, the bundle rake task doesn't display the output from gemcutter.

This rake task should probably either raise an error or display the interactive prompt.

[ahawkins]

I also have experienced this issue. Seems the code does not capture the output directly to show the bundler prompt. Here is a console log for your reference.

imac:cashier adam$ rake release
(in /Users/adam/Projects/cashier)
cashier 0.2.0 built to pkg/cashier-0.2.0.gem
Tagged v0.2.0
Pushed git commits and tags
^Crake aborted!


(See full trace by running task with --trace)
You have new mail in /var/mail/adam
imac:cashier adam$ 
imac:cashier adam$ 
imac:cashier adam$ gem push 
..gemspec        .infinity_test   Gemfile          Rakefile         pkg/             
.git/            .rspec           Gemfile.lock     cashier.gemspec  readme.md        
.gitignore       .rvmrc           LICENSE.txt      lib/             spec/            
imac:cashier adam$ gem push pkg/cashier-0.2.0.gem 
Enter your RubyGems.org credentials.
Don't have an account yet? Create one at http://rubygems.org/sign_up
   Email:   [email protected]
Password:   
Signed in.
Pushing gem to RubyGems.org...
Successfully registered gem: cashier (0.2.0)
imac:cashier adam$ gem -v
1.3.7
imac:cashier adam$ bundle -v
1.0.10

[tcurdt]

same here

$ gem -v
1.3.7
$ bundle -v
Bundler version 1.0.10

[owahab]

Same here.

Mac OS X 10.6.7
Ruby 1.9.2 (RVM)
Gem 1.5.2
Bundle 1.0.10

[bjoernalbers]

Me too.

Mac OS X 10.6.7
Ruby 1.8.7
Gems 1.8.5
Bundler 1.0.14

[owahab]

Of course, the current workaround is to run
gem push

[thbar]

Same here today.