Closed fatmcgav closed 7 years ago
@fatmcgav In Jenkins 2.69 with declarative pipeline like this it works just fine without any exceptions in the logs.
post {
failure {
hipchatSend credentialId: "HipChat-Creds", room: 'Alerts', color: "RED", sendAs: "Jenkins", notify: true, message: '$JOB_NAME #$BUILD_NUMBER Build failed after $DURATION (<a href="$URL">Open</a>)', failOnError: true
}
}
@Constantin07 hmm, ok... We're still using the scripted pipeline currently.
Any ideas if that should still work?
Not quite sure what's going on, I was unable to reproduce this issue with a very simple pipeline script:
node {
git 'https://github.com/aldaris/docbook-linktester.git'
def mvnHome = tool 'Maven3'
sh "'${mvnHome}/bin/mvn' -Dmaven.test.failure.ignore clean install"
hipchatSend color: 'GREEN', credentialId: 'HipChat-Jenkins-Token', message: 'Pipeline build finished', notify: true, room: 'Jenkins', sendAs: '', server: '', v2enabled: true
}
Can you provide exact reproduction steps?
On the other hand the error message points to fields that are not defined by the HipChat plugin itself, so I'm not quite convinced yet that this is a Hipchat plugin issue.
I'm trying to integration Hipchat into our existing Pipeline tests.
However when I add the
hipchatSend
action to the Pipeline, the job fails with the following:Jenkins v2.46, latest Pipeline plugins and Hipchat plugin.
Any ideas? Cheers