Cannot configure it in hosted bamboo
I have installed your plugin in bamboo which is hosted on our server, I cannot see any slack information please see the attached screenshot.
Please help
Comments (29)
-
-
Same with Bamboo version 5.7.2 build 5716.
Nowhere to put Slack team name, and all descriptions show 'Hipchat'.
-
Same here - pretty disappointed as it looked to be as simple as I needed it to be
-
Yes, sorry for the long delay, was out on long due vacation :)
-
- changed status to open
it's a simple fix, rename the ftl's
-
Sorry didnt get you , Also slack has changed to web request, instead of an API. is it compatible ?
-
- changed status to resolved
Rename ftl files, they need to be unique when deployed in bamboo
This plugin used the same as the original files from the HipChat plugin. So if it is used the modified ones for this plugin won't be used. This resolves
#1→ <<cset 2ecc3b141ec8>>
-
This plugin uses the incoming-webhook style requests, so it shouldn't be impacted
-
I see.. also can I have more documentation how to use ?
-
Doesn't seem to work... Ive added the web hooks ect... why won't this work? Im using an API token that was generated but just didn't want to posted it....
-
@ketanmujumdar you need to create an incoming web hook in your slack domain :
https://YOURDOMAIN.slack.com/services/new/incoming-webhook
They have changed the way the URL is constructed and therefore the don't talk anymore of an API token but of Webhook URL. It looks like the API token is the last part of this URL (after the last /)
-
Could you elaborate on this? I'm seeing the same problem.
I've tried all kind of variations for the slack domain and API token fields:
Slack domain:
- http://domain.slack.com
- domain
- domain.slack.comAPI Token:
- the complete webhook URL (https://hooks.slack.com/services/ABC/DEF/GHI)
- the ID parts: ABC/DEF/GHI
- the last part after the last slash: GHI -
@marache I'm having the same issue as @dredalious, any help would be appreciated.
-
I'm working on a new release of the plugin to support the new Slack API.
-
- changed status to open
Reopening as I'm reproducing this issue
-
- changed status to resolved
WIP for using the new API trying to resolve
#1and#2→ <<cset 2e7a7dca5e23>>
-
- changed status to open
wrong choice of word in commit message
-
Any progress on this? I am still getting the same issues
-
I can confirm that I'm having the same issue. I also rebuilt the plugin from your feature branch but the changes to expose the webhookURL did not fix the issue.
I've got this working in our environment by deploying from the new API feature branch and modifying the populate function. I've added my root cause analysis and proposed fix as comments to your last commit. Sorry about not following the normal fork/pull process but time constraints have forced me to do this quick and dirty :(
I hope this helps.
-
- changed status to resolved
fix from @bmsquire comment on code, fixes
#1#2→ <<cset a70f82540509>>
-
WIP for using the new API trying to resolve
#1and#2→ <<cset 2e7a7dca5e23>>
-
fix from @bmsquire comment on code, fixes
#1#2→ <<cset a70f82540509>>
-
So now will it work with the new Web request ?
-
Yes, I will make a release today that is also compatible with the 5.9.0 release of Bamboo
-
Is it done ?
-
yes you should see an available update in Bamboo's add ons page
-
Awesome, it works just that its not posting to private channel. Not sure why.
-
Hi @ketanmujumdar, sorry I cannot reproduce it locally, sending to a private channel may require to create a incoming web hook specifically for this channel... Please open a new issue if you have anymore problems.
-
- changed status to closed
- Log in to comment
My email ketanmujumdar@gmail.com