bhanditz / gradle-teamcity-log-errors-plugin

Scan log files for error messages and report them as build problems

Gradle TeamCity Log Errors Plugin

If your web application includes a suite of acceptance tests, they start an instance of the app and perform external checks using Selenium WebDriver or REST API.

But sometimes backend components of the tested application raise unhandled exceptions, which produce no errors in the UI, and cannot be caught this way. Even if all tests are green, the app still has hidden issues, which should be addressed.

This plugin helps detecting such problems. It provides the reportLogErrors task, which starts after the tests, scans log files for error messages or stacktraces, and reports them to TeamCity as build problems.

If any errors are found, the build is marked as failed. The Build Results page and e-mail notifications show a clear explanation what went wrong:

Features

• Stacktraces: all Java stacktraces are reported, from INFO or WARN messages.
• Error history: if the same error is reported in multiple builds, even with different timestamps, all occurrences are linked together: assigned investigations and muted problems are preserved.

Usage

buildscript {
    repositories {
        mavenCentral()
        maven { url 'http://repository.jetbrains.com/all' }
    }
    dependencies {
        classpath 'org.jetbrains.teamcity.gradle:log-errors:1.+'
    }
}

apply plugin: 'org.jetbrains.teamcity.log-errors'

reportLogErrors {
    pattern ( /\[.+?\] \s*(\S+) - \s*\S+ - (.*)/ )
    file 'service1.log'
    file 'service2.log'
}

• pattern: regex string, must contain two saving groups:
  • message level (INFO/WARN/ERROR),
  • a text.
• file: a log filename.