[JIRA] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris edited a comment on JENKINS-27520 Re: Notifications not sent starting 0.1.9 with HipChat API v2 v2integrationworksfineforme(cloudversionofHipChat).Theerrormessagesforv1andSendAsvalueshavebeenimprovedwith[# 47 46 |https://github.com/jenkinsci/hipchat-plugin/issues/ 47 46 ]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris resolved as Cannot Reproduce v2 integration works fine for me (cloud version of HipChat). The error messages for v1 and Send As values have been improved with #47. Jenkins / JENKINS-27520 Notifications not sent starting 0.1.9 with HipChat API v2 Change By: aldaris Status: Open Resolved Resolution: CannotReproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris commented on JENKINS-27520 Re: Notifications not sent starting 0.1.9 with HipChat API v2 Haven't really heard of the group API to be frank, but the simplest test would be to check if your OAuth2 access token has the send_notification scope: https://www.hipchat.com/docs/apiv2/method/get_session To generate OAuth2 tokens for my notifications I just normally go to the room I've created and create a new token under the Tokens menu. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title Adam Moore commented on JENKINS-27520 Re: Notifications not sent starting 0.1.9 with HipChat API v2 Ok I think I found out what the problem is. It seems that for groups api v2 integration isn't available. I can only get the older tokens. If I go to my personal account it seems like it's generating a v2 token. I can't find anything in the documentation that is saying this, but have you been able to generate a token for groups? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris commented on JENKINS-27520 Re: Notifications not sent starting 0.1.9 with HipChat API v2 That is a good point. The v1 API requires a valid value for the Send As configuration field (should be less than 15 chars long), the v2 API does not use the Send As value, it will publish messages using the name of the OAuth2 access tokens. To test your OAuth2 access token, you could follow https://www.hipchat.com/docs/apiv2/auth#auth_test . You should make sure that the acquired OAuth2 access token has the send_notification scope. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title
Adam Moore commented on JENKINS-27520
Re: Notifications not sent starting 0.1.9 with HipChat API v2
I was able to get the v1 api to work by setting the Send As value. I was not able to get the v2 version to work. I generated the token in hipchat, copied that over to jenkins, but I still get this error
HipChat post may have failed. ResponseCode: 401, Response: { error: { code: 401, message: Invalid OAuth session, type: Unauthorized }
}
Not sure what else is needed
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris commented on JENKINS-27520 Re: Notifications not sent starting 0.1.9 with HipChat API v2 I'm not really sure what is going wrong in your setup, I'm pretty sure it works well for me. I'm wondering if you are using a self-hosted HipChat server or are you using the cloud version instead? In any case, when performing an upgrade, the configuration should not need any change, it should remain to work just fine (using the v1 API). Most of the documentation is embedded into the plugin as help texts, so that should help you get going, but here are the main details just in case: v2 mode is a global option, either you enable v2 support in your Jenkins and use v2 OAuth2 tokens everywhere, or you use v1 style API tokens. Each job has a new field for the Auth Token now to allow you to define tokens per build jobs, however if no value is specified for the job, it should fall back to the globally configured Auth Token. v1 API tokens can be obtained by following the v1 docs, v2 OAuth2 tokens can be obtained by following the v2 docs. To help investigate the root cause of this problem please provide some logs from Jenkins for failed notification attempts. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris assigned an issue to aldaris Jenkins / JENKINS-27520 Notifications not sent starting 0.1.9 with HipChat API v2 Change By: aldaris Assignee: aldaris Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Adam Moore commented on JENKINS-27520 Notifications not sent starting 0.1.9 with HipChat API v2 I'll second this. I'm running on cloudbees and neither v1 nor v2 versions of the api work. Running test notifications sends nothing and running a build sends nothing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Behrooz Nobakht created JENKINS-27520 Notifications not sent starting 0.1.9 with HipChat API v2 Issue Type: Bug Assignee: Unassigned Components: hipchat-plugin Created: 20/Mar/15 8:16 AM Description: After downgrading to 0.1.8, it worked again. It could be that we need to change configuration to proper values. Please either provide the necessary documentation on how to upgrade to 0.1.9 which starts to use HipChat API v2 or provide a fix. Environment: Jenkins 1.605 Ubuntu 14.04 Java 1.8u40 Project: Jenkins Priority: Critical Reporter: Behrooz Nobakht This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
