JUnit Attachments Plugin is not working on Hudson - junit

I'm running integration tests using TestNG and Hudson combination. I'm able to generate my own customized JUnit XML files for Hudson for reporting purpose. And Hudson displays my customized report greatly. Now I want to attach test results which are of .txt files to my test class/test method. I have taken JUnit Attachments Plugin and installed it on Hudson. I generated the .txt files into the surefire-reports//*-output.txt directory as per the example mentioned in the following link: http://wiki.hudson-ci.org/display/HUDSON/JUnit+Attachments+Plugin.
But JUnit Attachments Plugin is not working on Hudson. I'm unable to see the attachments in Hudson.
Any suggestions to make it work?

Related

Visual Studio Team Services Building JSON Scripts

I'm currently building scripts using Selenium Builder (which saves files as JSON) and i'm having a hard time running these scripts on VSTS. My question specifically is, can Visual Studio Team Services build JSON scripts and tie them in with its C.I.? If so, which approach must I take in order to do this / make it possible?
Thanks!
Here is my steps for your reference:
Deploy your own private build agent by following this link.
Configure the required environment on the build agent like Selenium Driver, Firefox so that the testing can be run on the build agent.
Upload the json file generated by Selenium Builder into VSTS Repository.
Create a build definition with two Command Line tasks: The first one runs npm install command to install se-interpreter:
And the second one run se-interpreter command to run the test in json file:
Queue the build, you will see the test been executed during the build:

How to see Junit report in Jenkins

I have installed Hudson Post Build task in Jenkins. Now what to do to see junit report?
I tried setting up the source path to publish JUnit reports under test report XML tag. But i am not able to see the XML.

Html publisher plugin for Jenkins not triggering Doxygen to create documents

I am able to run Doxygen via the Doxygen GUI frontend and generate the documentation as expected. When I configure this to run in Jenkins, the console output from my build suggests that doxygen is running:
[htmlpublisher] Archiving HTML reports...
[htmlpublisher] Archiving at PROJECT level
C:\Doxygen\html to
C:\Jenkins\jobs\GIT_MASTER\htmlreports\GIT_MASTER_Doxygen_Documentation
Finished: SUCCESS
However when I check the OUTPUT_DIRECTORY it is empty.
My version of Jenkins is 1.542,
the html publisher plugin is 1.3 and
Doxygen is 1.8.6
I'm wondering if I have missed something in Jenkins configuration but I can't find anything else. As always any help is appreciated.
BTW, the Jenkins Doxygen plugin works as expected to generate html reports.
Thanks

Junit reports for Hudson

I am able to successfully run my JUnit test suite from the command line and now I want run these tests from Hudson.
However , for Hudson to generate the reports , it needs a results file (I think in xml format) .
How do I generate a results file from JUnit ?
I am using the following command to run the tests :
java com.nvidia.tests.TestSuite1
Thanks in advance .
Parag.
If you're using ant, you can look at the JUnit task for ant. This is probably the easiest way. You can just add the task at the appropriate place in the script.
If you're using maven, look at the surefire plugin for maven which will automatically run the tests and create the reports in jenkins.
EDIT: If you're not using any build tool (which you should be), then just add the ant build script to jenkins, and you should get the reports automatically.

pre build configuration in Hudson

I want to do a pre build configuration in hudson. basically I want to run a shell script which changes one perticular file after all the fresh source code is download from svn.
and then build...but hudson is not allowing it..
Just create the project as a freestyle project and configure the first step to execute the script. The next one to run your build via Maven or whatever. You should add the script to the project in your version control system.
Also check out the Hudson book for more info
http://www.simpligility.com/2011/06/hudson-book-changes-and-community/