-
Bug
-
Resolution: Fixed
-
Major
-
None
-
HipChat plugin 2.1.0
I upgraded to the new 2.1.0 release of the HipChat plugin and am now seeing messages like "HIPCHAT_CHANGES_OR_CAUSE is not supported in this context" when attempting commands like the following in a Jenkinsfile (multibranch pipeline):
hipchatSend(message: '${CHANGES_OR_CAUSE}', room: 'Some Room')
Note that this example uses the existing (now deprecated) CHANGES_OR_CAUSE template, not its HIPCHAT_CHANGES_OR_CAUSE replacement. This same sort of error happens for several other new templates as well, such as BUILD_DURATION, COMMIT_MESSAGE, and HIPCHAT_CHANGES.
Additionally, the DURATION template is now rendering as "0 ms" regardless of actual duration.
These messages were working as expected with the 2.0.0 version, aside from the "and counting" issue I logged as JENKINS-40461.
Is there something new that must be done to support these particular templates in a Jenkinsfile/pipeline build, as of 2.1.0, or is this a regression?
- relates to
-
JENKINS-43355 Emails using WARNINGS_RESULT show "is not supported in this context" in Pipeline builds
- Resolved