Status: New Owner: ---- Labels: Type-Defect Priority-Medium
New issue 1047 by usman.bh...@gmail.com: Moose-on-Moose job in jenkins failing http://code.google.com/p/moose-technology/issues/detail?id=1047
The job Moose-on-moose is failing in Jenkins probably because output file does not have the correct format. We launched the rules report on a moose image with:
OnMooseReport importAndExportAsHudsonTests
And it succeeded. Currently, the job is disabled.
Comment #1 on issue 1047 by v.blonde...@gmail.com: Moose-on-Moose job in jenkins failing http://code.google.com/p/moose-technology/issues/detail?id=1047
Solved by changing the xml file name expected as result of the OnMooseReport importAndExportAsHudsonTests command.
Now we have the test export ! https://ci.inria.fr/moose/job/moose-on-moose/
Updates: Status: Fixed Labels: Milestone-5.0 Maintainability
Comment #2 on issue 1047 by tu...@tudorgirba.com: Moose-on-Moose job in jenkins failing http://code.google.com/p/moose-technology/issues/detail?id=1047
Excellent!
What exactly was the problem?
Comment #3 on issue 1047 by v.blonde...@gmail.com: Moose-on-Moose job in jenkins failing http://code.google.com/p/moose-technology/issues/detail?id=1047
In the build configuration, you set in Jenkins the name of the xml report file to load.
The old name was: **/*-Test.xml But no file with the name *-Test.xml is created in the workspace.
The only file created is: **/Moose On Moose Report.xml
So I change the name of the file to look for.
Comment #4 on issue 1047 by usman.bh...@gmail.com: Moose-on-Moose job in jenkins failing http://code.google.com/p/moose-technology/issues/detail?id=1047
Tx Vincent.
-
moose-technology＠googlecode.com