Log a note when catchError sets build result

[jglick]

Otherwise it can be confusing why a build had the result that it did. Observed in a pipeline using the idiom

retry(count: 2, conditions: [kubernetesAgent(), nonresumable()]) {
  node(POD_LABEL) {
    stage('build') {
      withMockLoad(averageDuration: 180) {
        catchError(buildResult: 'UNSTABLE') {
          sh MOCK_LOAD_COMMAND
        }
      }
    }
    stage('publish') {
      junit 'mock-junit.xml'
      archiveArtifacts artifacts: 'mock-artifact-*.txt', allowEmptyArchive: true, fingerprint: true
    }
  }
}

When the first pod is killed, the node block retried and the build ran to completion (FlowEndNode set to SUCCESS) yet the Run is set to UNSTABLE, which is what the step is supposed to do but unintentional here; the reason for the catchError was rather to work around an exit code of 1 from the mock load command due to mock test failures, which is better handled via jenkinsci/mock-load-builder-plugin#102.

stale