Setting up Travis to auto deploy when all is passing
Level 0 of any work should be getting a deployment workflow set up. What this means in this case is that a push to GitHub will trigger our CI. And then from the CI, if the tests are passing, we trigger the deployment. In this example, I am not going to hit the URL that Forge gives you, but I am going to send an Artifact to S3, and then have CodeDeploy to deploy this Artifact.
As you will see in Chapter 4, Building Views and Adding Style under the Using Travis to run tests on every push section, I have covered setting up this app in Travis CI (https://travis-ci.org/); in this section, I will cover adding CodeDeploy as a part of this step.
Getting ready
You really need to see the section before this, otherwise continuing to know this will make no sense.
How to do it…
The following are the steps:
Install the
traviscommand-line tool in Homestead as noted in their docs at https://github.com/travis-ci/travis.rb#installation. Make sure to use Ruby...
