Hi, IMO "script shell" step should contain a few lines, and if you need further logic you might need to store those scripts in your SCM tool, then you can call that script. There are different approaches: 1) You could merge those "Script shell" in one shell and use your SCM to store those scripts: then you could trap those errors and add some error messages 2) You could use the groovy post build actions in order to manipulate those failures and add further details about those errors in the main job dashboard: https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Postbuild+Plugin 3) You could use the console parser plugin: https://wiki.jenkins-ci.org/display/JENKINS/Log+Parser+Plugin 4) You could use the build failure plugin in order to categorize those errors and add indicators in your job: https://wiki.jenkins-ci.org/display/JENKINS/Build+Failure+Analyzer
Those plugins already describe some examples of parsing the console output. Cheers On Tuesday, 8 September 2015 10:56:36 UTC+2, Adrien Ruffie wrote: > > Hello all, > > I want to customize the failure message at the job ending (you can see it > in attached file). > My problem is also, I have several "Script shell" steps in the same build, > but when one of them fail, the failure job report don't specify which one > failed ... > Do you know one mean to give one number in each "script shell" step in > order to specify it in the failure message ? > > Thank you very much and best regards. > > Adrien > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6815e9d7-044f-4291-bc70-ceb5334d995c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
