Yep, I think you got it in one.  You could, for now, create both files
so either version will have what it needs, perhaps.  The newer version
will continue to cleanup old credentials though, so you may have to
recreate theme in some cases (depending on your usage).  It may also
be helpful to note that for a little while now the client itself will
return whatever api key it knows about via `heroku auth:token`.  You
may be able to use that in order to not worry as much about where the
credentials come from.  Anyway, if you get stuck again or have other
questions let us know and we'll try to get you going again.
Thanks!
wes

On Mar 12, 7:26 am, dblock <[email protected]> wrote:
> I think I figured it out.
>
> Heroku now migrates credentials from .heroku to .netrc. We have two
> builds with different heroku-gem versions running on these machines.
> So the newer one migrates credentials away.
>
> Relevant code 
> inhttps://github.com/heroku/heroku/blob/master/lib/heroku/auth.rb
>
> -dB.
>
> On Mar 11, 9:42 am, Neil Middleton <[email protected]> wrote:
>
>
>
>
>
>
>
> > The Heroku gem creates a credentials file in your home directory, so I'd 
> > start with replicating that.
>
> > Neil
>
> > On 11 Mar 2012, at 13:26, dblock <[email protected]> wrote:
>
> > > It seems that heroku rake wants more than just the SSH key setup on
> > > the client. We want to use this in automation and we keep getting
> > > these after a couple of days:
>
> > > 04:46:45  [2012-03-11 05:46:45 -0400] bundle exec heroku rake ...
> > > 04:46:50  /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/heroku-2.18.1/
> > > lib/heroku/helpers.rb:87:in `ask': undefined method `strip' for
> > > nil:NilClass (NoMethodError)
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
> > > heroku-2.18.1/lib/heroku/auth.rb:96:in `ask_for_credentials'
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
> > > heroku-2.18.1/lib/heroku/auth.rb:137:in `ask_for_and_save_credentials'
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
> > > heroku-2.18.1/lib/heroku/auth.rb:71:in `get_credentials'
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
> > > heroku-2.18.1/lib/heroku/auth.rb:51:in `user'
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
> > > heroku-2.18.1/lib/heroku/auth.rb:11:in `client'
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
> > > heroku-2.18.1/lib/heroku/command/base.rb:38:in `heroku'
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
> > > heroku-2.18.1/lib/heroku/command/run.rb:74:in `rake'
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
> > > heroku-2.18.1/lib/heroku/command.rb:129:in `run'
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
> > > heroku-2.18.1/lib/heroku/cli.rb:9:in `start'
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/gems/
> > > heroku-2.18.1/bin/heroku:15:in `<top (required)>'
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/bin/heroku:
> > > 19:in `load'
> > > 04:46:50      from /home/jenkins/.rvm/gems/ruby-1.9.2-p290/bin/heroku:
> > > 19:in `<main>'
> > > 04:46:50  Enter your Heroku credentials.
> > > 04:46:50  Email: rake aborted!
> > > 04:46:50  failed with exit code 1
>
> > > How can we save / store credentials so that this doesn't happen?
>
> > > --
> > > You received this message because you are subscribed to the Google Groups 
> > > "Heroku" group.
> > > To post to this group, send email to [email protected].
> > > To unsubscribe from this group, send email to 
> > > [email protected].
> > > For more options, visit this group 
> > > athttp://groups.google.com/group/heroku?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Reply via email to