-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Notifications failing with 'HTTP 400' response #106
Comments
Firstly, invalidate your token and generate a new one, as you have just shared this one publicly. |
I would suggest to upgrade to 2.1.1 version of the plugin which resolved a few issues around pipeline support. |
@aldaris Apologies, it looks like I am running 2.1.1... Anything else I can try? |
I'm not sure, I will try to test this locally to see if I can reproduce this. |
Is this the only hipchatSend command in your pipeline? Tried to reproduce this locally, but it worked just fine for me. |
It's the only one that gets called, based on conditional logic...
|
The Test report URL looks to be empty in your message, that may be it. Not sure why would this happen though. Looks like your pipeline build didn't actually have test results associated with it. This may be something that needs to be changed in the DefaultCardProvider just to be absolutely sure that we aren't trying to display test related attributes if they are not even available. |
Additionally you may want to make sure that email-ext plugin is installed in your deployment, so that you definitely have access to the TEST_COUNTS macros. |
@aldaris Ah, yeh, tests... I'm using the Pipeline to control Terraform... See example here: https://github.com/weareact/terraform/blob/k5-jenkins-test/Jenkinsfile Is that a problem? |
It is probably a contributing factor, yes. Hopefully the above commit alleviates that. Just to be sure: @fatmcgav You did revoke that OAuth2 token you accidentally published in the issue description, right? |
Ok, I'll review the commit and see if i can test locally... And yeh, i've revoked the token above... 😅 |
I believe with the commit above and #108 things should be working in your env. Closing this now. Feel free to reopen if the issue is still present in 2.2.0 |
I'm trying to use Hipchat notifications plugin v2.1.0 with Pipeline, however the notification step is failing.
Jenkins step looks like:
Looking at the Jenkins logs, I can see the following being logged:
When searching issues, I found #39, but that's marked as resolved in a much earlier version of the plugin.
Any pointers?
Cheers
The text was updated successfully, but these errors were encountered: