Hmm...  this doesn't seem to work.  I was under the impression that
all of the Gem packaging was happening locally, with a git hook, but
it must be happing on heroku's end in a post-receive or something as
you can see it fails with a public key denied.  Here's my output:

Fetching g...@github.com:myuser/mygem.git
       Failed to add the host to the list of known hosts (/home/
group_home/.ssh/known_hosts).
       Permission denied (publickey).
       fatal: The remote end hung up unexpectedly
        [31mAn error has occurred in git when running `git clone
"g...@github.com:myuser/mygem.git" "/disk1/tmp/
11105_23612559740460/.bundle/gems/ruby/1.9.1/cache/bundler/git/
mygem.gem-ff17e89eb8ea82cbae23a3129c9eefc29d94db65" --bare --no-
hardlinks. Cannot complete bundling. [0m
       FAILED: Have you updated to use a 0.9 Gemfile?
       http://docs.heroku.com/gems#gem-bundler

It's odd that it's asking about 0.9 Gemfile but I assume this is just
a consequence of the failed gem fetching.  So does anyone have any
suggestions as to how I can allow Heroku to pull this gem?  Is there a
key for the Heroku 'group_home' user that I can add to my repo?
That'd be handy (and hopefully secure)  I suppose I could, as
mentioned, also vendor the gem and commit on push but it seems like an
extra couple of steps that I'm hoping are avoidable.

Brad

On Aug 9, 5:13 pm, Bradley <bradleyrobert...@gmail.com> wrote:
> Well my CI server already has access to the github repo (added its key
> to github) in order to build my apps/gems, so presumably I should just
> be able to use the git source as normal, and when I do the heroku
> push, I'm assuming it's this CI user that will be doing the bundling
> before pushing to Heroku, so it shouldn't require any extra auth
> config.  I'm going to try that tonight and we'll post my findings.
>
> On Aug 9, 3:00 pm, David Balatero <dbalat...@gmail.com> wrote:
>
>
>
> > If you could package a custom SSH pub/private keypair with your Gemfile, you
> > could then:
>
> > 1) Add that pub key to Github
> > 2) Set the :git source in the Gemfile for your private gem to point at your
> > private SSH Github URL.
>
> > However, I don't believe Bundler supports having an embedded public/private
> > keypair. It would be an interesting patch, though.
>
> > Currently, I just script/plugin install --force my private plugin from
> > Github every time I update it, which I hate.
>
> > - David
>
> > On Mon, Aug 9, 2010 at 11:55 AM, Andrew C. <andrew.c...@gmail.com> wrote:
> > > You can vendor the gem too.
>
> > > On Aug 9, 9:44 am, Bradley <bradleyrobert...@gmail.com> wrote:
> > > > Ya I'm just wondering the best way to reference this gem.  For
> > > > instance, the gem location will be different on my local machine
> > > > during dev as on my CI machine during build/deploy.
>
> > > > I'm using github and I've noticed that Bundler can use :git as a
> > > > source,  I assuming Heroku's deploy does this the Gem bundling locally
> > > > before pushing, so maybe my best bet is to use that repo as the source
> > > > and as long as my CI server has access to that private github repo,
> > > > all should be gravy?
>
> > > > On Aug 8, 9:34 pm, Michishige Kaito <chris.webs...@gmail.com> wrote:
>
> > > > >   El 08/08/10 22:23, Bradley escribi :
>
> > > > > > I'm writing a new app that uses a custom gem not publicly available
> > > on
> > > > > > gemcutter, or anywhere for that matter.  I'm building both the app
> > > and
> > > > > > gem with Hudson CI, then I'd like the app pushed to heroku by 
> > > > > > somehow
> > > > > > installing this gem and pushing.
>
> > > > > > I'm a bit confused as to how I might do this.  Do I want to bundle
> > > > > > package?  Will heroku then install the gem from vendor
> > > > > > automatically?
>
> > > > > > How do I have environment specific dependencies that work with
> > > > > > Heroku?  For instance while in development, i want to use my local
> > > > > > gem, but in Hudson I want to package the locally built gem from
> > > > > > hudson, then push my app to heroku.
>
> > > > > > I don't want these gems available publicly which is why I'm looking
> > > > > > for a good way to package the gem for my Heroku app to be able to 
> > > > > > use
> > > > > > it appropriately.
>
> > > > > > Doe this make sense?  Any suggestions/help is greatly appreciate.
>
> > > > > > **setup**
> > > > > > Hudson 1.368
> > > > > > Git 1.5.6.5
> > > > > > Bundler 1.0.0RC2
> > > > > > Heroku Stack bamboo-mri-1.9.1
> > > > > > Rails 2.3.8
>
> > > > > If you're using bundler, you can just push the gem file along with the
> > > > > rest of your app.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups
> > > "Heroku" group.
> > > To post to this group, send email to her...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > heroku+unsubscr...@googlegroups.com<heroku%2bunsubscr...@googlegroups.com>
> > > .
> > > For more options, visit this group at
> > >http://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 her...@googlegroups.com.
To unsubscribe from this group, send email to 
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Reply via email to