You could write a unit test result file with a single test that represents the success or failure of your build.
That dummy file would satisfy the requirement for a unit test result without requiring special case logic in the job definition. Mark Waite On May 18, 2014 10:10 PM, "Irfan Sayed" <[email protected]> wrote: > hi, > > if we add "publish junit results" as post build action in job and if there > are no junit test results to be displayed for any specific instance of > build then , build gets marked as failed > > this is sometime problematic , if we skip to execute the unit test cases > for any particular instance of build then unnecessary build gets marked > failed > > is there any way to change the behavior.?? i don't want to mark build as > failed if no junit results are to be displayed. > > As junit code base is now part of core jenkins , i cant download the > plugin and modify the codebase > > please suggest > > regards, > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
