date:20161018

Re: [capistrano-mailing-list] Cap 2.6 - Run as another user

2016-10-18 Thread William Johnston

I'm glad to hear you got it working! Thanks for reporting back.

~Willam

On Oct 18, 2016 8:30 PM, "Gokulakrishnan Sarangaraju" <
gokul.sarangar...@gmail.com> wrote:

> Sure William. I will upgrade to 3.1 or to a latest version for future
> queries.
>
> btw i was able to solve that issue with by allowing commands to be
> executed while switching user (sudo su - admin -c "command here"). It has
> nothing to do with Capistrano version.
>
> Regards,
> Gokul
>
>
> On Tuesday, October 18, 2016 at 5:31:31 AM UTC-7, William Johnston wrote:
>>
>> I'd suggest upgrading. You might be able to find people to help you
>> with this older version, but most people (IMO) have upgraded and will
>> be able to support Capistrano 3.
>>
>> ~William Johnston
>>
>>
>> On Mon, Oct 17, 2016 at 2:21 PM, Gokulakrishnan Sarangaraju
>>  wrote:
>> > Versions:
>> >
>> > Ruby - 1.8.7
>> > Capistrano - 2.6.0
>> > Rake / Rails / etc
>> >
>> > Platform:
>> >
>> > Working onCentOS
>> > Deploying to... CentOS
>> >
>> > Logs:
>> >
>> > Even though "deployuser" has the rights to switch to "admin" user
>> without
>> > entering password, cap script is expecting password to be entered.
>> >
>> > -bash-4.1$ cap -f /tmp/captest-user.cap deploy
>> >   * executing `deploy'
>> >   * executing "whoami"
>> > servers: ["host1"]
>> > [host1] executing command
>> >  ** [out :: host1] deployuser
>> > command finished in 69ms
>> >   * executing "sudo -p 'sudo password: ' -u admin
>> > /data/myapplication/script.sh stop"
>> > servers: ["host1"]
>> > [host1] executing command
>> > Password:
>> >
>> >
>> > Files:
>> >
>> > Capfile
>> >
>> > default_run_options[:pty] = true
>> > role :app, "host1"
>> > task :deploy, roles => :app do
>> > run "whoami"
>> > run "/data/myapplication/script.sh stop", :shell => "sudo su -
>> cmsadmin"
>> > run "tail -f /home/apache-tomcat-7.0.67/logs/catalina.out | sed
>> '/^INFO:
>> > Stopping ProtocolHandler/ q'"
>> > run "sudo puppet agent --confdir=/home/puppet --waitforcert 60 --test;
>> true"
>> > end
>> >
>> > In 2.6 is there a way i can execute commands on behalf of another user
>> > ("admin" in my case)? If so how? I understand that this is possible
>> with the
>> > help of https://github.com/fundingcircle/sshkit-backends-netssh_global
>> in
>> > Cap 3.0. But i would like to know if it is achievable using 2.6 or
>> should i
>> > have to upgrade it?
>> >
>> > Any pointers will help me a lot. Thanks!
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups
>> > "Capistrano" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an
>> > email to capistrano+...@googlegroups.com.
>> > To view this discussion on the web, visit
>> > https://groups.google.com/d/msgid/capistrano/71a57de7-0950-
>> 4f2d-9786-e89825e88972%40googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Capistrano" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to capistrano+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit https://groups.google.com/d/
> msgid/capistrano/6d0877e3-41a4-44fb-9919-4de04e7a8037%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to capistrano+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/capistrano/CAJBYiQjD4zMGOpR-eEP_2QQpEOiCZbUCYBR4Y-Yn8P62mfpnPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [capistrano-mailing-list] Cap 2.6 - Run as another user

2016-10-18 Thread Gokulakrishnan Sarangaraju

Sure William. I will upgrade to 3.1 or to a latest version for future 
queries. 

btw i was able to solve that issue with by allowing commands to be executed 
while switching user (sudo su - admin -c "command here"). It has nothing to 
do with Capistrano version. 

Regards,
Gokul


On Tuesday, October 18, 2016 at 5:31:31 AM UTC-7, William Johnston wrote:
>
> I'd suggest upgrading. You might be able to find people to help you 
> with this older version, but most people (IMO) have upgraded and will 
> be able to support Capistrano 3. 
>
> ~William Johnston 
>
>
> On Mon, Oct 17, 2016 at 2:21 PM, Gokulakrishnan Sarangaraju 
>  wrote: 
> > Versions: 
> > 
> > Ruby - 1.8.7 
> > Capistrano - 2.6.0 
> > Rake / Rails / etc 
> > 
> > Platform: 
> > 
> > Working onCentOS 
> > Deploying to... CentOS 
> > 
> > Logs: 
> > 
> > Even though "deployuser" has the rights to switch to "admin" user 
> without 
> > entering password, cap script is expecting password to be entered. 
> > 
> > -bash-4.1$ cap -f /tmp/captest-user.cap deploy 
> >   * executing `deploy' 
> >   * executing "whoami" 
> > servers: ["host1"] 
> > [host1] executing command 
> >  ** [out :: host1] deployuser 
> > command finished in 69ms 
> >   * executing "sudo -p 'sudo password: ' -u admin 
> > /data/myapplication/script.sh stop" 
> > servers: ["host1"] 
> > [host1] executing command 
> > Password: 
> > 
> > 
> > Files: 
> > 
> > Capfile 
> > 
> > default_run_options[:pty] = true 
> > role :app, "host1" 
> > task :deploy, roles => :app do 
> > run "whoami" 
> > run "/data/myapplication/script.sh stop", :shell => "sudo su - cmsadmin" 
> > run "tail -f /home/apache-tomcat-7.0.67/logs/catalina.out | sed '/^INFO: 
> > Stopping ProtocolHandler/ q'" 
> > run "sudo puppet agent --confdir=/home/puppet --waitforcert 60 --test; 
> true" 
> > end 
> > 
> > In 2.6 is there a way i can execute commands on behalf of another user 
> > ("admin" in my case)? If so how? I understand that this is possible with 
> the 
> > help of https://github.com/fundingcircle/sshkit-backends-netssh_global 
> in 
> > Cap 3.0. But i would like to know if it is achievable using 2.6 or 
> should i 
> > have to upgrade it? 
> > 
> > Any pointers will help me a lot. Thanks! 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Capistrano" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to capistrano+...@googlegroups.com . 
> > To view this discussion on the web, visit 
> > 
> https://groups.google.com/d/msgid/capistrano/71a57de7-0950-4f2d-9786-e89825e88972%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to capistrano+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/capistrano/6d0877e3-41a4-44fb-9919-4de04e7a8037%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [capistrano-mailing-list] Could not fetch specs from https://rubygems.org/

