Describe the bug
Travis CI gives us the ability to automatically deploy to Heroku when the different criteria defined by us are satisfied.
Right now we had configured it to deploy automatically to a Heroku dyno called "precaution" when there is a tagged commit and to another Heroku dyno called "dev-precaution" on every commit.
Describe the bug Travis CI gives us the ability to automatically deploy to Heroku when the different criteria defined by us are satisfied. Right now we had configured it to deploy automatically to a Heroku dyno called "precaution" when there is a tagged commit and to another Heroku dyno called "dev-precaution" on every commit.
I pretty sure that right now automatic deploy to Heroku from the vmware/precaution repo doesn't work because we need to authorize vmware/precaution project in front of Heroku. You can read about this in this full description step 4: https://medium.com/@felipeluizsoares/automatically-deploy-with-travis-ci-and-heroku-ddba1361647f
Many of our builds are failing because of that. For example https://github.com/vmware/precaution/commit/08eab0782f2666b81de37de4fe246041dc418ca6