You are viewing an old version (v. 1) of this page.
view page history | view next version >>
Investigate build failure
If a build is generated but failed, you will see an error summary in the build overview page like below:
This gives a quick view of which steps are in error, and cause of the error. You may open the step log or build log to view details of the errors. The error summary will also be displayed if you point mouse to the build failure icon in dashboard and in build history.
 | Enable debug logging for build log In case of a build failure, Enabling debug logging may help investigating the problem. This can be done by editing basic setting of corresponding configuration and set the log level to DEBUG or TRACE. |
Investigate configuration error
Configuration will be marked in error in below cases:
- Failed to evaluate snapshot taking script.
- Failed to evaluate build condition.
- Failed to determine build version.
- Failed to collect build metrics.
- Failed to send build notifications
Configuration error messages are logged in system log instead of build log either because the build has not been generated or because the build is finished and build log is closed. If a configuration is in error, its status icon will flickers. An error summary window will be displayed if you point mouse to the error icon like below:
| Enable debug logging for system log In case of configuration error, enabling debug logging may help the investigation. Debug logging for system log can be enabled by editing file conf/log4j.properties under QuickBuild server's installation directory, and change the second line to be: log4j.logger.com.pmease.quickbuild=DEBUG or log4j.logger.com.pmease.quickbuild=TRACE The modified log4j setting will take effect immediately after you've saved the file, and you do NOT need to restart the server. |