If you configure a Job with a Node Parameter and the following configuration

• run next build only if build succeeds
• node eligibility set to "All Nodes"
  and you select multiple nodes to build the job, the next build will always be triggered by the result of the main build action although a post build step (e.g. JUnit Test publisher) will mark the build as failed or unstable. I was expecting that the overall result will be considered before running the next build.

I added three test cases to the NodeLabelParameterTest class of the acceptance test harness project to underline this

One causes the main build to fail. In that case everything works as expected, subsequent builds are not started after the first build fails
The other two test cases use publishers to change the build result. In both cases the job will be built on all nodes.