We're migrating from "classic" Jenkins to kubernetes with pipelines - for now we're using scripted pipeline, but I'm not sure whether declarative ones would solve this issue for us.

On "old" Jenkins, when the test configuration failed the build was marked as unstable at least. I'm struggling to do it with pipelines - because by default the failed test configuration leaves the build result unchanged, which shows the successful build in the end.

There is this failureOnFailedTestConfig, but that one flips the build all the way to FAILURE, which is not what we want (we leave that to compilation issues).

I would be able to work around it and switch any non-success to UNSTABLE, but that is not possible. When the build is FAILURE already, there is no way I'm aware of to lower the result to UNSTABLE. But when it's success, I have no idea, whether some test configurations are failed or not.

I also checked whether the step produces any return value, perhaps I can work with that... but no, there is no stats I can use in the pipeline afterwards.

The failure* flags do not actually cause the step to fail, so I can handle it with catchError as I like - it merely marks the result so I'm out of options.

So we would need something as the said flag, but to put the status to unstable.

Or is there any other way how to get to the same effect? I've been searching the Internet for some months, but I couldn't find anything about this problem.