I'm using pylint to create parseable output of my python source code and the violations plugin to display the results in hudson. This works well for statistics, i.e. the number of errors will show up, but in the violations plugin, when you click on any file, it will display "No violations found". I figured out that this problem exists because pylint writes absolute filenames (starting with /home/myuser/.hudson), but the violation plugins requires the filenames to be relative to the workspace directory. As a workaround I added a sed call to my build step:
sed -i s#.*workspace/## pylint-hudson.txt
When I modify the pylint-results like this, the violations plugin works as expected.