Install packer for CI

[fuzzmz]

Issue

Fixes #63

List of Changes Proposed

Add a bash script which downloads the latest available version of Packer and unzips it.

Testing Evidence

Not yet tested. Need to check if the CI environment has the tools required by the shell script.

[fuzzmz]

Strange, looks like GitHub doesn't want to see the change I did to make the get-packer.sh script executable. Going to give it a bit more time, and if it still doesn't catch it we have two options:

1. close this PR and open a new one;
2. update the build configs to make the file executable there.

I'd honestly go with the first option, as it's cleaner than adding additional stuff in the build configs, but what do you say?

[coveralls]

Coverage remained the same at 81.944% when pulling 274799a on fuzzmz:install-packer-for-ci into 48bff8e on mayn:master.

[coveralls]

Coverage remained the same at 81.944% when pulling 92519a5 on fuzzmz:install-packer-for-ci into 48bff8e on mayn:master.

[fuzzmz]

OK, now we get packer on Travis CI in the build workspace.

Going to add a powershell script to download it for Appveyor tomorrow since at home I don't have access to a Windows machine.

[mayn]

@fuzzmz this is awesome!
minor comment can we move these scripts to a tools folder when ready.

Thanks again.

[fuzzmz]

Sure thing.

[coveralls]

Coverage remained the same at 81.944% when pulling 1ec4716 on fuzzmz:install-packer-for-ci into cfb5c3f on mayn:master.

[coveralls]

Coverage remained the same at 81.944% when pulling daa72cf on fuzzmz:install-packer-for-ci into cfb5c3f on mayn:master.

[coveralls]

Coverage remained the same at 81.944% when pulling 7f5cee0 on fuzzmz:install-packer-for-ci into cfb5c3f on mayn:master.

[coveralls]

Coverage remained the same at 81.944% when pulling 2ad7aa7 on fuzzmz:install-packer-for-ci into cfb5c3f on mayn:master.

[coveralls]

Coverage remained the same at 81.944% when pulling 394eb1c on fuzzmz:install-packer-for-ci into cfb5c3f on mayn:master.

[fuzzmz]

@mayn, any chance you can cancel the AppVeyor builds for this branch except for the "add debug messages" one? Looks like the powershell script fails somewhere and doesn't give any output, and it takes 1 hour for a job to timeout (and with 6 jobs per build, with another build queued which might not pass, it'll take ages to test this).

[mayn]

@fuzzmz done. I wonder if there is an appveyor setting you can inject into your branch to timeout faster?

[mayn]

@fuzzmz http://help.appveyor.com/discussions/problems/62-how-do-i-increase-the-logging-level-for-the-deployment-log#comment_31002697

[fuzzmz]

Awesome, thanks!

[coveralls]

Coverage remained the same at 81.944% when pulling d1d8341 on fuzzmz:install-packer-for-ci into cfb5c3f on mayn:master.

[fuzzmz]

@mayn, can you also cancel these running builds? Have a final version tested it on my own instance of Appveyor which should be good to go.

Sorry for all the fuss, don't know why I didn't think of enabling integration with Appveyor with my own fork until now.

[fuzzmz]

OK, have to run from work so I'll push the final commits now. With this change everything seems to be working.

Until your build which doesn't work times out you can see the working build result in my instance of Appveyor here.

[coveralls]

Coverage remained the same at 81.944% when pulling 1c1bad3 on fuzzmz:install-packer-for-ci into cfb5c3f on mayn:master.

[coveralls]

Coverage remained the same at 81.944% when pulling 1c1bad3 on fuzzmz:install-packer-for-ci into cfb5c3f on mayn:master.

[fuzzmz]

This is pretty much done from my point of view. Any feedback?

[mayn]

@fuzzmz thanks. Will review/merge later today

[mayn]

LGTM