2016-10-18 Thread William Johnston

Hey Eugeniu,

When I encounter issues like this, I'll first try and eliminate
Capistrano as the cause. Log into the server as your deploy user, and
navigate to the releases directory (something like
/home/user/rtms/releases/). Then run bundle install. If it
fails, this is a Bundler issue and has nothing to do with Capistrano.

~William Johnston

On Fri, Oct 7, 2016 at 8:52 AM, Eugeniu Tambur  wrote:
> Versions:
>
> Ruby 2.3.1
> Capistrano  3.6.1
> Rake / Rails / etc
>
> Platform:
>
> Working on Windows 8.1 x64
> Deploying to.Ubuntu 16.04
>
> Logs:
>
>
> 00:14 bundler:install
>   01 ~/.rvm/bin/rvm default do bundle install --path
> /home/user/rtms/shared/bundle --binstubs /home/user/rtms/shared/bin
> --without development test cucumber deploy --deployment …
>
>   01 Could not fetch specs from https://rubygems.org/
> cap aborted!
> SSHKit::Runner::ExecuteError: Exception while executing as u...@xx.xx.xx.xx:
> Exception while executing as u...@xx.xx.xx.xx: bundle exit status: 17
> bundle stdout: Could not fetch specs from https://rubygems.org/
> bundle stderr: Nothing written
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/runners/parallel.rb:15:in
> `rescue in block (2 levels) in execute'
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/runners/parallel.rb:11:in
> `block (2 levels) in execute'
> SSHKit::Runner::ExecuteError: Exception while executing as u...@xx.xx.xx.xx:
> bundle exit status: 17
> bundle stdout: Could not fetch specs from https://rubygems.org/
> bundle stderr: Nothing written
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/runners/parallel.rb:15:in
> `rescue in block (2 levels) in execute'
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/runners/parallel.rb:11:in
> `block (2 levels) in execute'
> SSHKit::Command::Failed: bundle exit status: 17
> bundle stdout: Could not fetch specs from https://rubygems.org/
> bundle stderr: Nothing written
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/command.rb:100:in
> `exit_status='
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/netssh.rb:148:in
> `execute_command'
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:141:in
> `block in create_command_and_execute'
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:141:in
> `tap'
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:141:in
> `create_command_and_execute'
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:74:in
> `execute'
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/capistrano-bundler-1.2.0/lib/capistrano/tasks/bundler.cap:36:in
> `block (5 levels) in '
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:93:in
> `with'
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/capistrano-bundler-1.2.0/lib/capistrano/tasks/bundler.cap:27:in
> `block (4 levels) in '
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:85:in
> `within'
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/capistrano-bundler-1.2.0/lib/capistrano/tasks/bundler.cap:26:in
> `block (3 levels) in '
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:29:in
> `instance_exec'
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:29:in
> `run'
> C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/runners/parallel.rb:12:in
> `block (2 levels) in execute'
> Tasks: TOP => deploy:initial
> The deploy has failed with an error: Exception while executing as
> u...@xx.xx.xx.xx: Exception while executing as u...@xx.xx.xx.xx: bundle exit
> status: 17
> bundle stdout: Could not fetch specs from https://rubygems.org/
> bundle stderr: Nothing written
> ** Invoke deploy:failed (first_time)
> ** Execute deploy:failed
>
>
> ** DEPLOY FAILED
> ** Refer to log/capistrano.log for details. Here are the last 20 lines:
>
>
>  * net-scp (1.2.1)
>
>  DEBUG [cc59676e]* sshkit (1.11.3)
>
>  * airbrussh (1.1.1)
>
>  DEBUG [cc59676e]* capistrano-harrow (0.5.3)
>
>  DEBUG [cc59676e]* capistrano (3.6.1)
>
>  * capistrano-bundler (1.2.0)
>
>  * capistrano-rails (1.1.8)
>
>  DEBUG [cc59676e]* capistrano-rvm (0.1.2)
>
>  DEBUG [cc59676e]* capistrano-upload-config (0.7.0)
>
>  DEBUG [cc59676e]* capistrano3-nginx (2.1.5)
>
>  DEBUG [cc59676e]* capistrano3-puma (1.2.1)
>
>  * xpath (2.0.0)
>
>  DEBUG [cc59676e]* capybara (2.10.0)
>
>  DEBUG [cc59676e]* database_cleaner (1.5.3)
>
>  DEBUG [cc59676e]* shoulda-matchers (3.1.1)
>
> Install missing gems with `bundle install`
>
>  DEBUG [cc59676e] Finished in 1.306 seconds with exit status 1 (failed).
>
>   INFO [e2042204] Running ~/.rvm/bin/rvm default do bundle install --path
> /home/user/rtms/shared/bundle --binstubs

