Travis CI Automated Deployment Problems about blt

[grasmash]

@justinlevi For the Bolt repo itself, we're actually committing an encrypted private key to the repository, which only the Travis worker is able to decrypt. We can then add the corresponding public key to our deployment endpoint.

It's a bit of a PIA, but it works. This line does the bulk of the work:
https://github.com/acquia/blt/blob/8.x/.travis.yml#L27

The actual encryption and the openssl portion of that command is done by the travis binary. See instructions for encrypting files with Travis CI.

We should add a note to the docs indicating that the prescribed workflow only applies to private repos.

[CashWilliams]

This isn't really possible with a free version of Travis. You need to be able to securely provide access to the ssh key, and only the paid version allows for this.

[justinlevi]

@CashWilliams Ahh, that would explain the issue then. Unfortunate that the free version of Travis can't do this. I guess I could just write a cron task, on another server, to check the build status and do a merge back.

Any other workflows for using free version of Travis that would make sense?