So yes, using -Dmaven.test.failure.ignore=true changes the exit code from 1
to 0. So if your linking commands you might not spot a previous command
actually silently errored.
As I want jenkins to fail at that step, and not progress to subsequent
steps. Not point wasting computing resources once all
John, is there a reason why you don't use
-Dmaven.test.failure.ignore=true? This has been my Jenkins setup for
years and with that I don't need two mvn runs.
Apart from that I can relate to Alexander's use case in that locally you
simply don't have those Jenkins reporting tools, telling you which
So I understand the option, but for the average developer understanding the
intermixed output might be a nightmare. If someone is building the code
they can just do -SkipTests and -fae, fix those, then go back to run the
tests.
I do a similar setup on Jenkins, with this kind of Jenkinsfile structu
I understand your use case Alex, just not your process. As this is the
users list Im not about to solve the issue of a missing --fail-all-at-end
switch, but I could try to think of workarounds.
Delany
On Sat, 26 Feb 2022 at 09:32, Alexander Kriegisch
wrote:
> Delany,
>
> you are completely misu