Re: [capistrano-mailing-list] Cap 2.6 - Run as another user

2016-10-18 Thread William Johnston

I'd suggest upgrading. You might be able to find people to help you
with this older version, but most people (IMO) have upgraded and will
be able to support Capistrano 3.

~William Johnston


On Mon, Oct 17, 2016 at 2:21 PM, Gokulakrishnan Sarangaraju
 wrote:
> Versions:
>
> Ruby - 1.8.7
> Capistrano - 2.6.0
> Rake / Rails / etc
>
> Platform:
>
> Working onCentOS
> Deploying to... CentOS
>
> Logs:
>
> Even though "deployuser" has the rights to switch to "admin" user without
> entering password, cap script is expecting password to be entered.
>
> -bash-4.1$ cap -f /tmp/captest-user.cap deploy
>   * executing `deploy'
>   * executing "whoami"
> servers: ["host1"]
> [host1] executing command
>  ** [out :: host1] deployuser
> command finished in 69ms
>   * executing "sudo -p 'sudo password: ' -u admin
> /data/myapplication/script.sh stop"
> servers: ["host1"]
> [host1] executing command
> Password:
>
>
> Files:
>
> Capfile
>
> default_run_options[:pty] = true
> role :app, "host1"
> task :deploy, roles => :app do
> run "whoami"
> run "/data/myapplication/script.sh stop", :shell => "sudo su - cmsadmin"
> run "tail -f /home/apache-tomcat-7.0.67/logs/catalina.out | sed '/^INFO:
> Stopping ProtocolHandler/ q'"
> run "sudo puppet agent --confdir=/home/puppet --waitforcert 60 --test; true"
> end
>
> In 2.6 is there a way i can execute commands on behalf of another user
> ("admin" in my case)? If so how? I understand that this is possible with the
> help of https://github.com/fundingcircle/sshkit-backends-netssh_global in
> Cap 3.0. But i would like to know if it is achievable using 2.6 or should i
> have to upgrade it?
>
> Any pointers will help me a lot. Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Capistrano" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to capistrano+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/capistrano/71a57de7-0950-4f2d-9786-e89825e88972%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to capistrano+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/capistrano/CAJBYiQhnWAPCEJJcKiJLnjmS8KxN-yPCEQJfZV4gUYefvHUyCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [capistrano-mailing-list] Getting the dreaded "Stage not set, ..." error, can't get around it.

2016-10-18 Thread Faddah Steve Yuetsu Wolf

hi Lee, 

thank you for the response.

so is Capistrano + wp-cli not being really supported any more as a solution 
for migrating/transferring WordPress sites & their MySQL database?

i'll look at roots.io, but i'm hoping it's as simple an (alleged) set-up 
for migrating/transferring as Capistrano + wp-cli was supposed to be. i say 
"alleged" because of all the issues i've been having in just trying to make 
this work. and can anyone still please tell me why i am getting this 
Stage not set, please call something such as `cap production deploy`, where 
production is a stage you have defined.
...error?

best,

—  faddah

On Tuesday, October 4, 2016 at 11:06:59 PM UTC-7, Lee Hambley wrote:
>
> Hi Faddah,
>
> You might be better served by roots.io whixh is an ansible2 based 
> WordPress+wp-cli deployment tool which formerly used Capistrano and sounds 
> a lot like what you're doing.
>
> (Sent from my Nexus 6, please forgive typos!)
>

-- 
You received this message because you are subscribed to the Google Groups 
"Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to capistrano+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/capistrano/bf96-2b3e-46d1-b640-342bfd6e6197%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[capistrano-mailing-list] Could not fetch specs from https://rubygems.org/

2016-10-18 Thread Eugeniu Tambur

*Versions:*

   - Ruby 2.3.1
   - Capistrano  3.6.1
   - Rake / Rails / etc

*Platform:*

   - Working on Windows 8.1 x64
   - Deploying to.Ubuntu 16.04

*Logs:*


00:14 bundler:install
  01 ~/.rvm/bin/rvm default do bundle install --path 
/home/user/rtms/shared/bundle --binstubs /home/user/rtms/shared/bin 
--without development test cucumber deploy --deployment …

  01 Could not fetch specs from https://rubygems.org/
cap aborted!
SSHKit::Runner::ExecuteError: Exception while executing as 
u...@xx.xx.xx.xx: Exception while executing as u...@xx.xx.xx.xx: bundle 
exit status: 17
bundle stdout: Could not fetch specs from https://rubygems.org/
bundle stderr: Nothing written
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/runners/parallel.rb:15:in
 
`rescue in block (2 levels) in execute'
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/runners/parallel.rb:11:in
 
