dpl: script provider don't work with bundler on travis

I want to deploy with Capistrano after a Travis build.

I have tried some different thinks: A. This results in a bundler: command not found: cap error

deploy:
  provider: script
  script: bundle exec cap integration deploy
  on:
    branch: master

B. This results in the same error on Travis but works on my local machine:

after_success: "[[ $TRAVIS_BRANCH = 'master' ]] && gem install dpl && dpl --provider=script --script='bundle exec cap integration deploy'"

C. This works

after_success: "[[ $TRAVIS_BRANCH = 'master' ]] && bundle exec cap integration deploy"

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 18 (6 by maintainers)

Commits related to this issue

The script provider for travis deployment doesn't work with bundler. Use after_success instead The bug: https://github.com/travis-ci/dpl/issues/336 — committed to AyudaEcuador/Ushahidi_Web by jreyes33 8 years ago
TravisCI deploy tasks jack yer bundle https://github.com/travis-ci/dpl/issues/336 Basically, each deploy step gets a clean ruby environment. This change now calls `bundle install` inside of each ste... — committed to volcano-lair/aws-verify by jmanero-r7 7 years ago
Deploy with after_script workaround of this bug: https://github.com/travis-ci/dpl/issues/336 — committed to ikuwow/query_ok by ikuwow 6 years ago
Deploy with after_script workaround of this bug: https://github.com/travis-ci/dpl/issues/336 — committed to ikuwow/query_ok by ikuwow 6 years ago
Deploy with after_script workaround of this bug: https://github.com/travis-ci/dpl/issues/336 — committed to ikuwow/query_ok by ikuwow 6 years ago
Using `after_success` instead of `deploy`, since it doesn't seem to work https://github.com/travis-ci/dpl/issues/336 — committed to podemos-info/census by leio10 6 years ago
Using `after_success` instead of `deploy`, since it doesn't seem to work https://github.com/travis-ci/dpl/issues/336 — committed to podemos-info/census by leio10 6 years ago
Using `after_success` instead of `deploy`, since it doesn't seem to work https://github.com/travis-ci/dpl/issues/336 — committed to podemos-info/census by leio10 6 years ago
Using `after_success` instead of `deploy`, since it doesn't seem to work https://github.com/travis-ci/dpl/issues/336 — committed to podemos-info/census by leio10 6 years ago
Using `after_success` instead of `deploy`, since it doesn't seem to work https://github.com/travis-ci/dpl/issues/336 — committed to podemos-info/census by leio10 6 years ago
Using `after_success` instead of `deploy`, since it doesn't seem to work https://github.com/travis-ci/dpl/issues/336 — committed to podemos-info/census by leio10 6 years ago
Using `after_success` instead of `deploy`, since it doesn't seem to work https://github.com/travis-ci/dpl/issues/336 — committed to podemos-info/census by leio10 6 years ago
Using `after_success` instead of `deploy`, since it doesn't seem to work https://github.com/travis-ci/dpl/issues/336 — committed to podemos-info/census by leio10 6 years ago

Most upvoted comments

Yes but its still a workaround

nazarhussain on Feb 7, 2017

An update would be great, since capistrano is dropping support for ruby < 2.0! https://github.com/capistrano/capistrano/commit/6015f943f4734c8744ff1534f9e455bb3f01b874

ppires on Jun 7, 2016

This works for me.

deploy:
  provider: script
    script: rvm use $(< .ruby-version) do bundle exec cap integration deploy
    skip_cleanup: true
    on:
      branch: master

wulab on May 23, 2018