| Over in Apache Foundation, Apache HBase makes use of Jenkins as a foundation-provided resource. We define a job that is driven by a Jenkinsfile. That jobs is comprised of multiple parallel stages. Many of the stages are nearly identical, and most of them conclude with a stanza that looks like
post {
always {
...
publishHTML target: [
allowMissing : true,
keepAll : true,
alwaysLinkToLastBuild: true,
// Has to be relative to WORKSPACE.
reportDir : "${env.OUTPUT_DIR_RELATIVE}",
reportFiles : 'console-report.html',
reportName : 'JDK11 Nightly Build Report (Hadoop3)'
]
}
}
Occasionally, stages in our BlueOcean builds will be marked as failed on this "Publish HTML reports" action. Output looks like this
[2020-05-02T11:13:44.352Z] [htmlpublisher] Archiving HTML reports...
[2020-05-02T11:13:44.370Z] [htmlpublisher] Archiving at BUILD level /home/jenkins/jenkins-slave/workspace/HBase_Nightly_branch-2.3@2/output-jdk11-hadoop3 to /x1/jenkins/jenkins-home/jobs/HBase Nightly/branches/branch-2-3.v4n2jn/builds/62/htmlreports/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29
script returned exit code 1
I've been working with the fine folks in ASF Infra to track down the issues, on my quest for passing builds. Unfortunately, we're stumped. Any advice or suggestions are most welcome! Thanks in advance. |