`block (2 levels) in execute'
SSHKit::Runner::ExecuteError: Exception while executing as 
u...@xx.xx.xx.xx: bundle exit status: 17
bundle stdout: Could not fetch specs from https://rubygems.org/
bundle stderr: Nothing written
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/runners/parallel.rb:15:in
 
`rescue in block (2 levels) in execute'
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/runners/parallel.rb:11:in
 
`block (2 levels) in execute'
SSHKit::Command::Failed: bundle exit status: 17
bundle stdout: Could not fetch specs from https://rubygems.org/
bundle stderr: Nothing written
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/command.rb:100:in
 
`exit_status='
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/netssh.rb:148:in
 
`execute_command'
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:141:in
 
`block in create_command_and_execute'
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:141:in
 
`tap'
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:141:in
 
`create_command_and_execute'
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:74:in
 
`execute'
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/capistrano-bundler-1.2.0/lib/capistrano/tasks/bundler.cap:36:in
 
`block (5 levels) in '
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:93:in
 
`with'
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/capistrano-bundler-1.2.0/lib/capistrano/tasks/bundler.cap:27:in
 
`block (4 levels) in '
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:85:in
 
`within'
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/capistrano-bundler-1.2.0/lib/capistrano/tasks/bundler.cap:26:in
 
`block (3 levels) in '
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:29:in
 
