First of all, thanks for detailed report, with steps to reproduce, images and very clear description.

>When clicking on the "demo" file name (not "view"!) in your browser it's considered as BIN file and download gets
>enforced. When clicking on demo.pl and demo.txt instead they are provided as plain-text files without forcing
>download to view them.

I think this is the correct behaviour in this case.

>It would be nice if such "binary files" could be also considered for TAP reports or if not at least warn in the
>TAP execution run and mention in the documentation that files should be preferably have suffix .tap.

In order to warn during the plug-in execution that a file being parsed is binary (or to skip it) the plug-in would have to use the same mime-types as Jenkins (the plug-in today uses none, it simply ignores the mime-types).

This can cause more bugs, and would be much more complicated to maintain.

However, I do agree that we could add/mention something in the documentation. Would you be willing to write something about it in the plug-in Wiki? If you already have the login in wiki.jenkins-ci.org, go to https://wiki.jenkins-ci.org/display/JENKINS/TAP+Plugin and feel free to add information that would help other users

Thanks a lot!
-B

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to