Add travis CI support to Pezmc/RemoteTech2
Use a passworded zip for the dll's

Not entirely sure where to document the password
Travis should now set the environment variable ZIPPASSWORD which can
then be used to unzip the .dll's

I believe this doesn't work with pull requests, as in theory a pull
request could just dump env to access the password.
Resolve conflict from 4300396cd22ae4f3fd9b50f8a2fede915ee652e1
Resolve conflict from 8a201771d87dda6e5092fd7b7142a77fabc0ab15
Add automatic deploys to GitHub releases via Travis
+ Correct mistake in travis.yml
+ Remove Travis deploy

Our custom tagging was causing this to trigger.
We can just rely on the custom solution for now!

+ Catch branches with /'s in their name as that's not a valid filename
Merge pull request #3 from Pezmc/travis-deploy

Add automatic github deploys
Mark as non-draft
Merge pull request #79 from Pezmc/chore/travis-cleaned

Add Travis CI support to RT2
Add secrets for CI against canonical repo
Update Travis build label URL
Don't prefix built tag with current tag
Remove 'v' prefix from generated tags
Remove another prefixed 'v'
Add the related SHA
Prevent pull requests deploying
Prevent loops

If we're already on a build tag, we don't need to do anything.
If the env vars are not set, don't fail to build
Merge pull request #81 from Pezmc/chores/travis-loop-fix

Enhancements to travis release system, hopefully travis should test this merge.
Include build information

Include information about the build in the release notes and in the
zip. This way we can confirm what build people have downloaded.
Merge pull request #82 from Pezmc/chores/travis-enhance

Include build information in build zip
Merge pull request #88 from RemoteTechnologiesGroup/chore/travis

Move travis ci intergration into the develop branch