`instance_exec'
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/backends/abstract.rb:29:in
 
`run'
C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/sshkit-1.11.3/lib/sshkit/runners/parallel.rb:12:in
 
`block (2 levels) in execute'
Tasks: TOP => deploy:initial
The deploy has failed with an error: Exception while executing as 
u...@xx.xx.xx.xx: Exception while executing as u...@xx.xx.xx.xx: bundle 
exit status: 17
bundle stdout: Could not fetch specs from https://rubygems.org/
bundle stderr: Nothing written
** Invoke deploy:failed (first_time)
** Execute deploy:failed


** DEPLOY FAILED
** Refer to log/capistrano.log for details. Here are the last 20 lines:


 * net-scp (1.2.1)

 DEBUG [cc59676e]* sshkit (1.11.3)

 * airbrussh (1.1.1)

 DEBUG [cc59676e]* capistrano-harrow (0.5.3)

 DEBUG [cc59676e]* capistrano (3.6.1)

 * capistrano-bundler (1.2.0)

 * capistrano-rails (1.1.8)

 DEBUG [cc59676e]* capistrano-rvm (0.1.2)

 DEBUG [cc59676e]* capistrano-upload-config (0.7.0)

 DEBUG [cc59676e]* capistrano3-nginx (2.1.5)

 DEBUG [cc59676e]* capistrano3-puma (1.2.1)

 * xpath (2.0.0)

 DEBUG [cc59676e]* capybara (2.10.0)

 DEBUG [cc59676e]* database_cleaner (1.5.3)

 DEBUG [cc59676e]* shoulda-matchers (3.1.1)

Install missing gems with `bundle install`

 DEBUG [cc59676e] Finished in 1.306 seconds with exit status 1 (failed).

  INFO [e2042204] Running ~/.rvm/bin/rvm default do bundle install --path 
/home/user/rtms/shared/bundle --binstubs /home/user/rtms/shared/bin 
--without development test cucumber deploy --deployment --quiet as 
u...@xx.xx.xx.xx

 DEBUG [e2042204] Command: cd /home/user/rtms/releases/20161007133640 && ( 
export RVM_BIN_PATH="~/.rvm/bin" ; ~/.rvm/bin/rvm default do bundle install 
--path /home/user/rtms/shared/bundle --binstubs /home/user/rtms/shared/bin 
--without development test cucumber deploy --deployment --quiet )

 DEBUG [e2042204]  * Could not fetch specs from https://rubygems.org/*

*Cap file:*

# Load DSL and set up stages
require "capistrano/setup"

# Include default

Re: [capistrano-mailing-list] Cap 2.6 - Run as another user

Re: [capistrano-mailing-list] Cap 2.6 - Run as another user

Re: [capistrano-mailing-list] Could not fetch specs from https://rubygems.org/

Re: [capistrano-mailing-list] Cap 2.6 - Run as another user

Re: [capistrano-mailing-list] Getting the dreaded "Stage not set, ..." error, can't get around it.

[capistrano-mailing-list] Could not fetch specs from https://rubygems.org/

6 matches

Site Navigation

Mail list logo

Footer information