You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If all tests pass, everything is good and the *.html report will display in CruiseControl.Net (the link to the *.html file works). However, if any of the test fail, the *.html file will not get displayed in CruiseControl.Net.
How do I correct this? I am guessing this happens because when a test fails, CCNet will not concatenate the build number into the *.xml file name. The *.xml file then cannot find the associated *.html file which exists in a folder named with the build number.
The *.html file does successfully get copied to the artifact directory, the CCNet just doesn't know how to find it since the build number wasn't concatenated into the *.xml's file name.
If I manually add the 'Lbuild.x.x.xxxxx' to the end of the *.xml file name, then everything works and and the link to the *.html page works when CruiseControl.Net is display in the web browser.
The text was updated successfully, but these errors were encountered:
If all tests pass, everything is good and the *.html report will display in CruiseControl.Net (the link to the *.html file works). However, if any of the test fail, the *.html file will not get displayed in CruiseControl.Net.
How do I correct this? I am guessing this happens because when a test fails, CCNet will not concatenate the build number into the *.xml file name. The *.xml file then cannot find the associated *.html file which exists in a folder named with the build number.
The *.html file does successfully get copied to the artifact directory, the CCNet just doesn't know how to find it since the build number wasn't concatenated into the *.xml's file name.
If I manually add the 'Lbuild.x.x.xxxxx' to the end of the *.xml file name, then everything works and and the link to the *.html page works when CruiseControl.Net is display in the web browser.
The text was updated successfully, but these errors were encountered: