deploy:update_code fails on windows

[fastsyrup]

Hi,

Deploying rails 4.1 app onto AWS. Get the following error when running cap:deploy or cap:bootstrap

...

• 2014-08-17 21:14:27 executing `deploy:setup'
• executing "sudo -p 'sudo password: ' mkdir -p /mnt/kalenderfee-production /mnt/kalenderfee-production/releases /mnt/kalenderfee-production/shared /mnt/kalenderfee-production/shared/system /mnt/kalenderfee-production/shared/log /mnt/kalenderfee-production/shared/pids"
  servers: ["staging.kalenderfee.com"]
  [staging.kalenderfee.com] executing command
  command finished in 227ms
• executing "sudo -p 'sudo password: ' chmod g+w /mnt/kalenderfee-production /mnt/kalenderfee-production/releases /mnt/kalenderfee-production/shared /mnt/kalenderfee-production/shared/system /mnt/kalenderfee-production/shared/log /mnt/kalenderfee-production/shared/pids"
  servers: ["staging.kalenderfee.com"]
  [staging.kalenderfee.com] executing command
  command finished in 224ms
  ** updating code for bootstrap
• 2014-08-17 21:14:28 executing `deploy:update_code'
• getting (via checkout) revision to C:/Users/solanmi/AppData/Local/Temp/20140817191429
  executing locally: xcopy . "C:/Users/solanmi/AppData/Local/Temp/20140817191429" /S/I/Y/Q/E
  975 File(s) copied
  command finished in 11306ms
• processing exclusions...
• Compressing C:/Users/solanmi/AppData/Local/Temp/20140817191429 to C:/Users/solanmi/AppData/Local/Temp/20140817191429.tar.gz
  executing locally: tar czf 20140817191429.tar.gz 20140817191429
  command finished in 34ms
  shell command failed with return code pid 10672 exit 53

I have tar in my path:

C:\Users\solanmi\Google Drive\kalenderfee\webapp>tar
tar: Must specify one of -c, -r, -t, -u, -x

When I go check the temp folder then there is no folder "20140817191429" although the xcopy seem s to report that it copied 975 files (which would be correct)...

[nirvdrum]

Unfortunately, there's really not much we can do about this. If you've hit the deployment stage, that's all Capistrano at that point. I think I was deploying with zip and had success. git should work fine as well.

[fastsyrup]

Oh okay, sorry wasn't aware... Will followup with them... Thx for your time!

Am 17.08.2014 um 22:49 schrieb Kevin Menard notifications@github.com:

Unfortunately, there's really not much we can do about this. If you've hit the deployment stage, that's all Capistrano at that point. I think I was deploying with zip and had success. git should work fine as well.

—
Reply to this email directly or view it on GitHub.

[nirvdrum]

@fastsyrup It gets a bit worse than that I'm afraid :-( Rubber still targets Capistrano 2. While immensely popular, that version isn't actively maintained any longer. The Capistrano team has devoted its efforts to Capistrano 3. I suspect that issue you've encountered is a problem in Capistrano 3 as well, but we can't easily backport any fix.

Your better bet would probably be to change up the deploy strategy in your deploy.rb depending on the OS.

[Streek]

Use BSDTAR I believe this is proper site http://gnuwin32.sourceforge.net/packages/libarchive.htm it worked just fine for me and even supports the -z option which windows doesn't by default.