|
On 02/09/2015 04:29 PM, Samuel Wu
wrote:
The WTP build currently keeps
going as usual when a compile problem happens and marks the
build as a successful one. We need to go to check the log to
figure out whether the build fails. I wonder how to change the
build to mark it as failed when a compile error happens.
In the Maven step of your CI job
https://hudson.eclipse.org/webtools/job/WTP-R3_7_Integration/configure
In the advanced settings, there is a parameter called "FAIL_MODE",
which is set to Never. You should either use NORMAL or AT_END.
Setting FAIL_MODE to Never is contrary to the goal of continuous
build: you want to know about failures loudly and ASAP. I suggest
you check job configuration history to find out who changed that,
and discuss with the author of this change what are the best and
worst practices of CI builds ;)
Due to the historical reason,
there are a few JUNIT tests fail during the build. I guess
that's the reason the build has been set up this way. I don't
think we can clean up the JUNIT tests right now. It would be
great if the build can differentiate the test errors and the
compile ones and handle them differently.
There are the maven.test.error.ignore=true and
maven.test.failure.ignore=true settings to configure the behaviour
regarding tests. You should only use this one and restore the
FAIL_MODE to a better value.
|
