Closed cpolzer closed 7 years ago
I might have figured it out: As decoumented in the wiki, create a secret text credential with a spark bot's token.
Ruh roh, did you figure out the issue causing that "Could not send message because of an unknown issue; please file an issue" ? If so, what was the resolution? I will start adding common pitfalls to the wiki. In the near future, I'll also put the exception contents in the jenkins console to help debug further.
Yes I think it was corporate proxy related.
Am 17.05.2017 um 18:33 schrieb Taylor Patton notifications@github.com:
Ruh roh, did you figure out the issue causing that "Could not send message because of an unknown issue; please file an issue" ? If so, what was the resolution? I will start adding common pitfalls to the wiki. In the near future, I'll also put the exception contents in the jenkins console to help debug further.
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.
Will check that out as soon the proxy has been configured
Hi,
when trying to use sparkSend in my pipeline, my credenitals are not found.
Log:
The credentials are stored in global namespace. Also when using the pipeline "pipeline-syntax/" helper, no credentials are listed, but I have a lot of them in use anywhere else.
Versions in use: Jenkins ver. 2.19.4 Cisco Spark Notifier 1.1.0
Any hints?