Closed farahfa closed 6 years ago
I'll note it down and this should be added within the next few days.
Hello, would it be possible to consider using the Credentials plugin directly as consumer? It would secure the storage of the webhook URL and be an elegant solution to the request.
I forgot to finish this off, but I'll go with @marcolinux's suggestion here. Bypasses unneeded steps.
great thanks. If you prepare a pre-release hpi I can test it with pleasure.
Well, for the sake of discussion, discord URL isn't necessarily a "secret". Which is why I suggested the ability to add it as an environment variable approach. Also, this way the developers have more freedom to define where they want to send the payload to.
So lets say they want to send the payload to different discord channels on different Jenkins builds, they could put the webhook urls as a "choice parameter" and the plugin will pick up on that.
I would like to apologize for my absence and lack of care taken on this project. If one of you wants to submit a PR for this that would be great, otherwise I'm setting it up for release 1.3 when I get around to it. I'll definitely have a look at how I'd approach this within the next few days and re-evaluate the options.
Any changes and I'll let you all know.
I'm going to close this, see #25 for more details.
Hello,
Currently if I enter the webhook as a parameter or as an environment variable (secret text), the notification doesn't get sent out as it doesn't accept the URL.
It would be cool if that can get enabled as it will make it so much easier to integrate it to many jobs (and if the webhook URL changes, I'll only have to change it once from the credentials page).