And the solution is simpler, I just need to save the failing tests before the maven execution and compare with the full list of failing tests I get after that maven execution: https://github.com/xwiki/xwiki-jenkins-pipeline/commit/1bce23c511fa04a1b26ae012f198c9b99049a100
Thanks -Vincent On Wednesday, January 31, 2018 at 7:19:39 AM UTC+1, Vincent Massol wrote: > > Actually my code won't work. Just realized that 'env' can only store > Strings. Thus I need a way to have some global variable shared between > calls to my scripted pipeline library... Any idea? > > On Tuesday, January 30, 2018 at 6:15:20 PM UTC+1, Vincent Massol wrote: >> >> Thanks Victor. Not sure how failureDiffString would help. The issue is >> that this returns the failures from all past maven executions and not just >> for the last run. >> >> FTM I've done this but it's overly complex and it would be nice to be >> able to get the failed tests related only to the last maven execution: >> >> https://github.com/xwiki/xwiki-jenkins-pipeline/commit/cd1ed55e12b22f3957ee1a6e099686461886350b >> >> Note that I have to go through a global env variable to save the previous >> state and compare. >> >> Thanks >> -Vincent >> >> On Tuesday, January 30, 2018 at 6:08:13 PM UTC+1, Victor Martinez wrote: >>> >>> What about this: >>> https://groups.google.com/d/msg/jenkinsci-dev/hI3aSyayYxQ/txGte6HQAAAJ >>> ? Not sure whether the failureDiffString method might help you in this case. >>> >>> Cheers >>> >> -- 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/93ea2888-f670-4b8d-9402-44541c4d9702%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
