Dan Grabowski - 31/May/07 10:22 PM Specifying either the ant file pattern for the xml results file or the just the directory containing the results file should both work. The value from this field is passed directly to the visitFilesThatMatch method of com.atlassian.bamboo.utils.FileVisitor. According to the javadoc, this method accepts a "comma separated list if sub-patterns", where each sub-pattern can be a subdirectory name or an ant style pattern. I've tried both options and had success with both. The one catch with specifying a directory is that the plugin assumes that any xml file in the directory is a coverage results file. If there are other xml files in the same directory, they will be picked up by the file visitor and the coverage plugin will attempt to process them. This should not cause any problems, because each coverage report parser does some basic prevalidation of the document structure and will skip a file that does not appear to be a valid report for the coverage tool being used. This is functional, but not ideal and it would be better in these cases to specify a pattern that matches only the coverage report file. The configuration documentation and field description should definitely be updated to make these details clearer. Updating the field label is probably a good idea too. Any thoughts on "Code coverage output directory/file(s)" or "Code coverage output location(s)"? I'm leaning toward the second option assisted by an updated field description that explains the configuration options better.