[BUILD] filePublish findbugs.html
I was previously use the logFilePublisher to publish our findbugs.html results file for our project. However, this made it appear in the list of logs tab and on double clicking would open as a plain text file rather than launching the browser to display the HTML.
Therefore I switched to try the filePublisher ant task.
http://publib.boulder.ibm.com/infocenter/rtc/v1r0m0/topic/com.ibm.team.build.doc/topics/r_filepublisher.html
Using an equivalent snippet to this to publish a findbugs.html results file.
filePublisher repositoryAddress="${repositoryAddress}"
userId="${userId}"
password="${password}"
buildResultUUID="${buildResultUUID}"
filePath="findbugs.html"
label="generic file"
verbose="true"
contributionTypeId="generic.test"
the output seems to suggest it has successfully published, but I do not see the file displayed anywhere on the build result page. Am I missing something? How should I correctly publish a findbugs.html results file so that it will open correctly from the build results page?
Therefore I switched to try the filePublisher ant task.
http://publib.boulder.ibm.com/infocenter/rtc/v1r0m0/topic/com.ibm.team.build.doc/topics/r_filepublisher.html
Using an equivalent snippet to this to publish a findbugs.html results file.
filePublisher repositoryAddress="${repositoryAddress}"
userId="${userId}"
password="${password}"
buildResultUUID="${buildResultUUID}"
filePath="findbugs.html"
label="generic file"
verbose="true"
contributionTypeId="generic.test"
the output seems to suggest it has successfully published, but I do not see the file displayed anywhere on the build result page. Am I missing something? How should I correctly publish a findbugs.html results file so that it will open correctly from the build results page?
3 answers
The filePublisher is a generic task intended for extenders that are
contributing their own UI to the build result editor (writing java code to
do this). This probably isn't helpful in your case.
I am not sure off the top of my head if it is possible to conveniently
display a published html file from the build result.
Have you tried using logPublisher (Logs page) or artifactFilePublisher
(Downloads page) and specifying the contentType attribute to set it to
text/html ?
You might also check configuring the eclipse preferences for File
Associations for .html
Finally, if you have this html file somewhere on the web, you can publish a
URL to it using the linkPublisher to make it show up on the External Links
page.
---
Ryan Manwiller
Jazz Team
contributing their own UI to the build result editor (writing java code to
do this). This probably isn't helpful in your case.
I am not sure off the top of my head if it is possible to conveniently
display a published html file from the build result.
Have you tried using logPublisher (Logs page) or artifactFilePublisher
(Downloads page) and specifying the contentType attribute to set it to
text/html ?
You might also check configuring the eclipse preferences for File
Associations for .html
Finally, if you have this html file somewhere on the web, you can publish a
URL to it using the linkPublisher to make it show up on the External Links
page.
---
Ryan Manwiller
Jazz Team
unfortunately i have (since posting) tried both logPublisher and artifactfilepublisher, but despite being text/html and eclipse's file associations for *.htm and *.html being correct, it always displays in the default editor
only current workaround is to do a 'save as' to disk and then manually open in a browser :(
only current workaround is to do a 'save as' to disk and then manually open in a browser :(
Hello,
I was having a similar issue with my CheckStyle report! Setting the content type toapplication/html seems to work.
I was having a similar issue with my CheckStyle report! Setting the content type to
unfortunately i have (since posting) tried both logPublisher and artifactfilepublisher, but despite being text/html and eclipse's file associations for *.htm and *.html being correct, it always displays in the default editor
only current workaround is to do a 'save as' to disk and then manually open in a browser :(