The pattern has been interpreted as a formatting directive. It was of course "*/.*".

Apparently preformatted text is not immune either... that's two stars, slash, star dot star.

Sorry for the delay to look into this gd_sfc

I remember merging a pull request where the contributor changed that pattern, to use [ant like patterns](https://ant.apache.org/manual/dirtasks.html).

Just tested and confirmed it has been fixed. Created a freestyle job, with the following shell producing tap streams.

cat > myfilewithnoextension <<EOF
1..2
ok 1
ok 2 # a comment
EOF

cat > anotherfile <<EOF
1..1
ok 1
EOF

Then added the tap plug-in post build step, with the following pattern to find test results: **/file. Worked as expected.

Attached screen shot of the successfully generated test result page, for the scenario described above.

You can use 2.0, which supports the pipeline-plugin, and has also this fix

Great, thanks very much! An upgrade to 2.0 was on my to-do list, so now I have more motivation!

Great. Hope everything goes smoothly while upgrading your instance. Worth remembering that a test bed server is recommended though I try to avoid breaking (too much) backward compatibility, it's quite easy to forget some XML field serialization handling in Jenkins API, and crash a server. In case you have troubles, just drop me a note, file an new issue, or comment here

2.0.1 released