Chapter 11: Travis CI UI Logging and Debugging

1. Yes whenever you merge a pull request in GitHub, Travis CI will automatically kick off another build.
2. No it doesn't, but you will see labels for the before_install and install lifecycle events as well as some other lifecycle events.
3. You will need to use Docker to pull down an image and you can find the full list of Docker images here (https://docs.travis-ci.com/user/common-build-problems/#Troubleshooting-Locally-in-a-Docker-Image).
4. Yes, but you will need to email [email protected] and then request whatever specific repositories you want to have debug mode enabled for. Additionally you will need to make a call to Travis API with the corresponding job id to trigger a build in debug mode.
5. You will need to make an API call to the Travis API by doing a GET request to the /builds endpoint. Here is a sample request using the curl REST client:

curl -s -X GET \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "Travis-API-Version: 3" \
  -H "Authorization: token $(travis token)" \
  -d '{ "quiet": true }' \
 https://api.travis-ci.org/builds

6. travis_run_before_install is the convenience bash function that you would use.
7. You would use the travis setup SERVICE cli command, and here is an example command to setup Heroku in Travis CI: travis setup heroku.