Parses output from the Android lint tool and displays the results for analysis.
Android Lint is a tool which scans your Android projects and reports on potential bugs, performance, security and translation issues, plus more.
This Jenkins plugin parses XML reports produced by running
lint, analyses them and displays the results for each build.
Information shown includes a build summary, trend graphs, display of warnings in context, and dashboard portlets.
This plugin builds on the work of the static analysis core plugin; see the Static Code Analysis Plug-ins page for a fuller list of features.
If the Dashboard View plugin is also installed, you will be able to add Lint-specific portlets to your dashboard views.
Enable "Publish Android Lint results" in the "Post-build Actions" of your Jenkins job.
By default, the plugin will parse any files called "
lint-results.xml", anywhere in your build's workspace.
This behaviour can be overridden by entering a filename or pattern, relative to the root of your build's workspace.
Note that this plugin does not run Lint for you — you must provide Lint results in XML format, either by running
lint during a build, or by copying the file(s) from somewhere else.
For best results, run Lint in your Android application's directory, e.g.:
cd app; lint --xml lint-results.xml .
Note: When running Jenkins on a headless system, or under a user ID which doesn't have access to a graphical environment, you may see some errors while running Lint.
To combat this, you can run Java in headless mode, as follows:
os_opts="-Djava.awt.headless=true" lint --xml lint-results.xml .
This plugin bundles part of the lint API so that it can retrieve and display full explanations for each type of issue.
If a newer version of lint is released which contains new rules, the plugin will be unable to show explanations for such rules.
In this case, please check the Jenkins Plugin Centre for updates, which should hopefully follow shortly after any major lint upgrades.