Use logs for troubleshooting
After pushing to your environment, you can see the results of the both hooks. Logs from the build hook are redirected to the output stream of
git push, so you can observe them in the terminal or capture them (along with error messages) with
git push > build.log 2>&1.
Logs from the deploy hook are located on the server in the following locations:
- Integration system:
The value of
<user>depends on the project ID and whether the environment is staging or production. For example, with a project ID of
yw1unoukjcawe, the staging environment user is
yw1unoukjcawe_stgand the production environment user is
So on a staging environment for project
yw1unoukjcawe, the deploy log is located at
Logs for all deployments that have happened on this environment are appended to this file, so check the timestamps on log entries to verify that you’re seeing the logs that correspond to the deployment that you are interested in.
The actual log output is highly verbose to allow troubleshooting. Following is a condensed example:
The deploy log contains start and stop messages for each of the two hooks:
Start deploy., and