The --deployment flag requires a Gemfile.lock. Please make sure you have checked your Gemfile.lock into version control before deploying.

[gerwinbrunner]

The original command that is created seemed to have a path issue. I made a fix for it.

The command looked like this:

cd test/releases/20120327132342 && bundle install --gemfile test/releases/20120327132342/Gemfile --path test/shared/bundle --deployment --quiet --without development test

Here the Gemfile could not be found, because we are looking in the wrong path

with the patch it looks like this and works:

cd test/releases/20120327132342 && bundle install --gemfile Gemfile --path test/shared/bundle --deployment --quiet --without development test


[indirect]

For most people (including me), this is an absolute path. Why is yours relative?

[gerwinbrunner]

Running it on an ubuntu 10.04 LTS

I think both commands are relative... (my bad) to the path I'm currently in.
And because we change in that folder with the beginning "cd test/releases/20120327132342 &&"
it will not work, cause then there needs to be the folder test/releases/20120327132342/test/releases/20120327132342/Gemfile

that's at least what I found out.

[travisbot]

This pull request fails (merged fabce69 into b3e9c1a).

[poori]

@indirect This seems to happen when you do a relative path to the deployment folder in capistrano's deploy.rb file.

set :deploy_to "relative_path"

instead of

set :deploy_to "absolute_path"

As a workaround, I changed it to an absolute path and it stopped complaining about the Gemfile.lock.

[indirect]

Sounds like it's not finding the Gemfile. Check the cap task docs for instructions on how to explicitly set the Gemfile location for the bundle install task.

On Jul 28, 2012, at 2:03 PM, poorireply@reply.github.com wrote:

@indirect This seems to happen when you do a relative path to the deployment folder in capistrano's deploy.rb file.

set :deploy_to "relative_path"

instead of

set :deploy_to "absolute_path"

I changed it to an absolute path and it stopped complaining about the Gemfile.lock.

---

Reply to this email directly or view it on GitHub:
#1799 (comment)