[7.4] Use different method of determining build status in pipe… (#46840)

* Switch method of determining build status for pipeline jobs to handle aborted builds better
This commit is contained in:
Brian Seeders 2019-09-30 16:28:03 -04:00 committed by GitHub
parent b4ec33fc2c
commit 9a03c6ca5e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

8
Jenkinsfile vendored
View file

@ -1,5 +1,7 @@
#!/bin/groovy
library 'kibana-pipeline-library'
stage("Kibana Pipeline") { // This stage is just here to help the BlueOcean UI a little bit
timeout(time: 180, unit: 'MINUTES') {
timestamps {
@ -246,10 +248,12 @@ def sendInfraMail() {
def sendKibanaMail() {
catchError {
if(params.NOTIFY_ON_FAILURE && currentBuild.result != 'SUCCESS' && currentBuild.result != 'ABORTED') {
def buildStatus = buildUtils.getBuildStatus()
if(params.NOTIFY_ON_FAILURE && buildStatus != 'SUCCESS' && buildStatus != 'ABORTED') {
emailext(
to: 'build-kibana@elastic.co',
subject: "${env.JOB_NAME} - Build # ${env.BUILD_NUMBER} - ${currentBuild.result}",
subject: "${env.JOB_NAME} - Build # ${env.BUILD_NUMBER} - ${buildStatus}",
body: '${SCRIPT,template="groovy-html.template"}',
mimeType: 'text/html',
)