Fix ansible paths when provisioning Linux from Windows

implemented null buider

optionally use existing ssh key for amazon builders

Updates googlecompute build to v1 API & uses boot persistent disk

builder/vmware-vmx: add cloning support on Windows [GH-824]

Update Ansible provisioner to set cwd to staging directory.

Properly return error when invalid instance state is found

fixing colored output of Makefile

common: fix error handeling when creating a floppy

builder/digitalocean: updated default image_id, fixes #1032

builder/digitalocean: updated default image_id, per #1032

use old ssh code until higebu's branch (#1030) is ready, see #1019

Changing to the v1 google-api-go-client. Now creates a persistent disk as the boot disk, and sets it to auto delete

The colored output is broken when using Zsh.

\033[32;01m==> Installing dependencies\033[0m
\033[32;01m==> Building\033[0m

After adding the parameter -e to echo I get the expected green lines.

The null builder is not really a bulider, it just setups a SSH
connection and runs the provisioners. It can be used to debug
provisioners without incurring high wait times. It does not create any
kind of image or artifact.

Fix a trailing comma in an example template

Since the paths are generated on the host machine but the commands are
executed on the VM being provisioned the paths generated will use path
separators from the host. In the case of provisioning a Linux VM from
Windows this path will not work.

Convert the path to use a '/' separator which should work for both
platforms in Go

Fix syntax error

Fix issue where using double quotes instead of round brackets would cause the following error:
./scripts/devcompile.sh: line 30: 10#1.2 > 10#1.2.1: syntax error: invalid arithmetic operator (error token is ".2 > 10#1.2.1")